My network is setup in a "hub and spoke" configuration with the main office being the hub and three branch locations. All branches can communicate with the main office via VPN connections. There are no firewalls blocking any internal traffic.
Main office subnet 10.39.1.0/255.255.255.0 Server Name: APP2 10.39.1.251 (2008R2) Server Name: TS 10.39.1.249 (2003R2)
Fraser branch subnet 10.39.3.0/255.255.255.0 Server Name: FRAS3 10.39.3.250 (2008R2)
Kremmling branch 10.39.5.0/255.255.255.0 Server Name: KREM 10.39.5.250 (2008R2)
Grand Lake branch 10.39.2.0/255.255.255.0 Server Name: GL 10.39.2.250(2008R2)
Each of the servers is a DC running AD integrated DNS. All servers successfully resolve NSLOOKUP of each other. All servers successfully reply to pings from APP2 server.
Just to be clear, all the branches have full two way unblocked communication with the main office, but they do not have direct communication to each other.
The problem is, I had to do a dcpromo /forecremoval from a failed server named FRAS2 at Fraser 10.39.3.0. I replaced it with a server named FRAS3. I promoted FRAS3 to a DC two days ago. The server APP2 located at the main office 10.39.1.0 holds all FSMO roles. AD Sites and Services on APP2 at the main office did not have a ntds connection to FRAS3. I manually created a connection. I forced replication and received the error "The naming context is in the process of being removed." SEE ATTACHED SCREEN PRINT.
How do I fix replicaiton? I have downloaded Microsoft's AD Replication status tool and will post more information as it becomes available.