Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I'm having issues opening up a http connection between a host on one interface (higher security level) and a webserver on another interface (lower security level). The webserver is statically mapped to a public ip address, and the host is using inte...
PIX-515E: Version 6.3(5)I'm trying to open a connection to a webserver on the dmz interface from a host on the inside interface and it fails. In this instance the webserver is listening on port 88. I think the problem it is something obvious that I...
The above config changes still fail for the inside interface hosts. Does anybody have an idea why? The (inside) alias line isn't re-writing the dns replies from 66.x.x.x to 172.16.3.4. Why is it not doing this? Anybody?
It still isn't working. The inside interface isn't intercepting the dns-reply for 66.x.x.x and transforming it to 172.16.3.4.here's the sho conn for the inside host initiating the http connection.TCP out 172.16.4.8:3956 in 66.x.x.x:80 idle 0:01:46 B...
Ok, the problem is now partially solved. After looking at the command reference for 6.3, I added these two entries to my pix config:alias (dmz) 172.16.3.4 66.x.x.x 255.255.255.255alias (inside) 172.16.3.4 66.x.x.x 255.255.255.255For hosts on the dmz...
The alias entries returned back with this error:Not enough arguments.Usage: [no] alias [<(if_name)>] []Should the syntax be?:alias (inside) 172.16.3.4 63.x.x.x 255.255.255.255alias (dmz) 172.16.3.4 63.x.x.x 255.255.255.255I'm probably wrong on wha...
