DCDiag errors (DSA error ) cant replicate between servers

[mndthegap1]

Sorry so long in advance

heres what we did.
demoted a dc using dcpromo and everything seemed to go through, checked ntdsutil and everything was gone.(server died had to remove)
on the other server that had all fszmo roles we did a inplace upgrade to windows 2003 server/AD. (everything went okay no errors etc.)
Got a new server w/ 2k3 on it, named it the same as the old dc that we use to have put on network ran dcpromo upgraded to domain controller everything okay.
had another server in diff branch same thing upgraded to 2k3 everything seemed okay.
BUT upon further checking i get the following errors when i do a dcdiag. I did a dcdiag /fix nothing changed, i can do an nslookup on all servers, soa records etc., i checked the -msdc directory in dns all records for servers there.
here is the dcdiag and repadmin results
I really really appreciate any help with this

C:\>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: ArgoNY\ANASTASIA
Starting test: Connectivity
......................... ANASTASIA passed test Connectivity

Doing primary tests

Testing server: ArgoNY\ANASTASIA
Starting test: Replications
[Replications Check,ANASTASIA] A recent replication attempt failed:
From (unknown) to ANASTASIA
Naming Context: DC=argointl,DC=com
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failu
re.
The failure occurred at 2005-05-25 14:53.49.
The last success occurred at 2005-05-19 09:13.41.
161 failures have occurred since the last success.
[Replications Check,ANASTASIA] A recent replication attempt failed:
From (unknown) to ANASTASIA
Naming Context: CN=Configuration,DC=argointl,DC=com
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failu
re.
The failure occurred at 2005-05-25 14:53.49.
The last success occurred at 2005-05-19 09:10.40.
161 failures have occurred since the last success.
[Replications Check,ANASTASIA] A recent replication attempt failed:
From (unknown) to ANASTASIA
Naming Context: CN=Schema,CN=Configuration,DC=argointl,DC=com
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failu
re.
The failure occurred at 2005-05-25 14:53.49.
The last success occurred at 2005-05-19 09:10.40.
161 failures have occurred since the last success.
......................... ANASTASIA passed test Replications
Starting test: NCSecDesc
......................... ANASTASIA passed test NCSecDesc
Starting test: NetLogons
......................... ANASTASIA passed test NetLogons
Starting test: Advertising
......................... ANASTASIA passed test Advertising
Starting test: KnowsOfRoleHolders
......................... ANASTASIA passed test KnowsOfRoleHolders
Starting test: RidManager
......................... ANASTASIA passed test RidManager
Starting test: MachineAccount
......................... ANASTASIA passed test MachineAccount
Starting test: Services
......................... ANASTASIA passed test Services
Starting test: ObjectsReplicated
......................... ANASTASIA passed test ObjectsReplicated
Starting test: frssysvol
......................... ANASTASIA passed test frssysvol
Starting test: kccevent
......................... ANASTASIA passed test kccevent
Starting test: systemlog
......................... ANASTASIA passed test systemlog

Running enterprise tests on : argointl.com
Starting test: Intersite
......................... argointl.com passed test Intersite
Starting test: FsmoCheck
......................... argointl.com passed test FsmoCheck

C:\>repadmin /showrpes
'repadmin' is not recognized as an internal or external command,
operable program or batch file.

C:\>e:

E:\Program Files\Support Tools>repadmin /showreps
ArgoNY\ANASTASIA
DC Options: IS_GC
Site Options: (none)
DC object GUID: 2c67b754-0f69-4aaa-8b81-c56d9f1a63ca
DC invocationID: 899a3a5d-444d-4a1c-b390-a7568dd54448

==== INBOUND NEIGHBORS ======================================

DC=argointl,DC=com
ArgoNY\JPMOBILESRV\0ADEL:fd4f4597-2e48-44bd-ab1d-3f29f237758d (deleted DSA)
via RPC
DC object GUID: 902a7022-aead-4349-afa6-29d6a813281f
Branch28\ARGOBR28 via RPC
DC object GUID: 4fdf701d-f5d3-45b8-ab6a-7e18a0064744
Last attempt @ 2005-05-25 15:23:51 was successful.
ArgoNY\JPMOBILESRV via RPC
DC object GUID: ee87ef76-eada-42fc-9316-3d0ee93f941b
Last attempt @ 2005-05-25 15:30:06 was successful.

CN=Configuration,DC=argointl,DC=com
ArgoNY\JPMOBILESRV\0ADEL:fd4f4597-2e48-44bd-ab1d-3f29f237758d (deleted DSA)
via RPC
DC object GUID: 902a7022-aead-4349-afa6-29d6a813281f
ArgoNY\JPMOBILESRV via RPC
DC object GUID: ee87ef76-eada-42fc-9316-3d0ee93f941b
Last attempt @ 2005-05-25 15:20:34 was successful.
Branch28\ARGOBR28 via RPC
DC object GUID: 4fdf701d-f5d3-45b8-ab6a-7e18a0064744
Last attempt @ 2005-05-25 15:23:51 was successful.

CN=Schema,CN=Configuration,DC=argointl,DC=com
ArgoNY\JPMOBILESRV\0ADEL:fd4f4597-2e48-44bd-ab1d-3f29f237758d (deleted DSA)
via RPC
DC object GUID: 902a7022-aead-4349-afa6-29d6a813281f
ArgoNY\JPMOBILESRV via RPC
DC object GUID: ee87ef76-eada-42fc-9316-3d0ee93f941b
Last attempt @ 2005-05-25 14:53:49 was successful.
Branch28\ARGOBR28 via RPC
DC object GUID: 4fdf701d-f5d3-45b8-ab6a-7e18a0064744
Last attempt @ 2005-05-25 15:23:51 was successful.

DC=ForestDnsZones,DC=argointl,DC=com
ArgoNY\JPMOBILESRV via RPC
DC object GUID: ee87ef76-eada-42fc-9316-3d0ee93f941b
Last attempt @ 2005-05-25 14:53:49 was successful.

DC=DomainDnsZones,DC=argointl,DC=com
ArgoNY\JPMOBILESRV via RPC
DC object GUID: ee87ef76-eada-42fc-9316-3d0ee93f941b
Last attempt @ 2005-05-25 14:53:49 was successful.

 

[adcfaq]

ok, points are DC's DNS to PDC DNS.

dns lookup failure means name resolution. focus on this.

 

[mndthegap1]

okay i went and demoted the server again that we named the old server followed everything in in http:support.microsoft.com/kb/216498
and everything went through successfully.
readded the server again and did a dcpromo bringing it back up.
NOW when i do a dcdiag. i get the same exact thing I had above BUT it also shows errors now the same as above for the server i just demoted/removed and readded for a 3rd time.

please help, im stuck on this and have a few people breathinig down my neck to fix....

could it be that its because its the same name for the server ?
is there some frs/ ntfrs cache i have to manually clear to get rid of the old entries ?

 

[joepc]

Not 100% about this but I think if you are going to keep the DC name the same you need to run a metadata cleanup command before you dcpromo in the new server.

I know you said you made sure everything was gone, but maybe something to check into. Have you gone into AD sites & servies and tried manually replicating between servers and see if you get any errors? If so it might through something in the event logs for you.