One thing I'm not sure of: Your internal user will access the internet over nat/global statements. The configured static allows traffic from the internet to the inside host. Is this really what you want?
Check the output from "show conn local 192.168.1.110 det". The flags on connections will indicate connection type and if you have something to correct.
Also one workaround would be to reduce the timeout allowed for udp conns.
If you are having problems with P2P users, you would probably want to invest in something that can filter that kind of traffic. Products like Websense will integrate with the PIX firewall and block access to P2P sites, and the Websense network agent will be able to block or throttle P2P traffic.
The PIX firewall is mainly designed to be a firewall and not a content filter, which is why Cisco partners with companies like Websense and N2H2.
I do have a traffic shaper in place. A great product named AstroFlow. I don't need content filtering but proper connection management for TCP and UDP.
Even though P2P is shaped, there are hundreds of UDP "connections" per user and that's what I am trying to get control of. PIX is limiting TCP connections on a per user basis fine but I can't seem to prevent my state table of filling up with UDP entries.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...