No Domain or Authentication from Domain Controller

  • Thread starter Thread starter Dan Kline
  • Start date Start date
D

Dan Kline

Hi,
I seem to have lost my domain even though AD and all other
win2k server functions are working. No one can
authenticate because the domain can't be found. However
users can map all the drives they want.
DCDiag reports the following:


DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\XXXXX
Starting test: Connectivity
XXXXX'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

(864d4477-a541-4031-a840-
2960e7f2e68c._msdcs.xxxxx.xxx.xxx.edu)

couldn't be resolved, the server name
(xxxxx.xxxxx.xxx.xxx.edu)

resolved to the IP address (xxx.xxx.xxx.xxx) and
was pingable. Check

that the IP address is registered correctly with
the DNS server.
......................... XXXX failed test
Connectivity

Doing primary tests

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

Running enterprise tests on : xxxxx.xxx.xxx.edu
Starting test: Intersite
......................... xxxxx.xxx.xxx.edu
passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(PDC_REQUIRED) call failed,
error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
......................... xxxxx.xxx.xxx.edu
failed test FsmoCheck

Does this information tell me anything other than that my
domain is gone? I have verified that the server is listed
in DNS. Is there a way to get the domain back without
doing dcpromo? If there isn't, is there a way to do
dcpromo without having to make all my accounts and set all
of my permissions all over again?
Thanks,
Dan
 
Ensure that the DC and all client machines are pointing at the DC only for DNS. Verify that the primary dns suffix on the DC and clients matches that of the
active directory domain name. Lastly, verify that in DNS you have a forward lookup zone that matches the active directory domain name and allows dynamic
updates.

Thank you,
Mike Johnston
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
 
You could install the support tools on your 2000 cd, then run netdiag /fix
and then netdiag /v /l and send the netdiag log to use so we cna verufuty
settings?
"Ace Fekay [MVP]"
 
Back
Top