Clicking the NAT Info option will take you to the screen shown below.
This page displays information about the IP addresses that the local Corente Virtual Services Gateway is using for Network Address Translation (NAT). When connecting locations for your Corente network, overlapping IP addresses will create a problem. If two networks in different locations contain IP addresses in the same address space, packets will not get routed to the appropriate computers. NAT can be used to solve this problem.
This page allows an administrator to check the NAT settings for the local Location gateway and determine what addresses the Location gateway is using to NAT each local or remote subnet, according to how NAT has been enabled for this Location gateway in the App Net Manager application.
The information is divided into categories for each NAT option: Outbound NAT and Auto Resolve/Inbound NAT.
Outbound NAT is enabled on the local Corente Virtual Services Gateway for local subnets that are participating in the Corente network. A Corente network administrator identifies a local subnet that the Corente Virtual Services Gateway will NAT to another subnet before the subnet is made visible to remote Corente network partners. The administrator is able to specify the subnet that will be used for NATing.
The User Group column lists the real IP addresses and netmasks of all local subnets that are participating in the Corente network.
If Outbound NAT has been specified for a local subnet, the NAT column will display the NATed IP address of that subnet. (This is the subnet of IP addresses that Corente network partners will use to make connections to the machines.) If Outbound NAT has not been enabled for this subnet, the column will display "N/A" and Corente network partners will use the real IP addresses of the machines for Corente network connections.
To facilitate data viewing, you can sort the entries in this table by User Group subnet or by NAT subnet simply by clicking on the headings at the top of each column. The entries will be sorted in order, from lowest to highest subnet.
If there are any Corente Clients that connect to this Location gateway, any subnets that are being NATed by Outbound NAT will be listed twice. One entry will list the subnet as NATed, the other entry will not. This occurs because NAT does not function between Corente Client partners and their host Location gateway. Corente Clients connect to the Location gateway like local clients rather than remote partners, so they connect to servers using real IP addresses.
Auto Resolve/Inbound NAT are enabled on the local Corente Virtual Services Gateway for each partner. Inbound NAT will re-map all IP addresses in the partner's User Group to a new set of addresses that have been chosen by a Corente network administrator, while Auto Resolve NAT will automatically perform NAT if a conflict is detected between the User Group of the local Location gateway and the User Group of the partner. If an IP address conflict is detected when Auto Resolve is enabled, the local Corente Gateway will NAT the partner's subnets to a new subnet (chosen by the Location gateway) so that local machines will be able to access computers in the partner's User Group. Both types of NATing will only occur locally; the NAT will be invisible to the remote computers.
The Partner column lists the fully-qualified name of the partner (i.e.,
domainname.gatewayname) that is participating in NAT-Internal with the local Location gateway.The User Group column lists the real IP addresses and netmasks of the subnets of this Location partner. (Depending upon what is included in the Location partner's User Group, there may be multiple subnets per partner.)
The NAT column will display the NATed IP addresses of these subnets. Local computers will use these translated IP addresses for Corente network connections.
Auto Resolve NAT partners will not be listed unless Auto Resolve NAT is currently occurring with this partner. In order for Auto Resolve NAT to solve addressing conflicts between two partners, it must be enabled on both sides of the connection (i.e., both the local Location gateway and the Location partner must enable Auto Resolve for each other).
To facilitate data viewing, you can sort the entries in this table by Partner, User Group subnet, or by NAT subnet simply by clicking on the headings at the top of each column. The entries will be sorted in order, either alphabetical (for Partner entries) or from lowest to highest subnet (for User Group or NAT entries).