asked on

Changing IP address to a Windows 2003 DC

Hello

Windows 2003 server, AD, DNS, DHCP in 192.168.1.2
5 PC connected in DHCP, network = 192.168.1.x/24

I need change the IP address plan of this network to a new IP plan: 192.168.1.x/24 and to change the IP Server to the new IP 192.168.1.1

In short I need to migrate from 192.168.2.x/24 to 192.168.1.x/24

Is it possible? is it safe? is it easy ? What are the steps to follow ?

Thank you

Joseph Moody

First - why?

Ernie Beek

Second, you can't change the IP address of a DC so you'll have to demote it first..........
Are you sure you want to do that?

Kruno Džoić

piece of cake

http://technet.microsoft.com/en-us/library/cc758579(WS.10).aspx

Muzafar Momin

you can change the IP followed with changes to below

1) replace the old ip with new one in DNS (fwd and reverse zone)
2) add the new ip address in NS (name server ) in dns
3) restart the server

Gad SAADIA

ASKER

muzafar answer say thas it is easy to do

as erniebeek say that I will have to démote and promote AD

what is the real answer ??

The reason why I need to do that is because I am moving the network to another location with another IP plan and I need to share internet access (same router)

Thank you

ASKER CERTIFIED SOLUTION

qf3l3k

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

qf3l3k

PS. Of course I missed one step for DNS... after change you can revert back TTL on DNS zone to previous value as we don't need short life time for DNS records anymore.

Gad SAADIA

ASKER

Thanks for your complete and clear answer

DO I have to change the IP address also in DNS (forward and revert zone?); is there any place in Windows that I have to enter the new IP addresse? (in addition to the "network propierties/TCPIP" zone? IN DHCP I will have to build a new scope, is it ?

I have a single domain environement so nothing to change in Sites adn Services AD

Thanks again

qf3l3k

Once you will reboot DC then DNS entry should be refreshed automatically by NetLogon service.
However, I would recommend to go to DNS and make sure that appropriate record is accordingly updated and if not just change it manually in both, forward and reverse lookup zones.

Of course new DHCP scope will be required which will correspond with new IP subnet.

Except DNS there is no other place you need to update IP until you have some 3rd party services/applications which might require that.

Also, in TCP/IP settings remember to update primary DNS server to point to new IP of the domain controller.

Whole change should not affect users badly as they might have just delay in logging on to network if computer will have old IP in DNS cache.

Gad SAADIA

ASKER

thank you