The HQ network is using PAT to gain access to the internet, the internal webserver needs to be accessed from the internet using static NAT.
! interface FastEthernet0/1 switchport access vlan 10 ! interface FastEthernet0/2 switchport access vlan 20 ! interface FastEthernet0/3 switchport access vlan 30 ! interface GigabitEthernet0/1 switchport mode trunk !
! interface GigabitEthernet0/0 no ip address duplex auto speed auto ! interface GigabitEthernet0/0.10 encapsulation dot1Q 10 ip address 192.168.10.1 255.255.255.0 ip nat inside ! interface GigabitEthernet0/0.20 encapsulation dot1Q 20 ip address 192.168.20.1 255.255.255.0 ip nat inside ! interface GigabitEthernet0/0.30 encapsulation dot1Q 30 ip address 192.168.30.1 255.255.255.0 ip nat inside ! interface Serial0/0/0 ip address 22.214.171.124 255.255.255.0 ip nat outside clock rate 2000000 ! ip nat pool PAT 126.96.36.199 188.8.131.52 netmask 255.255.255.0 ip nat inside source list PAT pool PAT overload ip nat inside source static tcp 192.168.30.10 80 184.108.40.206 80 ip route 0.0.0.0 0.0.0.0 Serial0/0/0 ! ip access-list standard PAT permit 192.168.0.0 0.0.255.255 !
! interface GigabitEthernet0/0 ip address 172.16.1.1 255.255.255.0 duplex auto speed auto ! interface Serial0/0/0 ip address 220.127.116.11 255.255.255.0 ! ip route 0.0.0.0 0.0.0.0 Serial0/0/0 !
All PC's are configured correctly, yet pinging from any VLAN inside the HQ network to the customer leads to a timeout, no translations are being made stating the
show ip nat translations command.
However, static NAT seems to be working fine visiting 18.104.22.168 in the browser on the customer PC.
By removing and reapplying static NAT the problem seems to be gone, but after reopening Packet Tracer the problem is back again, it makes no sense to me...
Am I overseeing something or could this be a bug in Packet Tracer?