Help needed with dcdiag messages

  • Thread starter Thread starter Fran
  • Start date Start date
F

Fran

I have a new client with a Windows 2000 server and AD running. We're
having some network issues (the database engine loses connection from
time to time) and I believe these to be DNS relates.

When I run DCDiag I get the following errors:

Testing server: Default-First-Site-Name\DC1
Starting test: Connectivity
DC1'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
(ab15732d-4b84-4b17-8283-fab8da113775._msdcs.[DomainName].com)
couldn't be
resolved, the server name ([DomainName].com) resolved to the IP
address (192.168.1.11) and was pingable. Check that the IP
address is
registered correctly with the DNS server.
......................... VTC failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\DC1
Skipping all tests, because server DC1 is
not responding to directory service requests

What am I missing here? How can I fix this so that the server is
running properly?

Fran
 
Open DNS snap-in and drill down to Forward lookup Zones/{yourdomain}/_msdcs
records. Here you should have domain controllers Aliases - the single-part
alias or alternate name for a host in this zone. If blank, the host name is
the same as the parent domain name. If you need to add a name here that
contains a period (.) to indicate the name of an additional domain level,
first add the additional domain separately in the DNS console and then add a
new CNAME record there as a single-part name.
ADSS uses these Aliases as the directory system agent (also known as "DSA")
object for the domain controller and the name of the forest in which the
domain controller is located.
 
Make sure that the domain controller is pointing ONLY to itself via it's static IP
address as it's preferred dns server in tcp/ip properties. After that try in this
order ipconfig /flushdns, netdiag /fix, ipconfig /registerdns, and restart netlogon
service. If possible a reboot would be good an run dcdiag again to see if the problem
clears up. Refer to the "To repair the Active Directory DNS record registration" in
the KB link below for more details. --- Steve

http://support.microsoft.com/?kbid=260371
 
I looked in the DNS snapin. There are no "_msdcs" or other "_"
listings in the DNS Forward Lookup Zones section.

Does this mean that the AD was set up incorrectly? If so, how can I
fix this (and where can I get details on that fix?)

Fran
 
Great suggestions, Steve! That fixed the DCDIAG error messages
completely! I hope this fixes my Database engine problems, too. Time
will tell, now. I really appreciate the help!

Fran

Make sure that the domain controller is pointing ONLY to itself via it's static IP
address as it's preferred dns server in tcp/ip properties. After that try in this
order ipconfig /flushdns, netdiag /fix, ipconfig /registerdns, and restart netlogon
service. If possible a reboot would be good an run dcdiag again to see if the problem
clears up. Refer to the "To repair the Active Directory DNS record registration" in
the KB link below for more details. --- Steve

http://support.microsoft.com/?kbid=260371

I have a new client with a Windows 2000 server and AD running. We're
having some network issues (the database engine loses connection from
time to time) and I believe these to be DNS relates.

When I run DCDiag I get the following errors:

Testing server: Default-First-Site-Name\DC1
Starting test: Connectivity
DC1'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
(ab15732d-4b84-4b17-8283-fab8da113775._msdcs.[DomainName].com)
couldn't be
resolved, the server name ([DomainName].com) resolved to the IP
address (192.168.1.11) and was pingable. Check that the IP
address is
registered correctly with the DNS server.
......................... VTC failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\DC1
Skipping all tests, because server DC1 is
not responding to directory service requests

What am I missing here? How can I fix this so that the server is
running properly?

Fran
Click to expand...
Click to expand...
 
Glad it worked for you and thanks for reporting back. The other problem will probably
clear up as most problems within a W2K domain are dns related as dns is used for a
resource locator in addition to name resolution. --- Steve

Great suggestions, Steve! That fixed the DCDIAG error messages
completely! I hope this fixes my Database engine problems, too. Time
will tell, now. I really appreciate the help!

Fran

Make sure that the domain controller is pointing ONLY to itself via it's static IP
address as it's preferred dns server in tcp/ip properties. After that try in this
order ipconfig /flushdns, netdiag /fix, ipconfig /registerdns, and restart netlogon
service. If possible a reboot would be good an run dcdiag again to see if the problem
clears up. Refer to the "To repair the Active Directory DNS record registration" in
the KB link below for more details. --- Steve

