I take it that "POS" really means "point of sale", not what one might imply from an app that behaves this way? :) You can use a "fake HTTP" protocol (and properly-ordered rules) as described in this isablog<http://blogs.technet.com/b/isablog/archive/2006/09/25/why-do-i-need-a-deny-rule-to-make-an-allow-rule-for-a-custom-protocol-work-correctly.aspx> to work around such silliness. Please send me the case number (offline if you like) - there's a support engineer that needs some education. From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Crockett, Gregory Sent: Tuesday, June 14, 2011 7:22 AM To: isalist@xxxxxxxxxxxxx Subject: [isalist] Application not proxy-aware Hello, I have an application, Radiant Systems Aloha - POS system, that phones home so that those at home can monitor the application. The phoning home agent uses port 80. ISA 2k6 sees the traffic as non-HTTP traffic - so it is dropped. I tried bypassing ISA with unchecking "Web Proxy Filter". That did not work. The monitor reports the data as invalid. PSS suggest to bypass ISA altogether - link directly to the Internet. PSS also mentioned that even though Web Proxy Filter is unchecked, ISA will always treat the traffic with Web Proxy Filter -- I might have misunderstood. The ISA server also as WebSense -- disabling yields the same results. Has anyone come across this? TIA Greg Crockett