DNS is by domain names (zones), not IP addresses, so DNS won't be an issue
IF you have all of your workstations registering themselves. But since
you'll have to visit the workstations to change their IP addresses anyway, I
would install DHCP on the server, set up a scope for your new IP range -
like 192.168.1.20 - 254, leaving enough out for static devices like servers,
printers, routers, etc. Make sure you set your DHCP to register IP address
leases in DNS. Then when you visit your clients, just set them for DHCP
(make sure the DHCP server is disabled on your NAT router). Do an ipconfig
/renew and verify that you get an IP address in the proper range. Should be
all done. Then next time you need to expand it'll take you 10 minutes (plus
printers).
....kurt
"Steve Keogh" <(E-Mail Removed)> wrote in message
news:5DC37D91-65B3-4C33-9BCC-(E-Mail Removed)...
> This may be a little convoluted. I inherited a small network with a new
> job.
> A single server running WIN 2000 Advanced, clients all run WIN XP Pro.
> All
> service packs etc. installed.
>
> The server is the DC, and also runs the DNS with AD. The network is on
> static IP's to facilitate outside IT support. We no longer use the
> outside
> tech company. We have run out of available IP address through growth.
>
> I would like to move the network to a private address scheme(192.168.1.0
> with a subnet of 255.255.255.0) with NAT routing enabled on our ISP's
> router(router would have address 192.168.1.1) and then run DHCP on our
> server. I need help in migrating the server form the old static address
> to a
> static address in the new scheme, and keep DNS etc. working. Anyone have
> any
> ideas?
>
|
Similar Threads
