Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP and Subnet Change

Status
Not open for further replies.

EST7745

IS-IT--Management
May 6, 2003
306
US
Right now we are using 172.25.0.0/16 255.255.0.0 for our numbering scheme on our LAN. I need to renumber the network to 192.168.0.0 255.255.255.0 scheme. I'm trying to figure out what kind of headaches I might run into during this change. It's a very small network - consists of 10 clients and 1 server that is running their DNS, DHCP, Exchange. Can anyone tell me of anything that might cause a problem - besides the obvious like having to reconfigure their DHCP scope etc?
 
Don't delete the scope that you are phasing out. If you merely deactivate it, it will issue NACK messages to clients trying to renew their addresses, and that will force the clients to drop their addresses and look for fresh ones. That will cut your migration time by half. You can set up a separate scope for the clients.

One thing that might be helpful is binding an address from the new network to the server before starting the process. If the server can listen on two networks, it will make the transition process easier.

Set up your DNS reverse lookup zone before you start, so that it can be autopopulated by DHCP, if you are set up for that sort of thing.

After the migration, remove the old address from your server, and then you will need to go through your IIS config, making sure that each website is listening on the new IP address on the General tab. Also check the Default SMTP Virtual Server in Exchange for the same reason. And in the DHCP and DNS environments, check the properties on the server name in the admin consoles and make sure that the services are listening on the proper IP. Sometimes an IP changeover like this can cause a service to listen incorrectly.

ShackDaddy
Shackelford Consulting
 
Do you mind if I ask what the "NEED" is for renumbering your network to the 192.168.0.0/24 subnet? Is there a specific reason for changing the actual IP addresses to be 192.168.0.x ?
 
Yes actually. We originally had a company with 100 client PCs. Now, 10 of those PC have branched off into another company so we would like to segregate those 10 computers into their own little network - however those 10 computers will still need access to two of the remaining 90 computers. So, we are using a Sonicwall to setup routes and rules so that these 10 computers can still get to the 2 computers it needs. Since all of the computers were all on the same network, they all are in the same IP range and subnet mask. Nothing will route to the other side if they are on the same range.
 
We did something just like this about a year ago only it was 110 computers that were broken out into a seperate network. They still received internet access from us as well for some time.

Will those 10 computers that are breaking away have their own domain controllers, DNS servers, etc.? Will they have their own seperate internet connection, etc?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top