Can we change IP address of Domain Controllers

[Guest]

Hi All,

I would like to change IP address of Domain Controllers with Windows 2003
Server. The DNS is AD Integrated. I have 1 DC and 1 ADC at my location and 3
ADCs in remote locations. I have to change IP addresses of all the DCs and IP
Class will be different.
Will it work? If yes, how I can do so.

Koushik Sarkar
MCSA

 

[Myweb]

Hello Koushik,

Post what you have configured and what you will have in the future. It's
easier to help you.

Best regards

Myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

 

[Herb Martin]

Hi All,

I would like to change IP address of Domain Controllers with Windows 2003
Server. The DNS is AD Integrated. I have 1 DC and 1 ADC at my location and
3
ADCs in remote locations. I have to change IP addresses of all the DCs and
IP
Class will be different.
Will it work? If yes, how I can do so.

Yes. After you change it, run "NetDiag /fix" (Restarting NetLogon should
be sufficient but NetDiag /fix seems to be the most reliable.)

You may also need to reboot but I would not expect that to be necessary.

 

[Paul Bergson [MVP-DS]]

Yes, but make sure that you either reboot the dc, restart netlogon or run
netdiag /fix. Also ipconfig /registerdns and point all clients that use the
dc for dns point to the new location. Also be aware of any changes to sites
and services.

http://technet2.microsoft.com/windo...86417143-92b6-431b-8439-91f456e921dd1033.mspx

When complete I would also

Run diagnostics against your Active Directory domain.

If you don't have the tools installed, install them from your server install
disk.
d:\support\tools\setup.exe

Run dcdiag, netdiag and repadmin in verbose mode.
-> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt

**Note: Using the /E switch in dcdiag will run diagnostics against ALL dc's
in the forest. If you have significant numbers of DC's this test could
generate significant detail and take a long time. You also want to take
into account slow links to dc's will also add to the testing time.

If you download a gui script I wrote it should be simple to set and run
(DCDiag and NetDiag). It also has the option to run individual tests
without having to learn all the switch options. The details will be output
in notepad text files that pop up automagically.

The script is located in the download section on my website at
http://www.pbbergs.com

Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)

When complete search for fail, error and warning messages.


--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Guest]

Thanks Paul and Herb, lemme do the change and see what happens.

 

[Herb Martin]

Thanks Paul and Herb, lemme do the change and see what happens.

"DCdiag /c" before AND after messing with a DC is a very good idea.

DCDiag should be run regularly anyway -- search the output for FAIL
or WARN and fix the problems.