I almost never use the web browser on ISA. However, I need to do it in my case to debug. If the ISA server can't connect to a given port on the internal machine, then I have no chance of letting it gate traffic. :) It appears that Server Publishing my internal SSL port works if I can use a DNS name to get to the resource, but not if I use the raw IP number. Right now I am only publishing a single SSL port on the ISA server, should any secondary ports be opened? Thanks. ---orig Subject: RE: SSL High Port Publishing Issue From: "Thomas W Shinder" <tshinder@xxxxxxxxxxxxxxxxxx> Hi Steve, =20 SAFETY TIP: Test from external client only and NEVER, I repeat NEVER use the browser on the firewall. If you need to use a browser on the firewall, run it from the pix ;-) =20 NOTICE: This communication, including attachments, is information that is confidential and may be privileged. It constitutes non public information intended to be conveyed only to the designated recipient(s). If the reader or recipient of this communication is not the intended recipient, an employee or agent of the intended recipient who is responsible for delivering it to the intended recipient, or if you believe that you have received this communication in error, please notify the sender immediately by return email and promptly erase this email including attachments without reading or saving them in any manner. The unauthorized use, dissemination, distribution or reproduction of this email, including attachments, is prohibited and may be unlawful. Receipt by anyone other than the intended recipient(s) is not a waiver of confidentiality or privilege by the sender.