Domain logon issue

[Fat Frog]

Hello.



I am having problem on a member server running Windows Server 2003 SP1.



It took 30 minutes to log on to the domain after a reboot. The server seemed
to be forever hanging at "applying settings..." before it finally connected
to the domain.



I found a lot of errors with event ID 1053, source: userenv. "Windows cannot
determine the user or computer name. (The specified domain either does not
exist or could not be contacted.) Group Policy processing aborted."

____________________



Running netdiag.ext shows some errors:



Testing trust relationships... Failed

Testing Kerberos authentication... Failed



DC discovery test. . . . . . . . . : Failed

Find DC in domain 'MyDomainName':

[FATAL] Cannot find DC in domain 'MyDomainName'.
[ERROR_NO_SUCH_DOMAIN]



DC list test . . . . . . . . . . . : Failed

'MyDomainName': Cannot find DC to get DC list from [test skipped].

List of DCs in Domain 'MyDomainName':



Trust relationship test. . . . . . : Failed

Test to ensure DomainSid of domain 'MyDomainName' is correct.

'MyDomainName': Cannot find DC to get DC list from [test skipped].

[FATAL] Secure channel to domain 'MyDomainName' is broken.
[ERROR_NO_LOGON_SERVERS]



Kerberos test. . . . . . . . . . . : Skipped

'MyDomainName': Cannot find DC to get DC list from [test skipped].



LDAP test. . . . . . . . . . . . . : Failed

Cannot find DC to run LDAP tests on. The error occurred was: The
specified domain either does not exist or could not be contacted.



Find DC in domain 'MyDomainName':

[WARNING] Cannot find DC in domain 'MyDomainName'.
[ERROR_NO_SUCH_DOMAIN]

________________



MS Help says:

To verify that the domain controller can be contacted through Domain Name
System (DNS), try to access \\mydomain.com\sysvol\mydomain.com, where
mydomain.com is the fully qualified DNS name of your domain.

This test also failed.

________________



I tried to connect to this server from a couple of client computers. One
client is ok.



The other client got the following:

The Mapped network drive could not be created because the following error
has occurred: The specified network name is no longer available.



When I tried to connect to it via UNC, it also errored out:

There are currently no logon servers available to service the logon request.



Sorry for the long post.

Thanks for your help.

TL

 

[Fat Frog]

Sorry, please ignore. This is posted to the wrong group by accident.