GeneralDzur
Technical User
Could you mighty brains please help me here? A client is running a 2600-series router, and I'm supposed to set up a static NAT/PAT translation so a main server in St. Louis can access an internal server here.
Servers 140.175.xx.xx
134.135.xx.xx
Need access to our internal server, 192.168.25.2.
We don't have any ACL's regulating outbound traffic, only a mild firewall ACL regulating inbound traffic. I've set up this command list, is it right for re-directing external (Internet) requests to the internal server, 192.168.7.25?
ip nat inside source static tcp 192.168.25.2 4350 140.175.xx.xx 4350 extendable
ip nat inside source static tcp 192.168.25.2 4351 140.175.xx.xx 4351 extendable
ip nat inside source static tcp 192.168.25.2 5052 140.175.xx.xx 5052 extendable
ip nat inside source static tcp 192.168.25.2 5601 140.175.xx.xx 5601 extendable
ip nat inside source static tcp 192.168.25.2 9998 140.175.xx.xx 9998 extendable
I do not understand Outside Local, Outside Global, Inside Local, Inside Global. I'd really appreciate any help here.
- stephan
Servers 140.175.xx.xx
134.135.xx.xx
Need access to our internal server, 192.168.25.2.
We don't have any ACL's regulating outbound traffic, only a mild firewall ACL regulating inbound traffic. I've set up this command list, is it right for re-directing external (Internet) requests to the internal server, 192.168.7.25?
ip nat inside source static tcp 192.168.25.2 4350 140.175.xx.xx 4350 extendable
ip nat inside source static tcp 192.168.25.2 4351 140.175.xx.xx 4351 extendable
ip nat inside source static tcp 192.168.25.2 5052 140.175.xx.xx 5052 extendable
ip nat inside source static tcp 192.168.25.2 5601 140.175.xx.xx 5601 extendable
ip nat inside source static tcp 192.168.25.2 9998 140.175.xx.xx 9998 extendable
I do not understand Outside Local, Outside Global, Inside Local, Inside Global. I'd really appreciate any help here.
- stephan