Hi Stefaan, That's got to be the whackieist KB article I've ever seen for a hotfix package. The only issue it fixes is with SSL tunneling on different ports, and I didn't even know there was an issue with that! :) I entered a tasteful comment on the page so maybe someone will read it someday. Thomas W Shinder, M.D. Site: www.isaserver.org Blog: http://blogs.isaserver.org/shinder/ Book: http://tinyurl.com/3xqb7 MVP -- ISA Firewalls > -----Original Message----- > From: isapros-bounce@xxxxxxxxxxxxx > [mailto:isapros-bounce@xxxxxxxxxxxxx] On Behalf Of Stefaan Pouseele > Sent: Saturday, July 08, 2006 7:27 AM > To: isapros@xxxxxxxxxxxxx > Subject: [isapros] Configuring Direct Access in ISA 2004 SP2 > > Hey guys, > > we all know that ISA Server 2004 SP2 makes some changes to > the way that > destinations specified for direct access are handled. What > *exactly* has > changed is described in > http://support.microsoft.com/default.aspx?scid=kb;en-us;903746. > > In February 2006, I made a PSS call to fix that issue and > received a private > fix. The 'trick' was a modified wpad.dat script that allows > the use of URL's > to specify direct access (e.g. '*.microsoft.com/*') without > breaking the > changes introduced in SP2 for the branch office scenario's. > Unfortunately, > the private fix was broken by > http://support.microsoft.com/?kbid=916106. > > According to last post (Sunday, June 18, 2006 3:56 AM) at > https://blogs.technet.com/isablog/archive/2006/02/27/420653.as > px there is a > fix for the Direct Access issue, which you can get by calling Product > Support and requesting the fix for KB 920716. On July 5, 2006 > the KB was > released with the title "Description of the ISA Server 2004 > hotfix package: > June 6, 2006" > (http://support.microsoft.com/default.aspx?scid=kb;en-us;92071 > 6). However, I > can't find any reference to the Direct Access issue! > > Has any body some more info about it? > > Thanks, > Stefaan > > > >