Hi there,
I'm currently trying resolve some wins replication problems. I think I have tracked a lot of it down to the fact that a lot the WINS servers are not pointing to themselves, there isn't a proper hub/spoke topology amongst other things.
However, does anyone know why I may be experiencing either of the two issues below :
- on running an nbtstat -c on the (supposedly) hub server I get a lot of entires that have an IP address in both the name and address field i.e.
Name Type Host Address Life [sec]
---------------------------------------------------------
10.14.101.40 <20> UNIQUE 10.14.101.40 602
10.132.103.93 <20> UNIQUE 10.132.103.93 600
10.10.106.114 <20> UNIQUE 10.10.106.114 600
- Also on putting a sniffer on the network I am getting quite a few clients that are send UDP requests on port 137 to the wins serevr for FQDNs (which are then aboviously failing) despite these clients having DNS servers defined and the appropriate DNS entries being present.
Any help much appreciated
Ben.
I'm currently trying resolve some wins replication problems. I think I have tracked a lot of it down to the fact that a lot the WINS servers are not pointing to themselves, there isn't a proper hub/spoke topology amongst other things.
However, does anyone know why I may be experiencing either of the two issues below :
- on running an nbtstat -c on the (supposedly) hub server I get a lot of entires that have an IP address in both the name and address field i.e.
Name Type Host Address Life [sec]
---------------------------------------------------------
10.14.101.40 <20> UNIQUE 10.14.101.40 602
10.132.103.93 <20> UNIQUE 10.132.103.93 600
10.10.106.114 <20> UNIQUE 10.10.106.114 600
- Also on putting a sniffer on the network I am getting quite a few clients that are send UDP requests on port 137 to the wins serevr for FQDNs (which are then aboviously failing) despite these clients having DNS servers defined and the appropriate DNS entries being present.
Any help much appreciated
Ben.