This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

UTM doesn't resolve internal hostnames

Couple months ago, I posted this: https://community.sophos.com/products/unified-threat-management/f/53/t/75570

Temporarily gave up with the UTM as I had exams going on. But now, decided to give it another shot in my off time. Bob from these forums was a tremendous help - but alas, I still can't get it working. 

Literally, the only thing that is stopping me from enjoying UTM-protection heaven is the fact it does not resolve internal hostnames. At all. It point blank refuses to resolve anything internally - so I'm stuck having to use \\192.168.1.xxx instead of \\Fileserver. 

To be clear, now, there is no AD server (to simply things, I only have a Windows 10 PC as a file server, a Laptop and a Laser printer as well as a Wireless AP) on the network. Everything is set to stock on the UTM. 

How would one allow the UTM to resolve internal hostnames? Everything is on a WORKGROUP (printer, laptop, file server) - shouldn't the UTM be able to automatically resolve internal hostnames without me having to create static routes or anything like that? There is no AD, no other DNS server etc. 

Thanks!



This thread was automatically locked due to age.
Parents
  • No, you need to define them. The UTM is not compatible with Microsoft Workgroups. 

    Definitions & Users > Network Definitions > New Network Definition.. > Type: host

    Then just add all the systems on your network with static IPs (It looks like there are just 4 of them)

Reply
  • No, you need to define them. The UTM is not compatible with Microsoft Workgroups. 

    Definitions & Users > Network Definitions > New Network Definition.. > Type: host

    Then just add all the systems on your network with static IPs (It looks like there are just 4 of them)

Children
No Data