Discussion Locked

Windows 2000 Support Tools

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I cannot find anything on Microsoft's site about this....
I have installed the adminpak.msi on my Windows 2000 Prof workstation. When I try to open Active Directory Users, or anything else, I get the following message:
"Naming Information cannot be located because: the server is not operational. Contact your System Administrator to verify that your domain is properly configured and is currently online."

These tools work on the server. There is presently only 1 Win2K server in a new domain with about 25 Win2K workstations attached. The rest of the network is NT4 in a different, trusted domain.

6 replies

by tsonnacchio

I'm a Win2K novice myself, but having an identically named computer on the network will generate that error message. Be sure to move the logon from domain to workgroup, then change the computer name. Not sure if that's the problem, but it's happened to me a couple times.

by umbral-echo

Open the command prompt and try the following command:

ping

Use the domain name that the server displays at the top of the tree when you open Active Directory Users and Computers (eg. domain.local).

If you receive a reply look for another answer. If the request times out read on.

DNS name resolution is required to allow the client machine to connect to the domain. All the Active Directory utilities require DNS to be functioning properly or they will report an error. If you can't ping the DNS domain name you have a name resolution problem.

Check the TCP/IP Properties on the client and make sure that the IP address of your network's DNS server appears in the Primary DNS Server box.

If it still wont ping the domain, check the TCP/IP Properties on the server and make sure the IP address of your network's DNS server appears in the Primary DNS Server box.

If the number was wrong on the server, correct it and at the command prompt type:

ipconfig /registerdns

This should get you working if this is a name resolution problem.

One more problem that might be present on your network. If your DNS server is a Windows NT 4 server you need to be aware that this does not provide support for Active Directory SRV records. You need to upgrade, or create a second DNS server on Windows 2000 so the Dynamic Update Protocol can work properly.

by umbral-echo

These problems assume you have not opened the Action Menu in the utility and chosen Connect to Domain, Connect to Domain Controller, or Connect to Forest. This error always appears the first time you run the utilities from the client. If you didn't notice the commands in the action menu this will fix you up immediately.

by tmyers

DHCP was assigning the old domain's DNS server, not the new, correct one.

Thank you

This discussion is closed to new replies.