Re: Help needed with dcdiag messages
From: Steven L Umbach (n9rou_at_nospam-comcast.net)
Date: 06/23/04
- Next message: Steven L Umbach: "Re: Network Browsing error in Win2003"
- Previous message: cmalmstrom: "terminal service connection problem"
- In reply to: Fran: "Re: Help needed with dcdiag messages"
- Next in thread: Fran: "Re: Help needed with dcdiag messages"
- Reply: Fran: "Re: Help needed with dcdiag messages"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 23 Jun 2004 04:15:13 GMT
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
<Fran> wrote in message news:6qshd0pn6sugkg32a1osh4d0ed3qluom8a@4ax.com...
> 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 news:m55gd0p8fi0umajkjoj258f0iohhg3m27j@4ax.com...
> >> 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
> >
>
- Next message: Steven L Umbach: "Re: Network Browsing error in Win2003"
- Previous message: cmalmstrom: "terminal service connection problem"
- In reply to: Fran: "Re: Help needed with dcdiag messages"
- Next in thread: Fran: "Re: Help needed with dcdiag messages"
- Reply: Fran: "Re: Help needed with dcdiag messages"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|