I'm planning on changing my IP address range internally from
192.168.1.0/24 to 172.16.16.0/24

Just wondering if there are any well-know gotchas or recomended kb
documents to consult about approaching this process.

I have two DNS servers and one DHCP server in h-house, all running on
Win2003 Sp2.

My current plan is to update dhcp with the new information, then
reconfigure DNS, and manually change static IP addresses for swichtes
and servers, then test the new DHCP leases on the workstations.

Any comments or tips aprecieted.

Hello Jim,

Thank you for your post. This is George and I will be assisting you in this
post.

Please note, change IP network scope will be a very complicated project.
Try some other way if this is not necessary because changing IP network
scope will bring some risk.

Here are some suggestions for your reference.

Important notes:

1. Backup all the DNS and DHCP servers before you make any changes.

2. Please schedule non-business time to perform the IP network change. Make
all these servers offline before making any changes.

3. Related services such as RRAS, ISA (or 3rd party firewalls), etc, should
be adjusted.

Suggestions:
==================

1. Unauthorized the old DHCP server if it has been authorized before.

2. Delete old DHCP scope and then build the new one. You should use the new
network ID when you build the new "DNS Reverse Lookup Zone". Change the
DHCP and DNS server to the new IP address manually.

Please note, the old records in DNS server may last for some time, you can
delete them manually.

3. Change the IP address and DNS server address of Domain Controllers.
Reconnect Domain Controller to the network, restart the Net Logon service
or restart the Domain Controllers.

4. Re-authorize the DHCP server if necessary.

5. Renew IP configuration on all the workstations manually, by using
"ipconfig /release" and "ipconfig /renew". Then re-register all the
workstations' IP address in the DNS server by using "ipconfig /flushdns"
and "ipconfig /registerdns".

You can accomplish this by simply restarting all the workstations.

6. For some shortcuts, or other related applications settings that locate
target computers using their IP address instead of using FQDN, please
adjust them manually.

I hope this can you. If anything is unclear, please feel free to let
me know. I look forward to your reply. Thank you.

Sincerely,
George Yin
Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks !


George Yin(MSFT) wrote:
> Hello Jim,
>
> Thank you for your post. This is George and I will be assisting you in this
> post.
>
> Please note, change IP network scope will be a very complicated project.
> Try some other way if this is not necessary because changing IP network
> scope will bring some risk.
>
> Here are some suggestions for your reference.
>
> Important notes:
>
> 1. Backup all the DNS and DHCP servers before you make any changes.
>
> 2. Please schedule non-business time to perform the IP network change. Make
> all these servers offline before making any changes.
>
> 3. Related services such as RRAS, ISA (or 3rd party firewalls), etc, should
> be adjusted.
>
> Suggestions:
> ==================
>
> 1. Unauthorized the old DHCP server if it has been authorized before.
>
> 2. Delete old DHCP scope and then build the new one. You should use the new
> network ID when you build the new "DNS Reverse Lookup Zone". Change the
> DHCP and DNS server to the new IP address manually.
>
> Please note, the old records in DNS server may last for some time, you can
> delete them manually.
>
> 3. Change the IP address and DNS server address of Domain Controllers.
> Reconnect Domain Controller to the network, restart the Net Logon service
> or restart the Domain Controllers.
>
> 4. Re-authorize the DHCP server if necessary.
>
> 5. Renew IP configuration on all the workstations manually, by using
> "ipconfig /release" and "ipconfig /renew". Then re-register all the
> workstations' IP address in the DNS server by using "ipconfig /flushdns"
> and "ipconfig /registerdns".
>
> You can accomplish this by simply restarting all the workstations.
>
> 6. For some shortcuts, or other related applications settings that locate
> target computers using their IP address instead of using FQDN, please
> adjust them manually.
>
> I hope this can you. If anything is unclear, please feel free to let
> me know. I look forward to your reply. Thank you.
>
> Sincerely,
> George Yin
> Microsoft Online Support
> Microsoft Global Technical Support Center
>
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>

I wouldn't do it unless I really, had to. There are lots of things that could
go wrong.

On the domain controller side, you should change the IP address first, then
configure the new subnet and when done, you should deal with DNS, deleting
all Host A records from the forward lookup zone.

"Jim Helfer" wrote:

> I'm planning on changing my IP address range internally from
> 192.168.1.0/24 to 172.16.16.0/24
>
> Just wondering if there are any well-know gotchas or recomended kb
> documents to consult about approaching this process.
>
> I have two DNS servers and one DHCP server in h-house, all running on
> Win2003 Sp2.
>
> My current plan is to update dhcp with the new information, then
> reconfigure DNS, and manually change static IP addresses for swichtes
> and servers, then test the new DHCP leases on the workstations.
>
> Any comments or tips aprecieted.
>
>

Dear Jim,

Thanks for the reply and I hope everything goes well. Please feel free to
let me know if there is anything else I can do to .

Thank you and have a nice day!

Sincerely,
George Yin
Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.