changing public IP addresses for Border 3.9

[Siuslaw]

In article <Siuslaw.3uo59z@no-mx.forums.novell.com>, Siuslaw wrote:
> Have 2 servers running Netware 6.5 sp2, set up July 2007. Server one
> has GroupWise 6.0. Server 2 has BorderManager 3.9. Changing ISPs, have
> to change public IP addresses. Consultant not available.


Well, I know of one who is!
> Read Novell
> BorderManager Admin & Troubleshooting Guides, also Craig Johnson's
> BorderManager 3.9 Lite. Also found TIDs 3435980, 3083890, &10052520 &
> have been browsing this site's forums all day. Looks like a lot of
> settings need to be changed, not sure of the order. Also, no iManager
> on either server. Install & use or work from console in inetcfg.nlm,
> filtcfg.nlm, etc.?
> Thanks.

You need iManager to change proxy addresses, vpn addresses and access
rules. The access rules probably don't call out the old public IP
addresses. The proxy will work for outbound even with the old public IP
in the config, but if you are using reverse proxy or generic proxies, you
must change them. (I'd immediately start working on getting an iManager
2.7.2 working on one or both servers, and perhaps have a mobile iManager
on your PC as well). VPN needs iManager, but if you're not using VPN you
don't have to worry about that.

What needs to be changed are settings in INETCFG and FILTCFG, and your
public DNS records for sure for your inbound SMTP to GroupWise. You will
also need to have a PTR record set up for your outbound email address.
If you don't do this, your inbound email will stop, and without the ptr
record, some of your outbound email will be rejected. The filters can be
changed, but I prefer to duplicate the ones calling out the public IP. (I
usually have time to set up both new and old links at the same time and go
back and forth for a while to test. Alternatively, you can just unload
filters for a short test to the new IP address. Don't forget to change
the default route (or set up both, and dead gateway protection) and don't
use NAT on both public addresses at the same time.

I do this a lot. In fact I just did it for a law firm this morning. Give
me a call if you need help - my contact info is at my website.

Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to Craig Johnson Consulting - BorderManager, NetWare, and More ***

Thanks, Craig.

I had checked your site and thought you might be out of the country still.

A couple of things: We do not have a VPN. New ISP has assigned three static IP addresses and configured the Cisco ME 3400-2CS Layer 3 metro ethernet switch to have 2 vLans, one for public traffic (this is a public library district main branch-not part of any city, county, etc, so this "accidental IT person"/librarian takes care of LAN), one for staff traffic (some of which has to point at a county firewall to get to a remote server for all library catalog services) and one for GroupWise traffic which will still point to current address, also going through that county firewall.

Spent quite a bit of time last few days going through posts in BorderManager and iManager forums. Seems like iManager 2.7 has a lot of problems. Since we don't have any version of iManager on either server, and since it looks like it is a problem to go down to 2.6 if 2.7 causes problems, would it be better to load 2.6?

Main question: Order of changes. Do Netware server first, then GroupWise, then BorderManger, right? Make changes in INETCFG first, then FILTCFG, then proxies, right? How about DNS entries? Does it matter if they are changed before or after filters, proxies?

I am not trying to do this alone. I do have a person coming in who works with Netware at the local community college, but he doesn't have BorderManger experience. I gave him a copy of your BorderManager 3.9 lite book and he has been reading it.

Linda Weight
lweight@siuslaw.lib.or.us
1-541-997-3132 x 208