WINS setup

[Jeff Brooks-Manas]

Hello,

I have a mixed 2000 server/NT4.0 SP 6a server environment, with all 2000 Pro
clients. There are three offices on AD (in the same domain) and two offices
that each have NT4.0 domains. I'm still running AD in mixed mode until I can
get rid of two legacy domains. WINS is set up in a hub and spoke
configuration, with one server configured as the push/pull partner with the
4 other servers. There is no other WINS replication going on. I am not able
to see all machines in the network neighborhood (even within the domain),
let alone across domains. If I do a search for computers, I can find the
machines in other domains, and I can map the shares. I want to be able to
see the other machines without having to search.

Thanks in advance for any help with this!

Jeff

 

[Ellen Prater [MSFT]]

Make sure that all wins servers are pointing to themselves for both primary
and secondary wins servers. Also make sure that the push/pull relationship
is on both sides (hub has a push/pull relationship with the spoke and the
spoke has a push/pull relationship with the hub). Port 42 must be open in
both directions for the 2 wins servers to replicate wins. On each WINS
server, you should see a 1Bh record for the domain master browser which is
the PDC or PDC emulator. When clients bootup, they will query the 1Bh in
wins to get the browse list. If the browse list is incomplete, they will
not be able to browse all segments. If they can't browse at all, then the
1Bh is most likely missing from their wins server. To get the PDC emulator
to register with WINS, do an nbtstat -RR. Then this record will be
replicated to the other wins servers. Each network segment has a master
browser which updates the domain master browser's list.

This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"