Anonymous_User Absent Member.
Absent Member.
1274 views

Server Private and Public IP Addresses

We're a small business and currently run two NW65 SP8 servers.

The first server provides Groupwise 7.0.4 and file sharing services. Whilst
the second server runs Bordermanager 3.8 SP5 providing firewall and VPN
services

At long last we're starting to give serious thought to replacing Netware
with NOWS/OES11/Grouwise 2012.

The Bordermanager server is showing its age and will be replaced with a
separate hardware router with built in firewall and VPN services.

Currently the Groupwise/file server just has one NIC configured with a
private IP address whilst the Bordermanager server has two NICs with one
public and one private IP address bound. A secondary IP address is
configured on the public IP address in the BM server and then SMTP firewall
rules and NAT allow mail flow in and out on to the other server running
Groupwise.

The question is when retiring the BM server are there any benefit(s),
security related or otherwise, to configuring the remaining Groupwise server
so that it has two separate NICs with one public and one private IP address
bound to each NIC.

Or with the hardware router/firewall and appropriate rules in place is it
perfectly acceptable just to configure the existing private NIC in the
Groupwise server so that the TCP/IP static route points directly at the
routers IP address.

And we have a range of public IP addresses available from our ISP just in
case that makes a difference.


Labels (2)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Server Private and Public IP Addresses

Apologies not enough caffeine in the system. Posted to wrong group.

"Neil Walkingshaw" <> wrote in message
news:w_Keu.268$bI1.169@novprvlin0913.provo.novell.com...
> We're a small business and currently run two NW65 SP8 servers.
>
> The first server provides Groupwise 7.0.4 and file sharing services.
> Whilst the second server runs Bordermanager 3.8 SP5 providing firewall and
> VPN services
>
> At long last we're starting to give serious thought to replacing Netware
> with NOWS/OES11/Grouwise 2012.
>
> The Bordermanager server is showing its age and will be replaced with a
> separate hardware router with built in firewall and VPN services.
>
> Currently the Groupwise/file server just has one NIC configured with a
> private IP address whilst the Bordermanager server has two NICs with one
> public and one private IP address bound. A secondary IP address is
> configured on the public IP address in the BM server and then SMTP
> firewall rules and NAT allow mail flow in and out on to the other server
> running Groupwise.
>
> The question is when retiring the BM server are there any benefit(s),
> security related or otherwise, to configuring the remaining Groupwise
> server so that it has two separate NICs with one public and one private IP
> address bound to each NIC.
>
> Or with the hardware router/firewall and appropriate rules in place is it
> perfectly acceptable just to configure the existing private NIC in the
> Groupwise server so that the TCP/IP static route points directly at the
> routers IP address.
>
> And we have a range of public IP addresses available from our ISP just in
> case that makes a difference.
>
>



0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Server Private and Public IP Addresses

Hi Neil,

In my GroupWise system we only make use of private IP's and let the Firewall appliance in front of it handle the NATting side of things. But that's just our setup!

Further to that, I setup my GroupWise servers with secondary [private] IP addresses and bind my GroupWise agents exclusively to these secondary IP's. That way, whenever we move the GroupWise system to newer servers the IP's move with the GroupWise system resulting in less reconfiguration and nightmares. Just some food-for-thought!

Hope that helps.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.