change IP address of w2k3 dc

Forum Windows 2000/NT : Windows 2000/NT General Discussion - change IP address of w2k3 dc

TomsGuide.com: Over 800,000 questions and answers to address all your high-tech questions. Sign up now! Its free!
Word :    Username :           
 

Archived from groups: microsoft.public.win2000.active_directory,microsoft.public.win2000.networking (More info?)

 

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 :-)

Sponsored Links
Register or log in to remove.

Archived from groups: microsoft.public.win2000.active_directory,microsoft.public.win2000.networking (More info?)

 

"eddiec" <chalk@no.spam.netspace.net.au> wrote in message
news:eaMgphEZFHA.1092@tk2msftngp13.phx.gbl...
> 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 /server:DC-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: ]

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]



> TIA
>
> eddiec :-)
>
>

Reply to Anonymous
Tom's Guide > Forum > Windows 2000/NT > Windows 2000/NT General Discussion > change IP address of w2k3 dc
Go to:

There are 12 identified and unidentified users. To see the list of identified users, Click here.

Please mind

You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.

Add a reply Cancel
Google ads