We have a PIX firewall, ver 5.3, a DMZ (192.168.0.0) and an internal (token ring) 126.96.36.199 network. One of our applications needs to have two servers in our DMZ have the ability to communicate via email. Both servers are IP'd in the DMZ but have static commands to an outside IP in the PIX. Apparently, email was functional between these two systems prior to putting them behind the PIX. Since they now have to use IP addresses (either internal or external) for access, this function is no longer available and is necessary. I entered the alias commands which I thought were correct (based on my reading) but they did not work. Could anyone give me a hand here? I surely would appreciate it! Thanks, Carolyn
The reason I ask is that I did encounter some copies in which the alias command didn't work.
For example, I could ping our web server in the DMZ by name and get the public IP address returned. But as soon as the alias command was entered, then I got no replies at all when I was expecting to see it's private IP address.
Now at the time I think I was using 5.25 and also 5.31.
When I queried the TAC I was informed that this was a problem caused by 5.25 and told to switch to 5.26 and that cured the problem for both copies.
In which case try a newer version of the software.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...