If you are running DNS inside your network, you can essentially fool the internal users to point to the inside address of the webserver. If not, the problem lies in the fact that your internal machine goes out through the pix, resolves the address a...

i would hope that you have more than one public ip right?? if you do not, this will be a pain. The idea is to static a public ip to an internal ip, set the ACL for permissions and bind it either to the ip or the interface - depends on which command...

Usually a solution is based on # of hosts, # of networks, speed, capabilities, security of the device and the list goes on and on. you might want to check out www.securehq.org. They review everything security and might give you some better insight.

Do you guys look at the TAC center or what? Please look at http://www.cisco.com/warp/public/110/mailserver_in.html. you need to have a static as well as an ACL, or a conduit opening pop3 and smtp INBOUND. It looks from above that you have it enabl...

This sounds like one of those "I setup Windows 2K with DNS inside my network and I'm assuming that the rest of the world can see it" syndrome. Your internal users are looking at your internal DNS - which lists your domain. It does not sound like yo...