We have three DCs in one location (London) and one DC in another location (Swindon).
London DCs are 1 x Win2000 SP4, 1 Win2003, 1 x Win2003 R2
Swindon DC is Win2000 SP4
All FSMOs are located on the Win2003 R2 server.
GC is on Win2003 R2 server in London and on Win2000 server in Swindon.
Replication was working between all four DCs, but now it is failing from London to Swindon. We recently removed a DC that was the primary DNS for the network, the Win2003 R2 box is now the only DNS server in the network. I've checked DNS entries both on the network properties and also within the DNS server itself and I believe everything is correct (famous last words!).
Swindon:
The DC can replicate OK with all other DCs. I've ran netdiag and dcdiag on Swindon server and no error shows up.
Run repadmin / showreps and it shows the other DCs as both inbound and outbound neighbours.
Run repadmin /getchanges server-id and uid etc and it brings back any changes OK.
London:
The same happens on all DCs in London:
Repadmin /showreps - they all show just inbound neighbours but the Swindon server brings up the following error:
Source: Swindon\DC1
******* 4322 CONSECUTIVE FAILURES since 2006-12-07 19:14:13
Last error: 1722 (0x6ba):
The RPC server is unavailable.
If I try to run repadmin /getchanges I get the following error:
Building starting position from destination server DC1
DsBindWithCred to DC1 failed with status 1722 (0x6ba):
The RPC server is unavailable.
If I run netdiag in verbose mode I see this:
DC list test . . . . . . . . . . . : Passed
List of DCs in Domain 'CORP':
server5.corp.co.uk
server8.corp.co.uk
SERVER2.corp.co.uk
DC1.corp.co.uk (this DC is down)
Therefore it does not do an LDAP test etc on this server
I run dcdiag in verbose mode on all servers in the enterprise and see the following entry in the file:
Testing server: Swindon\DC1
Starting test: Connectivity
* Active Directory LDAP Services Check
[DC1] LDAP search failed with error 58,
The specified server cannot perform the requested operation..
***Error: The machine, DC1 could not be contacted, because of a
bad net response. Check to make sure that this machine is a Domain
Controller.
......................... DC1 failed test Connectivity
I can ping DC1 from all other DCs using it's FQDN even after flushing the DNS cache from each server.
Any help would be much apreciated
MM
|
