Ah, okay, this makes much more sense. Can I summarize it by saying that when browsing the web without using a proxy, it returns a slightly different URL with ISA2004 than it did with ISA2000, which confuses the SurfControl plug-in, causing it to ignore the request? -----Original Message----- From: David Farinic [mailto:davidf@xxxxxxx] Sent: Sunday, April 03, 2005 10:25 To: [ISAserver.org Discussion List] Subject: [isalist] RE: SurfControl & SNAT http://www.ISAserver.org >>Okay, so why do you think it worked with ISA2000, but not with ISA2004? >It didn't. This is the most probable reason why it might work for ISA2000 and not for ISA2004: One of the differences: Example request with URL: http://xxx.com/test.txt from SNAT client ISA proxy function for plugins: GetServerVariable(pfc,"URL",&url[0],&dwSize)) Returns for SNAT&FW client On ISA2004: "/test.txt" On ISA2000 same function for same clients returns: "http://xxx.com/test.txt"; This change has to be considered by any ISA ISAPI Proxy plug-in working with URLs. Regards David Farinic. P.S.: IMHO user credentials are not in question here as problem is that they don't see URL which breaks everything. User's credentials don't as u can still deploy "filter [SEX sites] for all clients" scenario.