urgent: Second win2003 domain controller doesn't process login requests
- From: StanislavO@xxxxxx
- Date: 4 Feb 2007 04:06:46 -0800
Hello,
I have two Win2003 domain controllers in the organization, both
migrated from WinNT 4.0 -> Windows 2000 -> Windows 2003. One of them,
who used to be PDC previously, has motherboard malfanction which
causes it to halt unexpectedly. Unfortunately when it halts all
network resources immediately become inaccessible, user cannot login,
etc! The second DC seems to be simply ignored.
The hardware can't be replaced immediately, can it be fixed by
software means?
DCDIAG run on secondary server shows:
Testing server: VED-local\BACKUP
Starting test: Connectivity
......................... BACKUP passed test Connectivity
Doing primary tests
Testing server: VED-local\BACKUP
Starting test: Replications
[DC] DsBindWithSpnEx() failed with error 1722,
Win32 Error 1722.
......................... BACKUP passed test Replications
Starting test: NCSecDesc
......................... BACKUP passed test NCSecDesc
Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\BACKUP\netlogon)
[BACKUP] An net use or LsaPolicy operation failed with error
1203, Win3
2 Error 1203.
......................... BACKUP failed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for \
\dc.vedm.local, when we
were trying to reach BACKUP.
Server is not responding or is not considered suitable.
[DC] LDAP search failed with error 58,
Win32 Error 58.
Server BACKUP is advertising as a global catalog, but
[DC] LDAP search failed with error 58,
Win32 Error 58.
Server BACKUP is advertising as a global catalog, but
it could not be verified that the server thought it was a GC.
......................... BACKUP failed test Advertising
Starting test: KnowsOfRoleHolders
Warning: DC is the Schema Owner, but is not responding to DS
RPC Bind.
Warning: DC is the Schema Owner, but is not responding to
LDAP Bind.
Warning: DC is the Domain Owner, but is not responding to DS
RPC Bind.
Warning: DC is the Domain Owner, but is not responding to
LDAP Bind.
Warning: DC is the PDC Owner, but is not responding to DS RPC
Bind.
Warning: DC is the PDC Owner, but is not responding to LDAP
Bind.
Warning: DC is the Infrastructure Update Owner, but is not
responding t
o DS RPC Bind.
Warning: DC is the Infrastructure Update Owner, but is not
responding t
o LDAP Bind.
......................... BACKUP failed test
KnowsOfRoleHolders
Starting test: RidManager
......................... BACKUP passed test RidManager
Starting test: MachineAccount
......................... BACKUP passed test MachineAccount
Starting test: Services
......................... BACKUP passed test Services
Starting test: ObjectsReplicated
......................... BACKUP passed test
ObjectsReplicated
Starting test: frssysvol
......................... BACKUP passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours
after the
SYSVOL has been shared. Failing SYSVOL replication problems
may cause
Group Policy problems.
......................... BACKUP failed test frsevent
Starting test: kccevent
An Error Event occured. EventID: 0xC00005F8
Time Generated: 02/04/2007 14:46:43
Event String: Internal error: The Intersite Messaging
service
An Error Event occured. EventID: 0xC000055D
Time Generated: 02/04/2007 14:46:43
Event String: The Intersite Messaging service could not
receive
......................... BACKUP failed test kccevent
Starting test: systemlog
......................... BACKUP passed test systemlog
Starting test: VerifyReferences
......................... BACKUP passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test
CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test
CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test
CheckSDRefDom
Running partition tests on : vedm
Starting test: CrossRefValidation
......................... vedm passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... vedm passed test CheckSDRefDom
Running enterprise tests on : vedm.local
Starting test: Intersite
......................... vedm.local passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error
1355
A Global Catalog Server could not be located - All GC's are
down.
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
error 135
5
A Good Time Server could not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
A KDC could not be located - All the KDCs are down.
......................... vedm.local failed test FsmoCheck
.
- Follow-Ups:
- Prev by Date: Re: Scheduled tasks only run if logged in
- Next by Date: Re: urgent: Second win2003 domain controller doesn't process login requests
- Previous by thread: Re: 2003 R2 smtp problem
- Next by thread: Re: urgent: Second win2003 domain controller doesn't process login requests
- Index(es):
Relevant Pages
|
