A Forum reader recently asked:
“I found out that a few months down the road I’ll be dealing with new public IP addresses. Can you recommend anything to read? Are there any gotchas, or do you have other sage words for me? The site is moving; we’ll be using the same ISP, but it has to be reprovisioned for various reasons.”
And here’s the response from Caterina Luppi …
You’ll have your hands full. If your server is only doing proxy for your users, the major issue are the filters that will have to be changed to reflect the new address. If you’re using SSL, reverse proxy, internal mail servers, internal web servers, VPN etc, you’re in for a larger amount of work.
First of all, make sure you don’t take shortcuts in the process, since they don’t pay off.
Once you’ve got the new addresses,
1. Disable filtering in inetcfg.
2. Bind the new addresses to your public interface.
3. Change the default gateway and DNS servers and make sure that basic routing works (you can ping the internet, resolve names etc).
4. If that works, configure NAT on the public binding and make sure that a workstation can access the Internet.
5. If you’re using reverse proxy and/or static NAT, add the secondary IP addresses and configure the static assignments.
In the meantime, you might want to start the process of moving the domain from your old ISP to your new one, if they’re the ones who provide DNS resolution for your domain.
Once the filters are done and everything works, you’ve to work on recreating the VPN (if you have it) and the security certificates.
Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment. It just worked for at least one person, and perhaps it will be useful for you too. Be sure to test in a non-production environment.