win2k server change IP address scheme?
Hi - it feels good to be on board!
I've "inherited" a small business network based on win2k with a mix of win98, XP home and pro clients, and several remote offices "connected" via VPN. A couple of offices worked fine when they were on ISDN, but my predecessor could not get VPN to work over ADSL.
I believe the main problem is that the IP address range we use (for over 10 years!) is in the "public" domain (192.192.19x.x), registered in Taiwan and maybe conflicting!
I'm planning to move over to a "private" subnet in the 10.x.x.x/24 range and I believe I'm fairly well prepared for the change.
I would however, appreciate any advice with the server setup -
I've created a new DHCP scope (with an exclusion range for static IP's) - not activated it yet.
I will change the server, mail server and router's static IP addresses.
Reboot the client PC's (on DHCP)
Reconfigure network printers etc (on static IP's)
Then reconfigure the VPN gateways.
I wonder, is there's anything obvious that I may have overlooked, particularly with the server setup?
Any help / advice would very much appreciated.
Many thanks
Milly54
I've "inherited" a small business network based on win2k with a mix of win98, XP home and pro clients, and several remote offices "connected" via VPN. A couple of offices worked fine when they were on ISDN, but my predecessor could not get VPN to work over ADSL.
I believe the main problem is that the IP address range we use (for over 10 years!) is in the "public" domain (192.192.19x.x), registered in Taiwan and maybe conflicting!
I'm planning to move over to a "private" subnet in the 10.x.x.x/24 range and I believe I'm fairly well prepared for the change.
I would however, appreciate any advice with the server setup -
I've created a new DHCP scope (with an exclusion range for static IP's) - not activated it yet.
I will change the server, mail server and router's static IP addresses.
Reboot the client PC's (on DHCP)
Reconfigure network printers etc (on static IP's)
Then reconfigure the VPN gateways.
I wonder, is there's anything obvious that I may have overlooked, particularly with the server setup?
Any help / advice would very much appreciated.
Many thanks
Milly54
0
Comments
A poorly documented network will cause massive headaches for anyone trying to change anything.
Also you probably don't really need 10.0.0.0/24, Unless you need all 24 bits for the network's.Im pretty sure 10.0.0.0/16 sure be more then enough. You could probably get by with less if you subnet it.
For VPN's im not too sure of how you would do this without linux based gateways.
Essentially, I am redoing the whole thing and I've drawn up a map and table for the changes - I just want to be sure of no nasty surprises with the server config - ie is the new NIC IP and scope all that I need to do?
No special reason for /24 - I just want to run each remote site on a separate subnet for ease of identity (eg 10.x.10.x, 10.x.20.x, 10.x.30.x etc)
milly54