Is it possible to forward port 443 to an internal server with the same IP used for dynamic NAT
I have taken over management of a Cisco ASA device (v8.2), and I am trying to open up one of the sites on the internal server to be available on the Internet via port 443. The problem is, the public IP that I thought was available is actually being used for dynamic NAT for the internal network. I'm wondering if it is possible to still use that same IP for the static NAT/PAT to the server. On the one hand, it seems like it might work, since the port forward only needs port 443, but on the other hand, I'm not sure if having two NAT rules using the same public IP will just cause a conflict, and I don't want to try it and bring down the network, so I was wondering if anyone has experience with this, and if this is not possible, is there another workaround?
I read this, which is what I want to do... but I just am not sure about the ramifications of using the existing IP:
2nd edit: I went ahead and added it under Public Server (it added the static NAT - no port specified, and the rule 'any public_ip https allow,' but traffic still isn't getting through. When I look at the logs, it says it's being denied by access-group "inside_access_out," which just has an implicit 'any any ip deny' rule, but I am not sure what it needs.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.