Hi John,
I would make sure that DNS setting on server is pointing back at itself with
127.0.0.1. I would also configure new IP in old subnet just before I would
turn it off and move it to new site. Make sure that if there are any routers
or firewalls between one and the other site that they are properly
configured for replication between one and other DC.
After you turn it on, it should automatically update DNS records, but if it
doesn't restart the NetLogon service (don't disable the service, just
restart it)...
I hope this helps,
Mike
"John zhang" <(E-Mail Removed)> wrote in message
news:4dda01c473de$04db4770$(E-Mail Removed)...
> We have a DC (2003 domain controller) setup and running
> in head office (not holding any of Master roles. I
> planning to move this server to a branch office, which
> means I will be doing the following steps.
>
> 1. Disconnect it from network;
> 2. Change the IP address of the server;
> 3. Ship and connect the server into branch network.
>
> Will this cause any problem? Is there any DNS entry I
> have to manually update to reflect the IP changes or it
> will be updated automactically (Auto update is turned on
> in the Zone). I know there are some work needs to be done
> in AD, for example move the server to a different site
> etc....
>
> Any help would be appreciated.
>
> John
>
|