Hi,

I have to change IP class in a small domain (4 W2K
servers (DNS, DHCP, Exchange, SQL) and 250+ clinets).

My plan is first to shut down all servers, then start the
DC, change IP address to DC, change static addresses in
DNS (also configured on DC) for servers and then start
(and change) all IP addesses on servers. The second step
will be changing address pool on DHCP and changing IP
addresses in Exchange Server.

What do you think about my plan? Would it work or the
things are not so easy?

Thanks, Greg.

This sounds like a better plan than most. I'd leave all the clients logged
in, online, and with current leases, then once everything is changed go
through and do a manual ipconfig /renew before rebooting them. That way,
you;ll still have a relatively working network in case things don't go as
planned on the first try.


"GregS" <(E-Mail Removed)> wrote in message
news:05ec01c3cc9f$c1a6db30$(E-Mail Removed)...
> Hi,
>
> I have to change IP class in a small domain (4 W2K
> servers (DNS, DHCP, Exchange, SQL) and 250+ clinets).
>
> My plan is first to shut down all servers, then start the
> DC, change IP address to DC, change static addresses in
> DNS (also configured on DC) for servers and then start
> (and change) all IP addesses on servers. The second step
> will be changing address pool on DHCP and changing IP
> addresses in Exchange Server.
>
> What do you think about my plan? Would it work or the
> things are not so easy?
>
> Thanks, Greg.
>
>