Network Topology
![]()
Issue Phenomenon
If the mapping to the port is configured on the firewall, only some web pages can be displayed when accessing the external network PC.
Nat server protocol tcp global 9.8.187.128 18888 inside 10.172.10.99 18888 vrrp 5
nat server protocol tcp global 9.8.187.128 18443 inside 10.172.10.99 18443 vrrp 5
And when configure full mapping on the firewall, you can access normally, as follows:
nat server protocol tcp global 9.8.187.128 any inside 10.172.10.99 any vrrp 5
Issue analysis
When the PC accesses the server, the server needs to access some of its own services through the global address of the nat server. The ports of these services do not do the nat server. You need to configure intra-domain NAT to resolve this issue.
1. After configuring
port-based mapping and full mapping, view the session table information. It is
found that the following bidirectional NAT session table appears when
configuring full mapping.
Tcp VPN: public -> public
Zone: trust -> trust TTL: 00:00:10 Left: timeout
Interface: G0/0/0 Nexthop: 10.172.11.249 MAC: 00-00-5e-00-01-17
<-- packets:12 bytes:2297 --> packets:18 bytes:3680
10.172.10.99:46915[9.8.187.128:46915]-->9.8.187.128:18888[10.172.10.99:18888]
2. In addition to accessing the 18888 and 18443 ports, the PC may also access other ports, but the PC captures the PC and does not access other ports of the server.
3. If the PC does not access other ports on the server, then the server must automatically access other addresses. Through packet capture analysis, this is the case, the server will access its own global address, so you need to configure intra-domain NAT or full mapping. Nat server.
4. Successful packet capture, the server 10.172.10.99 will initiate an access to 9.8.187.128, in this case both directions will hit the same nat server, do two-way NAT. Unsuccessful packet capture, because the source port of the initiator is not 18888, it can only hit the forward NAT, so the source address sent to the server at this time is still 10.172.10.99, after the pc receives the message because The request is 9.8.187.128 instead of 10.172.10.99, so there is no response to any message.