http://support.microsoft.com/?kbid=260371

I have a new client with a Windows 2000 server and AD running. We're
having some network issues (the database engine loses connection from
time to time) and I believe these to be DNS relates.

When I run DCDiag I get the following errors:

Testing server: Default-First-Site-Name\DC1
Starting test: Connectivity
DC1'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
(ab15732d-4b84-4b17-8283-fab8da113775._msdcs.[DomainName].com)
couldn't be
resolved, the server name ([DomainName].com) resolved to the IP
address (192.168.1.11) and was pingable. Check that the IP
address is
registered correctly with the DNS server.
......................... VTC failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\DC1
Skipping all tests, because server DC1 is
not responding to directory service requests

What am I missing here? How can I fix this so that the server is
running properly?

Fran
Click to expand...
Click to expand...
Click to expand...
 
I tried this on another similar site (but wasn't having any problems)
and got several errors when I ran NetDiag /Fix
like:

DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for
the name '[server].[domainname].com.'. [RCODE_SERVER_FAILURE]
The name '[server].[domainname].com.' may not be
registered in DNS.

Isn't this an easy fix to get things started?

Fran
Make sure that the domain controller is pointing ONLY to itself via it's static IP
address as it's preferred dns server in tcp/ip properties. After that try in this
order ipconfig /flushdns, netdiag /fix, ipconfig /registerdns, and restart netlogon
service. If possible a reboot would be good an run dcdiag again to see if the problem
clears up. Refer to the "To repair the Active Directory DNS record registration" in
the KB link below for more details. --- Steve

http://support.microsoft.com/?kbid=260371

I have a new client with a Windows 2000 server and AD running. We're
having some network issues (the database engine loses connection from
time to time) and I believe these to be DNS relates.

When I run DCDiag I get the following errors:

Testing server: Default-First-Site-Name\DC1
Starting test: Connectivity
DC1'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
(ab15732d-4b84-4b17-8283-fab8da113775._msdcs.[DomainName].com)
couldn't be
resolved, the server name ([DomainName].com) resolved to the IP
address (192.168.1.11) and was pingable. Check that the IP
address is
registered correctly with the DNS server.
......................... VTC failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\DC1
Skipping all tests, because server DC1 is
not responding to directory service requests

What am I missing here? How can I fix this so that the server is
running properly?

Fran
Click to expand...
Click to expand...
 
I tried this on another similar site (but wasn't having any problems)
and got several errors when I ran NetDiag /Fix
like:

DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for
the name '[server].[domainname].com.'. [RCODE_SERVER_FAILURE]
The name '[server].[domainname].com.' may not be
registered in DNS.

Isn't this an easy fix to get things started?

Fran
Make sure that the domain controller is pointing ONLY to itself via it's static IP
address as it's preferred dns server in tcp/ip properties. After that try in this
order ipconfig /flushdns, netdiag /fix, ipconfig /registerdns, and restart netlogon
service. If possible a reboot would be good an run dcdiag again to see if the problem
clears up. Refer to the "To repair the Active Directory DNS record registration" in
the KB link below for more details. --- Steve

http://support.microsoft.com/?kbid=260371

I have a new client with a Windows 2000 server and AD running. We're
having some network issues (the database engine loses connection from
time to time) and I believe these to be DNS relates.

When I run DCDiag I get the following errors:

Testing server: Default-First-Site-Name\DC1
Starting test: Connectivity
DC1'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
(ab15732d-4b84-4b17-8283-fab8da113775._msdcs.[DomainName].com)
couldn't be
resolved, the server name ([DomainName].com) resolved to the IP
address (192.168.1.11) and was pingable. Check that the IP
address is
registered correctly with the DNS server.
......................... VTC failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\DC1
Skipping all tests, because server DC1 is
not responding to directory service requests

What am I missing here? How can I fix this so that the server is
running properly?

Fran
Click to expand...
Click to expand...
 
Sometimes error messages can be temporary due to network connectivity to a dns
server, etc. I would be more concerned if you were having access problems in the
network or if dcdiag showed unexplained major errors. The KB I referenced before is a
good start to troubleshoot AD dns problems which suggest some of the fixes I listed.
Most dns issues are due to a domain computer having the wrong dns servers listed in
their dns preferred servers. You may also want to post in the win2000.dns newsgroup
as there are some real dns and Active Directory experts over there. --- Steve


I tried this on another similar site (but wasn't having any problems)
and got several errors when I ran NetDiag /Fix
like:

DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for
the name '[server].[domainname].com.'. [RCODE_SERVER_FAILURE]
The name '[server].[domainname].com.' may not be
registered in DNS.

Isn't this an easy fix to get things started?

Fran
Make sure that the domain controller is pointing ONLY to itself via it's static IP
address as it's preferred dns server in tcp/ip properties. After that try in this
order ipconfig /flushdns, netdiag /fix, ipconfig /registerdns, and restart netlogon
service. If possible a reboot would be good an run dcdiag again to see if the problem
clears up. Refer to the "To repair the Active Directory DNS record registration" in
the KB link below for more details. --- Steve

http://support.microsoft.com/?kbid=260371

I have a new client with a Windows 2000 server and AD running. We're
having some network issues (the database engine loses connection from
time to time) and I believe these to be DNS relates.

When I run DCDiag I get the following errors:

Testing server: Default-First-Site-Name\DC1
Starting test: Connectivity
DC1'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
(ab15732d-4b84-4b17-8283-fab8da113775._msdcs.[DomainName].com)
couldn't be
resolved, the server name ([DomainName].com) resolved to the IP
address (192.168.1.11) and was pingable. Check that the IP
address is
registered correctly with the DNS server.
......................... VTC failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\DC1
Skipping all tests, because server DC1 is
not responding to directory service requests

What am I missing here? How can I fix this so that the server is
running properly?

Fran
Click to expand...
Click to expand...
Click to expand...
 
Will do, Steve. Thanks again for the assistance!

Fran

Sometimes error messages can be temporary due to network connectivity to a dns
server, etc. I would be more concerned if you were having access problems in the
network or if dcdiag showed unexplained major errors. The KB I referenced before is a
good start to troubleshoot AD dns problems which suggest some of the fixes I listed.
Most dns issues are due to a domain computer having the wrong dns servers listed in
their dns preferred servers. You may also want to post in the win2000.dns newsgroup
as there are some real dns and Active Directory experts over there. --- Steve


I tried this on another similar site (but wasn't having any problems)
and got several errors when I ran NetDiag /Fix
like:

DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for
the name '[server].[domainname].com.'. [RCODE_SERVER_FAILURE]
The name '[server].[domainname].com.' may not be
registered in DNS.

Isn't this an easy fix to get things started?

Fran
Make sure that the domain controller is pointing ONLY to itself via it's static IP
address as it's preferred dns server in tcp/ip properties. After that try in this
order ipconfig /flushdns, netdiag /fix, ipconfig /registerdns, and restart netlogon
service. If possible a reboot would be good an run dcdiag again to see if the problem
clears up. Refer to the "To repair the Active Directory DNS record registration" in
the KB link below for more details. --- Steve

http://support.microsoft.com/?kbid=260371

<Fran> wrote in message I have a new client with a Windows 2000 server and AD running. We're
having some network issues (the database engine loses connection from
time to time) and I believe these to be DNS relates.

When I run DCDiag I get the following errors:

Testing server: Default-First-Site-Name\DC1
Starting test: Connectivity
DC1'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
(ab15732d-4b84-4b17-8283-fab8da113775._msdcs.[DomainName].com)
couldn't be
resolved, the server name ([DomainName].com) resolved to the IP
address (192.168.1.11) and was pingable. Check that the IP
address is
registered correctly with the DNS server.
......................... VTC failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\DC1
Skipping all tests, because server DC1 is
not responding to directory service requests

What am I missing here? How can I fix this so that the server is
running properly?

Fran
Click to expand...
Click to expand...
Click to expand...
 
Back
Top