Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 3 subscribers
  • Views 4796 views
  • Users 0 members are here
Options
Suggested
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

WINS not working-- can't figure out if it is Sophos related not.

CarlosNaldinho

I have two LANs connected using IPsec to form a site-to-site VPN using two Sophos UTMs. All is working fine but I'd like to have the remote computers show up when users go to network.

This should be a simple matter of just setting up SAMBA and activating the WINS server function -- which I did.

I then took one computer on each LAN and assigned it to use the WINS server.

The result is that either computer can do name resolution -- I can ping the remote computer using the name rather than the IP but the computers still don't show up in each other's network.

I've checked that the browsing service is on for both Windows 10 computers. The Ubuntu VM running the WINS server is the master for the 192.168.2.0/24 network.. For the 10.1.1.0/24 network the Windows 10 machine connected to the WINS is showing up as master.

Reading about this issue some people mention firewalls being the problem. Is there something I need to do with Sophos to make this work? 

Rather than set the WINS server from each computer is it possible to have Sophos assign it when it hands out IPs?



This thread was automatically locked due to age.
  • 0

    It's been a long time since I have been using WINS but that doesn't seem to be your problem, your problem may be Microsoft related. I think you can find more info following this link.

    Managing several Sophos UTMs and Sophos XGs both at work and at some home locations, dedicated to continuously improve IT-security and feeling well helping others with their IT-security challenges.

    Sometimes I post some useful tips on my blog, see blog.pijnappels.eu/category/sophos/ for Sophos related posts.

  • 0 in reply to apijnappels

    Thanks for the suggestion but that is not it. I know about that issue but I'm not using Windows Server. This is just a basic WINS server setup.

  • 0

    Hi, Carlos, and welcome to the UTM Community!

    Any luck trying #1 in Rulz to see if the UTM is interfering?  Why do you need WINS?  Can your DHCP server make a default Domain assignment?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    I don't need WINS so much as I'd just like to have it -- being able to go to Network and right click on a remote machine to start RDP is easier than having to remember the IP or name of the remote machines.

    I'm fairly new to this but I don't think I'm using domains as I'm not using Active Directory at the moment -- this is just one workgroup over two subnets.

    Since my original post I have made some progress.

    The setup is two subnets 192.168.2.0/24 and 10.1.1.0/24 with the WINS server on 192.168.2.0 and IPsec connecting the two

    I changed DHCP to M-Node on both ends and pointed everything at the WINS server.

    That got me as far as having name resolution work. Without the WINS server I used to have to type 10.1.1.5 to from the other subnet but now I could refer to the computer by name. No computers would show up from the other networks would show up in the opposite subnet.

    I then read that the site-to-site should have a masquerading rule so I added a rule to each for the opposite network to the local interface.

    This fixed my problem -- for one subnet. 10.1.1.0/24 now has all the computers for both networks showing up in browsing. 192.168.2.0/24 only has computers from 192.168.2.0/24

    So I am very close to solving it but also running out of ideas.


Unfiltered HTML