Discussion Locked

Computer Browsing issue on W2K3/NTdomain

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We've adquired a new box for upgrading our platform from a NT4 SP6 domain to a Win2K3 AD. We've configured DNS, Wins and DHCP on new box, and began to move clients from NT domain to Win2K3 AD, but it has arised an issue when a workstation tries to browse through network places (we use Win2K SP4/WinXP SP1), the most of times we get no machines listed on domain. However, they're getting their DHCP assignment, they can access most of resources on other machines across the network (entering remote destination IP\resource name on a Run dialog box), but they still cannot see anything on domain space. We've reviewed some articles here, and got aware about Browstat utility, and made some test in our enviroment. It turned out that our -workstations- had enabled Computer Browsing service, so we disabled it on all the machines. However, since we get the right source for Browsing services (our Win2K3 domain server), it happens that browsing works fine for two mintes or three, then falls and most of the workstations can't browse domains. At this time, we have two domains running: Old NT4 domain (with most of our clients, who haven't been moved yet because of described browsing problem) and new Win2K3 domain with almost 40% of machines active, using (suppossedly!) Win2K3 server as Master Browsing. Can anyone give some advice on what can be happening? It could seem as something is not working ok on the new server, so it stops responding request from browsing clients for a while (a long while) and then it works again for a couple minutes before failing once again... Thanks in advance for your comments.

5 replies

by bfilmfan

You will need to maintain WINS for the NT 4.0 clients. Providing you currently have a WINS server, make sure that you have an entry for it in DNS.

Are both WINS servers aware of the other? The Primary domain controllers for both the NT and AD domains should be holding the Master Browser roles.

Did you set the PDC in the old NT 4 domain to not be a master browser perhaps?

by jmaldonado

Both servers (NT4 and W2K3) are MB for their own domains, but still at some points it keep happening that service fell down and no clients could see any machine on the network (all of them where still accesible via Run box, though). However, it turned out to be caused for two conditions: since MB for new domain (W2K3) was also serving as a RAS server, whenever a remote client conected to the service, WINS overwrote server record with modem's IP, and no one on the network could reach this IP in order to "ask" the server about browing service, so it fell down (an Microsoft Knowledge Database article outlines this issue, but can remember the number at this moment). On the other hand, a few machines with Win98 were still conecting to our network (three), and when moved them to the new domain they automatically claimed to be a MB (a default setting on Win9x), but since they couldn't autenticate correctly with W2K3 domain they were not able to collect and serve computer list for the domain and the service fell down.

by umang.desai

Make sure no other clients have Master Broweser on i have seen in mixed envirments its causes issues

by jmaldonado

As described in previous response, our problem turned out to be caused by two conditions: A RAS service running on same box than Browsing service, and older Win98 clients connecting to the enviroment. Solving these conditions lead to problem resolution.

This discussion is closed to new replies.