HPE FlexNetwork MSR Series - NAT Server for External-To-Internal Access through Domain Name Configuration Example

168
XDMCP : Disabled
Static NAT load balancing: Disabled
# Display NAT session information generated when Host accesses the FTP server.
[Router] display nat session verbose
Slot 1:
Initiator:
Source IP/port: 202.38.1.10/1694
Destination IP/port: 202.38.1.1/21
DS-Lite tunnel peer: -
VPN instance/VLAN ID/Inline ID: -/-/-
Protocol: TCP(6)
Inbound interface: GigabitEthernet2/0/2
Responder:
Source IP/port: 10.110.10.3/21
Destination IP/port: 202.38.1.10/1694
DS-Lite tunnel peer: -
VPN instance/VLAN ID/Inline ID: -/-/-
Protocol: TCP(6)
Inbound interface: GigabitEthernet2/0/1
State: TCP_ESTABLISHED
Application: FTP
Start time: 2012-08-15 14:53:29 TTL: 3597s
Initiator->Responder: 7 packets 308 bytes
Responder->Initiator: 5 packets 312 bytes
Total sessions found: 1
NAT Server for external-to-internal access through domain
name configuration example
Network requirements
As shown in Figure 68, Web server at 10.110.10.2/24 in the internal network provides services for
external users. A DNS server at 10.110.10.3/24 is used to resolve the domain name of the Web
server. The company has two public IP addresses: 202.38.1.2 and 202.38.1.3.
Configure NAT Server to allow external users to access the internal Web server by using the domain
name.