The company I work for have recently moved office. During that time we setup a second server in the new building and did a phased move. Once everyone was across we reconfigured the main server from the old office to the new IP range following through documentation from the Microsoft website to move a DC to a different ip range/site.
Everything seems to be working great locally, the main server is now been used as the primary DC on the local domain. The problem we are having is with replication between the site housing the moved DC and the other sites in out infrastructure. After further analysis it appears that the main server can't communicate with the other sites, but can communicate with the outside world).
Some basic ping and tracerts were carried out. the results were as follows:
when performing a tracert to a server at a second site from the main local server following error occurs:
ia.net [220.127.116.11] - Destination net unreachable.
The same test performed on the second server in the local site completes successfully, the hops in between timeout so I can see if it passes through 18.104.22.168 or not.
tracert to the www.google.com
from the main server in the local site completes successfully also it passes through the 22.214.171.124 server fine.
tracert from the second server to google also complete fine and uses the same route as the main server, including 126.96.36.199.
Pinging from a server on a remote site fails to the main server, but is successful to the second server.
I am at a bit of a lose with this now so any advice and troubleshooting support is greatly appreciated.