2003 server back to the network

[elektrongyorsito]

Hi,

I have a big trouble. We had to change the motherboard one of our server (Some cooler management failure), but the replacement was unsuccessful So we changed back everything to the original. We have two domain controller:
1) a win2003 (whose motherboard we try to change) with all the five roles:schema master, domain naming master, pdc, infrastructre, rid master and it is a global catalog too.
2) a win2000server slave domain controller with global catalog.

When we try to change back the master the AD failed. So we try to boot in directory restore mode and restore system state.
When the master booted up, the event log showed:
the kcc has detected that successive attempts to replicate with the following dc has consistently failed. After that it seems working because I found in the log:
"The local dc is now the intersite topology generator and has assumed responsibility for generating and maintaining intersite replication topologies for this site." And there is no error after it in the directory service log.

But the file replication service is failed countinously. The log says: "the file replication service is having trouble enabling replication from t2 to t1 for c:\windows\sysvol\domain using the dns name t2.dom.hu"
And this error occures on the other dc, except the sequence mixed: "...replication from t1 to t2 for..."

And t1 has: frs check the sysvol, and t1 cannot became a dc, until this process is complete...

(t2 is the slave, and t1 is the master)

I can ping the dcs from other dc.
But on t1 there is the SYSVOL directory, but not shared to the network. I can't use the c$ (\\t1\c$), unless i use ip address (\\192.168.3.3\c$).

On t1 I run: repadmin /showvector t2:
DsReplicaGetInfo() failed with status 8453 (0x2105)
Replication access was denied.

How can I start the sysvol and others replication?
Thank you

chr

 

[pagy]

This is for windows 2000 but I believe still relevant to your problem;

http://support.microsoft.com/default.aspx?scid=kb;en-us;329860

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[elektrongyorsito]

Thank you pagy!
I viewed it, and I found it an other page:
"Test the remote procedure call (RPC) connectivity between computer A and computer B. To do so, start Event Viewer on computer B from computer A (which uses RPC). Check FRS event logs on both computers. If Event ID 13508 is present, there may be a problem with the RPC service on either computer or with creating a secure connection between computer A and computer B."

Because I couln't open event viewer of t1 from t2, and I have EID: 13508, so I focused on your help:"Step 3: Reset the Secure Channel Password". Before it I test it with:
nltest /sc_verify dom.hu and it says:

Flag:80
Trusted DC Name
Trusted DC Connection Status Status= 1311 0x51f ERROR_NO_LOGON_SERVERS
Trust Verification Status=1311 0x51f ERROR_NO_LOGON_SERVERS
Command completed successfully


So I didn't reset secure channel password. Why is it?