Hello Jonathan,No problem with changing ip address, before starting make a |
Meinolf Weber [MVP-DS] replied to Jonathan Zaldivar on Wednesday, November 04, 2009 2:06 AM
|
Hello Jonathan,
No problem with changing ip address, before starting make a backup of course,
then run support tools dcdiag /v, netdiag /v and repadmin /showrepl to check
for errors in the domain. If no errors exist change the ip address and run
ipconfig /flushdns and ipconfig /registerdns. Then restart the netlogon service
or reboot the server. Make SURE you use the DC which is also DNS server or
you have already configured a reachable DNS server.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm |
 |
|
Jonathan Zaldivar wrote:If any workstations or servers reference the old IP |
Hank Arnold replied to Jonathan Zaldivar on Wednesday, November 04, 2009 4:44 AM
|
If any workstations or servers reference the old IP address as one of
their DNS servers, you will need to change them to point to the new IP
address (or a different one).
--
Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services
http://mypcassistant.blogspot.com/ |
 |
|
If you are using dhcp and the dc has a fixed address, make sure to changethe |
Paul Bergson [MVP-DS] replied to Jonathan Zaldivar on Wednesday, November 04, 2009 8:13 AM
|
If you are using dhcp and the dc has a fixed address, make sure to change
the reservation. If your clients recieve their dns address within dhcp make
sure to change the options to reflect this change. When you bring up the
dc, modify the static address and verify any machines that refer to the
dc/dns server that they use a host name and not an ip address. One thing
that pops to mind is a secondary dns server (If you have one) or a WINS
server. Verify they all are pointing properly if using static addresses.
If you have a dmz and there are clients that need to come back inside,
verify that the ports are properly configured for the new location, this is
quite a common error when moving a dc.
--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009
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. |
 |
|