Hi Ben, I wasn't trying to goad you (yet) into installing the Firewall client. What I was trying to determine is if the clients were configured as Web proxy clients. Since Web proxy clients are configured to forward connections to the Web proxy service, and if the Web proxy service has a rule that allows outbound HTTP, the ISA firewall doesn't care what port the destination HTTP connection is made on, all it cares about is HTTP. So, you don't need to create a new protocol definition to support the Web proxy clients. I suspect what happened was that when you installed the Firewall clients, the Web proxy client configuration took place automatically and that's why things worked (IIRC my ancient ISA2k knowledge). HTH, Tom Thomas W Shinder, M.D. Site: www.isaserver.org <http://www.isaserver.org/> Blog: http://spaces.msn.com/members/drisa/ Book: http://tinyurl.com/3xqb7 <http://tinyurl.com/3xqb7> MVP -- ISA Firewalls **Who is John Galt?** ________________________________ From: Ben Schorr [mailto:bens@xxxxxxxxxxxxxxxx] Sent: Tuesday, January 10, 2006 5:20 PM To: [ISAserver.org Discussion List] Subject: [isalist] RE: Accessing Port 81? http://www.ISAserver.org O.K., I went ahead and installed the Firewall Client on the workstations that needed to access this site and that works fine. Good enough - like I said, only maybe 2-3 workstations in the whole org need to access this site so it's fine. Thanks! Ben M. Schorr Chief Executive Officer ______________________________________________ Roland Schorr & Tower 737 Bishop St. Suite 1655 Honolulu, Hawaii 96813 Mobile: 808-782-6306 Fax: 808-533-3677 www.rolandschorr.com <http://www.rolandschorr.com/> bens@xxxxxxxxxxxxxxxx ________________________________ From: Thomas W Shinder [mailto:tshinder@xxxxxxxxxxx] Sent: Tuesday, January 10, 2006 12:21 PM To: [ISAserver.org Discussion List] Subject: [isalist] RE: Accessing Port 81? http://www.ISAserver.org Hi Ben, Are these Web proxy clients that are having the problems? Tom Thomas W Shinder, M.D. Site: www.isaserver.org <http://www.isaserver.org/> Blog: http://spaces.msn.com/members/drisa/ Book: http://tinyurl.com/3xqb7 <http://tinyurl.com/3xqb7> MVP -- ISA Firewalls **Who is John Galt?** ________________________________ From: Ben Schorr [mailto:bens@xxxxxxxxxxxxxxxx] Sent: Tuesday, January 10, 2006 4:09 PM To: [ISAserver.org Discussion List] Subject: [isalist] Accessing Port 81? http://www.ISAserver.org I've Googled this and tried a few things (like adding the SSLPortListMembers registry key) but so far with zero success. I have a client who's LAN is behind an ISA 2000 box. They need to access a website that is located on port 81 but it simply won't connect to it. I tried creating a protocol definition for it, but no luck. Any tips would be appreciated. The site they are trying to reach is in the format of: http://server.domain.com:81/sites/directory/page.aspx And it works fine for machines at other sites who are not behind this ISA 2000 box so I assume it's ISA blocking the access. Thanks for any suggestions. Ben M. Schorr Chief Executive Officer ______________________________________________ Roland Schorr & Tower 737 Bishop St. Suite 1655 Honolulu, Hawaii 96813 Mobile: 808-782-6306 Fax: 808-533-3677 www.rolandschorr.com <http://www.rolandschorr.com/> bens@xxxxxxxxxxxxxxxx ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA <http://www.webelists.com/cgi/lyris.pl?enter=isalist%0bISA> Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA <http://www.isaserver.org/pages/newsletter.asp%0bISA> Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Visit <http://www.isaserver.org/pages/larticle.asp?type=FAQ%0b---------------- --------------------------------------%0bVisit> TechGenix.com for more information about our other sites: http://www.techgenix.com ------------------------------------------------------ You <http://www.techgenix.com%0b-------------------------------------------- ----------%0bYou> are currently subscribed to this ISAserver.org Discussion List as: tshinder@xxxxxxxxxxxxxxxxxx To <mailto:tshinder@xxxxxxxxxxxxxxxxxx%0bTo> unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report <http://www.webelists.com/cgi/lyris.pl?enter=isalist%0bReport> abuse to listadmin@xxxxxxxxxxxxx ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA <http://www.webelists.com/cgi/lyris.pl?enter=isalist%0bISA> Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA <http://www.isaserver.org/pages/newsletter.asp%0bISA> Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Visit <http://www.isaserver.org/pages/larticle.asp?type=FAQ%0b---------------- --------------------------------------%0bVisit> TechGenix.com for more information about our other sites: http://www.techgenix.com ------------------------------------------------------ You <http://www.techgenix.com%0b-------------------------------------------- ----------%0bYou> are currently subscribed to this ISAserver.org Discussion List as: bens@xxxxxxxxxxxxxxxx To <mailto:bens@xxxxxxxxxxxxxxxx%0bTo> unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report <http://www.webelists.com/cgi/lyris.pl?enter=isalist%0bReport> abuse to listadmin@xxxxxxxxxxxxx ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Visit TechGenix.com for more information about our other sites: http://www.techgenix.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: tshinder@xxxxxxxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx