change IP address of w2k3 dc

[eddiec]

hi everyone,

I have a DC that was set up in head office on the head office subnet. This
has now been transported to a remote site with an intermittent slow dial up
connection.

If the IP address of the DC is changed to an IP on the remote site LAN the
machine takes about 1/4 hr to boot. How can I move the machine to the remote
subnet?

TIA

eddiec

 

[Robert L [MS-MVP]]

since this is the DC, I think it is DNS issue. we need more information to help.

Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

hi everyone,

I have a DC that was set up in head office on the head office subnet. This
has now been transported to a remote site with an intermittent slow dial up
connection.

If the IP address of the DC is changed to an IP on the remote site LAN the
machine takes about 1/4 hr to boot. How can I move the machine to the remote
subnet?

TIA

eddiec

 

[Herb Martin]

hi everyone,

I have a DC that was set up in head office on the head office subnet. This
has now been transported to a remote site with an intermittent slow dial up
connection.

If the IP address of the DC is changed to an IP on the remote site LAN the
machine takes about 1/4 hr to boot. How can I move the machine to the remote
subnet?

Robert is correct that it may improve if DNS is checked
and correct, however 15 minutes for a Domain Controller
is not extreme (maybe a tad long, but not extreme.)

You will need it to have the correct IP address and subnet
mask before it can boot effectively anyway so fix that.

Fix the Sites and Services to include this site with its subnet
defintion if you haven't done so, and add a Site Link from the
new site to other sites you already have.

Ensure this server is moved to the correct site. Then double
check DNS and replication....

DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)

netdiag /fix

....or maybe:

dcdiag /fix

(Win2003 can do this from Support tools):
nltest /dsregdns /serverC-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.

Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]