DcDiag errors

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am working with a single 2000 Domain controller.
Users are experiencing slow log in, which I tracked to DNS configs on the
workstation as well as in DNS.

We are also experiencing errors authenticating workstations to the domain.
If I try joining the workstation to the domain "abcdbc.k12.pa.us", I get an
error that the domain can not be resolved in DNS. If I try to join the
workstation to the original NT4 domain "abcd.k12.pa.us", I am successful and
the end result is that the workstation has joined the domain
"abcdbc.k12.pa.us".

We are also receiving errors with event id 5513 from netlogon as well as
5774 from dns in the event logs.

I have run dcdiag which reports the following:

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\JOHN2
Starting test: Connectivity
JOHN2'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
(164ff663-f4d5-4bd4-81d2-7fe5b437dab7._msdcs.abcdbc.k12.pa.us)
couldn't be resolved, the server name (john2.abcdbc.pvt.k12.pa.us)
resolved to the IP address (192.168.1.22) and was pingable. Check
that the IP address is registered correctly with the DNS server.
......................... john2 failed test Connectivity

Doing primary tests

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

Running enterprise tests on : abcdbc.k12.pa.us
Starting test: Intersite
......................... abcdbc.k12.pa.us passed test Intersite
Starting test: FsmoCheck
......................... abcdbc.k12.pa.us passed test FsmoCheck


The computer name is listed as: john2.abcdbc.pvt.k12.pa.us
the domain is listed as: abcdbc.k12.pa.us


Any suggestions as to how to correct this?
Or should I resort to rebuilding this system.

The original admin tried to upgrade equipment and OS with out doing a
migration. But instead tried to duplicate the domain.

Thanks for the help in advance,
Jeff
 
Are the clients pointing to your Internal DNS Server? Is the DC ( assuming
only one ) pointing only to itself? So, if the IP Address is 192.168.1.15
in the TCP/IP Configuration is the Domain Controller pointing to O*N*L*Y
192.168.1.15? Are your clients getting the IP Lease from DHCP? Does DHCP
give only the local DNS Server IP Address ( again, 192.168.1.15 )?

There is no room for your ISP's DNS Server information anywhere in your
environment EXCEPT in the Forwarders tab in the Forward Lookup Zone.

--
Cary W. Shultz
Roanoke, VA 24014
Microsoft Active Directory MVP

http://www.activedirectory-win2000.com
http://www.grouppolicy-win2000.com
 
Cary,
Yes the clients are pointing to the server for dns.
I checked the ip configuration of the nic and it is configured to look to
itself for dns.

Fowarding is set to the isp.

In the error message It suggests to check or register the servers ip address
correctly in dns. How do I register this correctly?

Thanks
Jeff
 
Back
Top