Windows 2000/2003 IP Subnet change and concern over impact in AD e

Dear all,

We have a Windows 2000 and 2003 network with XP clients, network printers
etc, and a fairly straightforward firewall and dsl router for Internet
connectivity. Nothing much more than file and print going on, and the usual
Active directory on the two DC's, one w2k and one w2k3 server. Current Ip
subnet is 172.16.0.0/16

My question is, does anyone know if there will be any problems changing the
IP subnet to 172.16.1.0/24 ??

The DHCP scopes, and static IP's would be changed accordingly, but wondered
if Active Directory or the DNS etc might have a hissy fit with the change??

Any thoughts muchg appreciated as I could do without them throwing a strop

PS the reason for the change is to allow a site to site vpn to work
properly, current 172.16 subnet is too broad and will prevent traffic from
going over the link to the 172.16.2.0 network

cheers

Hi JonP

Well, I recently conducted an IP change similar to the one that you are
planning and most things ran very smoothly. The only problem that I
encountered was with printer port mapping. If you are using network printers
then you may need to change the IP mapping of the printer ports as I have
known them to go haywire.

Also if you are using firewalls with exception rules, such as Symantec
Client Firewall, use the central administration to allow the new subnet to
operate before you change the Ip otherwise you may loose connectivity with
the server and end up needing to do it manually.

As far as DNS goes, it should automatically accept the new DNS information
from the DHCP Service. It might be worth checking on the DNS properties to
ensure that Dynamic updating is enabled.

Other than that there should be no problems, just make sure u do it when no
essential network activity is going on!

Brendan

"JonP" wrote:

> Dear all,
>
> We have a Windows 2000 and 2003 network with XP clients, network printers
> etc, and a fairly straightforward firewall and dsl router for Internet
> connectivity. Nothing much more than file and print going on, and the usual
> Active directory on the two DC's, one w2k and one w2k3 server. Current Ip
> subnet is 172.16.0.0/16
>
> My question is, does anyone know if there will be any problems changing the
> IP subnet to 172.16.1.0/24 ??
>
> The DHCP scopes, and static IP's would be changed accordingly, but wondered
> if Active Directory or the DNS etc might have a hissy fit with the change??
>
> Any thoughts muchg appreciated as I could do without them throwing a strop
>
> PS the reason for the change is to allow a site to site vpn to work
> properly, current 172.16 subnet is too broad and will prevent traffic from
> going over the link to the 172.16.2.0 network
>
> cheers
>