We help IT Professionals succeed at work.

Changed IP adddress on a remote server

dances1960
dances1960 asked
on
Hi
I have recently had to move a server to a new office, while on the same subnet I have had to change the server IP address.
I have the offices linked with VPN tunnels and can ping both FQDN and ip address to both sides of the network.
But I am unable to get file replication or AD replication
I get an RPC error and have checked with DNS and think all is ok, what am I missing.
 
Comment
Watch Question

Amitabh SinghCloud Architect

Commented:
Did you checked open TCP port  if its open on your network or Windows Firewalls ?

TCP Port required for AD  replication
http://social.technet.microsoft.com/wiki/contents/articles/active-directory-replication-over-firewalls.aspx
Commented:
Check the Reverse Lookup and Forward Lookup Zones and make sure that the old IP is no longer bounded to the server name.

Author

Commented:
Hi thank you for both replys I shall check both the tcp settings on the asa and forward and reverse look up zones although I have pinged the FQDN and get the correct ip address in reply from the main site office. I

Author

Commented:
all seems fine with the ASA so I dont think it's a port problem. and i have no references to the old IP address in DNS, not sure what to do next
Commented:
You say you changed the IP address of the server, but the new IP has the same mask and is on the same subnet, yes? What if you change the IP back to it's old designation, will it start working again? For test purposes see what happens. If the old IP doesn't work from the new site, this will help you narrow your troubleshooting efforts. Maybe it's a trust issue, or ACL on a firewall???

Author

Commented:
Great idea thanks, I will need to change all the dns back to the old ip address but will do it tonight, thanks for the help so far.

Author

Commented:
Hi
the IP address change didn't do anything but I disabled the KMS and restarted it and replication of the servers went ahead, creating another problem, all the new Pc's that had joined the domain while it wasn't replicating have now lost the ability to logon, the joys of networks
Commented:
For those PCs which lost connection to the DC, you might have to go to the DNS server settings and remove each one of them.  The DNS entries for those systems were bounded to the old IP and must be removed in order for them to bind to the change of the server's IP address.  Make sure that those systems are rebooted first before making an attempt to log onto the domain again.

Author

Commented:
Thank you very much for the support all is now working

Explore More ContentExplore courses, solutions, and other research materials related to this topic.