Win2K & XP workstations unable to connect to domain server and DCDiagtest fail

  • Thread starter Thread starter Linda Yang
  • Start date Start date
L

Linda Yang

Hi,

I have a Win2K Advanced Server machine that is used for domain
controller for the machine. It has DNS installed. The only machines
could utilize the domain server logins are the Win98se machines. All
the 2K/XP machines, I will get error message such as:
A domain controller for the domain DOMAINNAME could not be contacted.

I tries Domain Controller Diagnosis (DCDiag.exe), I get following error
messages:

Testing server: Default-First-Site-Name\SVRNAME
Starting test: Connectivity
SVRNAME's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(4c3e4bbe-29c1-40e9-8170-ac8464ab4469._msdcs.DOMAINNAME) couldn't be
resolved, the server name (SVRNAME.DOMAINNAME) resolved to the IP
Address (10.0.0.4) and was pingable. Check that the IP address is
registered correctly with the DNS server.
......................... SVRNAME failed test Connectivity

I searched the help files and internet for a while. Since I am very new
with server administration, I think something's wrong with my DNS
configuration, but I am not sure how to configure it. If anyone can
point me to right direction will be greatly appreciated.

Linda
 
Hi Linda. Correct dns configuration is critical in Windows 2000. Your domain
controller needs to have a static ip address and point to itself by that ip
address in it's tcp/ip properties as preferred dns server. Then your Windows
2000 and XP Pro machines need to point to the domain controller as their
preferred dns server in tcp/ip properties and NEVER an ISP dns server. See the
link below which should be helpful. Fix the problem on the domain controller
first to the point where dcdiag does not show those errors, before you try to
reconnect the W2K workstations. -- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382
 
Possibly:

1. Go to Administrative Tools/Services.

2. Scroll down to Netlogon, right click it, and select Restart.

Now try to join a Win2k machine to the domain.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
 
Steven,

Thanks for the pointers. My server already have a fixed IP, I added the
IP address of the server into DNS server address under TCP/IP
properties, I still get the same connectivity test from DCDiag.

Under computer management, DNS configuration it has forward and backward
look up zone. It was not configured. Do I need to configure it? If
yes, what should be the configuration. Do I also need to configure WINS?

Linda
 
Doug,

Thanks for replying. I tried to restart the netlogon, it didn't help.
I think my problem is still in DNS server configuration, that is why it
failed the connectivity test.

How do I get the IP address register correctly with DNS server?

Linda
 
Back
Top