Server 2003 Replication Error

[bmdixon]

Over Easter we set up a whole new network.
We've been getting an error when testing replication between domain controllers.

Replicating on KHPDC2 works fine but when on KHPDC1 this error occurs...
I have no idea what is causing this?! Any help would be very gratefully received!

[adamf]

Can you resolve the names of the servers from each other using nslookup? Any errors in event logs? DNS errors would be a good place to start.

[Geoff]

Presumably you've checked your DNS is sane and working?

[bmdixon]

It seems to be working now....
i did a ipconfig /flushdns and then ipconfig /registerdns and a couple of minutes later it works....
DNS is/was working fine, i could ping the server(s), no problem.
Thanks for your advice

EDIT:
Spoke too soon. It's back, but seems to be coming and going....!
In the eventviewer when i run ipconfig /registerdns i get the following error:

The system failed to register pointer (PTR) resource records (RRs) for network adapter with settings:

Adapter Name : {3EB3183C-947A-46D4-86AE-0A9C9AFAF00F}
Host Name : khpdc1
Adapter-specific Domain Suffix : KINGSHEATH.local
DNS server list :
10.125.16.55, 10.120.224.105
Sent update to server : 10.120.224.107
IP Address : 10.125.16.56

The reason that the system could not register these RRs was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request.

You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator.

[Geoff]

What DNS servers are you using?

[bmdixon]

10.125.16.55 is our internal DNS (and also our secondry Domain Controller)

[ChrisH]

Try running the ultrasound tool from microsoft it is very helpful at monitoring and troubleshooting problems like this.

[Geoff]

What is 10.120.224.105 and 10.120.224.107?

[SYNACK]

Weird it seems to be trying to update your records on 10.120.224.107, is this one of your servers also.

It might be helpful to post up an "ipconfig /all" so that we can see whats going on with your net cards configurations.

Random thought, do you have more than one network card in the system as this could be causing it some confusion.

I would try adding the record manually in the DNS server snapin on your DNS server. This can sometimes get through weird security issues that occur as the record then exists and it is only an update.

[j17sparky]

I have the same problem, seems to come and go at random. 3years on i still havnt traced the problem.

[bio]

please run dcdiag on both DC's as well and post the outputs, so we can try to help further. The tool replmon is also quite handy with this problem

bio..

[ezzauk]

Hi ya do you have 2 nic's pluged in on the server in Q?, as if there both on the same ip range this will cause problems. The best option if you want the two nics working on the same ip range is to trunk them on the server and switch.

[Jennifer-Botham]

The reason that the system could not register these RRs was because of a security related problem.