It could be due to your ISP doing some caching on TCP80 (WWW) port, esp. happens if you are using dial-up account, you should be using any port other than TCP80.
For IPsec/udp you need to open up IPsec/UDP (port configured) on the PIX FW, and UDP500 (ISAKMP) port as well, but if you are trying to use more than one client behind the PIX at the same time, then IPSec/UDP is not a solution for you, use IPsec/TCP instead.
Sounds like a NAT/PAT issue. Are you doing PAT for your clients on the router? You will need to have static 1-to1 NAT translations. IPSEC over tcp isnt a feature that works to the pix, only to a 3000 concentrator. That should be up and coming when 6.3 is released, talk to you local account manager on details of that. But until then, when connecting to the pix you will need to do a 1-to-1 static NAT translation.
Currently only the vpn3000 concentrators support ipsec over tcp/udp. You will need to have a static address for each client behind your router pat device to connect to the pix. If your running 12.2.5T you can set up a one to one esp nat translation that will allow one of your 2 clients to connect to the pix without the additional public ip's.
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...