General discussion

Locked

Changing IP subnets for Win2K domain

By NetLion ·
Due to company reorg I am told that the network addresses for our entire Win2K environment will be changing possibly overnight. While I can guess some of the steps to take with Site definitions and DNS, what other gotchas should I be looking at. I'm sure this has happened to someone before. My plan "was" to bring up the new network with ability to see old one, migrate to new DCs on new network, move member servers, and then take old DCs on old network down. I'm not sure I can do this if the change happens overnight. Thoughts? Good article links?

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by Mikel~T In reply to Changing IP subnets for W ...

Hopefully you are using DHCP for your workstations so that you can set the DHCP lease time to 60 minutes before the IP migration...that will make it easy to get all the client PCs changed over when they start up the next morning.

The servers are pretty easy to migrate. You can always add secondary IP numbers to the LAN interfaces of the servers so everything wills till communicate using the old IP scheme while you start removing the old IPs from one server or group of servers at a time.

I'd also make sure DNS is set to scavenge records every day until you finally make the changeover to the new IP scheme.

This should give you a good start on things.

hope this helps.

Mike C.

Collapse -

by NetLion In reply to

Poster rated this answer.

Collapse -

by NetLion In reply to Changing IP subnets for W ...

Yes, DHCP makes desktop changes a no-brainer. I am most concerned about Domain Controllers. What is the effect of changing the IP address on your DCs, especially those running DNS (integrated with AD) and Certificate Service.

Collapse -

by voldar In reply to Changing IP subnets for W ...

About your DCs, it's not a problem to change the IP, but you should also verify any record in forward and lookup zones so that they show these IP changes. Check the NS records, change the Reverse Lookup Zone IP address etc.
That's it.

Collapse -

by NetLion In reply to

Thanks. I think my paranoia comes from renaming our domain. We have already convinced management to wait until we upgrade to Windows 2003 for that. With over 100 servers and 4 domain controllers I just want to make sure we don't miss anything.

Collapse -

by NetLion In reply to Changing IP subnets for W ...

This question was closed by the author

Back to Windows Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums