05-05-2013 04:12 AM - edited 03-11-2019 06:38 PM
Hi there,
I have a Cisco ASA 5505 in my home office which has a few PCs behind it with a linux web server running some websites. I can access the websites from outside no problem (i.e. on my iPhone using a 3G connection). However, I struggle to access the websites from within the network. The ASA gives me this error:
6 | May 05 2013 | 11:52:27 | 192.168.55.61 | 50420 | Failed to locate egress interface for TCP from inside:192.168.55.61/50420 to 86.*.*.*/80 |
ASA runs version 9. Here is the config bit:
object network denon-server
host 192.168.55.200
access-list outside_access_in extended permit tcp any object denon-server eq www
object network denon-server
nat (any,outside) static interface service tcp www www
Any suggestions?
Solved! Go to Solution.
05-05-2013 07:34 AM
Hi,
I assume that you are trying to reach the LAN server with the public IP address that the ASA holds and also uses for the above Port Forward / Static PAT configuration?
If this is the situation then I am afraid that with the current configuration that is not possible. The NAT configuration towards Internet is done between probably "inside" and "outside". So "outside" interface holds the public IP address. ASA doesnt let you connect to that "outside" IP address from behind the "inside" IP address. (Or any other interface for that matter)
What you could try to do is configure a NAT that would enable you to use the public IP address of the server even when connecting from the "inside" of ASA.
Try this
object network SERVER-LOCAL
host 192.168.55.200
object network SERVER-PUBLIC
host 86.x.x.x
object network LAN
subnet 192.168.55.0 255.255.255.0
nat (inside,inside) source dynamic LAN interface destination static SERVER-PUBLIC SERVER-LOCAL
Where
Check that the network mask is correct for the LAN and fill in the public IP address.
The actual NAT configuration tells the ASA this
This should enable the LAN hosts to use the public IP address to connect to the server. The server though will see the connections coming from the ASA "inside" interface IP address.
Hope this helps
Please remember to mark a correct reply as the correct answer if it did answer. And/or rate helpfull answers
Ask more if needed.
- Jouni
05-05-2013 07:34 AM
Hi,
I assume that you are trying to reach the LAN server with the public IP address that the ASA holds and also uses for the above Port Forward / Static PAT configuration?
If this is the situation then I am afraid that with the current configuration that is not possible. The NAT configuration towards Internet is done between probably "inside" and "outside". So "outside" interface holds the public IP address. ASA doesnt let you connect to that "outside" IP address from behind the "inside" IP address. (Or any other interface for that matter)
What you could try to do is configure a NAT that would enable you to use the public IP address of the server even when connecting from the "inside" of ASA.
Try this
object network SERVER-LOCAL
host 192.168.55.200
object network SERVER-PUBLIC
host 86.x.x.x
object network LAN
subnet 192.168.55.0 255.255.255.0
nat (inside,inside) source dynamic LAN interface destination static SERVER-PUBLIC SERVER-LOCAL
Where
Check that the network mask is correct for the LAN and fill in the public IP address.
The actual NAT configuration tells the ASA this
This should enable the LAN hosts to use the public IP address to connect to the server. The server though will see the connections coming from the ASA "inside" interface IP address.
Hope this helps
Please remember to mark a correct reply as the correct answer if it did answer. And/or rate helpfull answers
Ask more if needed.
- Jouni
05-05-2013 10:19 AM
Awesome, thank you very much. This has solved my problem!
05-05-2013 11:17 AM
Hi,
Glad to hear it works now
- Jouni
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide