Discussion Locked

W2K Pro clients cann't see domain.

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are running a Windows NT Server 4.0 domain and problems occur when Windows 2000 Pro clients try to join the domain. Windows 9x clients have no problem with joining the domain. The environment is a routed TCP/IP network. When certain, not all, W2KPro clients try to add to the domain they get an error message that says" The domain MSU could not be found. If netbuei is added to the protocol list then the clients is allowed to join the domain.

5 replies

by dc1

Couple of options instead of installing Netbeui.

1. Install WINS/DNS on your network and configure all servers/clients with the addresses of the servers.

2. Configure the local lmhost or hosts file on the w2k pro clients to resolve the domainand domain controller.

by joseph moore

In addition to the comments by DC1:
It sounds like your 2000 Professional clients do not have a WINS server configured for them to use.
2000 uses configured DNS server(s) for all name resolution first, then any entries in the old fashioned HOSTS file.
After that, 2000 Pro uses a configured WINS server, and then the LMHOSTS file.
Finally, it is supposed to do a network broadcast, screaming the names it is trying to resolve across your network.
When you are running a NT4 domain and you have2000 Pro clients, you need to either configure a WINS server on the 2000Pro clients and/or make 2 entries in the LMHOSTS file for the NT4 PDC and the NT4 domain.

Here is a TechNet article on how to write the LMHOSTS file for domain controller resolution:
http://support.microsoft.com/support/kb/articles/Q180/0/94.ASP
(please remove any spaces)

This discussion is closed to new replies.