That error response can only be obtained when web publishing. IIS response is quite different. You probably were using the ISA_Redirects tool or something similar and forgot to move it to the new server. The good news is that in ISA 2006, such custom mechanisms aren't required. In the listener "Connections" tab, you can opt to redirect anonymous or authenticated HTTP connections to HTTPS. From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Roy Tsao Sent: Monday, January 29, 2007 1:18 AM To: isalist@xxxxxxxxxxxxx Subject: [isalist] Re: Publishing in ISA2006 Original publishing is SSL bridge or tunneling? ----- Original Message ----- From: Ball, Dan <mailto:DBall@xxxxxxxxxxx> To: isalist@xxxxxxxxxxxxx Sent: Monday, January 29, 2007 10:40 AM Subject: [isalist] Publishing in ISA2006 When I upgraded ISA2004 to ISA2006, my published webserver and Exchange server no longer worked. Browsing to the website gave me this error: Error Code: 403 Forbidden. The page must be viewed over a secure channel (Secure Sockets Layer (SSL)). Contact the server administrator. (12241) Typing https:// into the URL allowed the traffic to flow. The only way I could get it to work was to enable the "Redirect authenticated traffic from HTTP to HTTPS" option in the web listener. This works because it redirects all web traffic to HTTPS. However, it doesn't work for all pages, we have a few pages that have problems, and have had reports from some people that cannot access the website at all. So, I need to get this working properly again. I've deleted all of the publishing rules and the web listener several times, recreating everything from scratch; it still gives me the same error. I've followed every tutorial I could find, it appears that I'm doing it correctly. There must be some little detail that I'm missing with ISA2006. Probably something obvious, but it is eluding me... Anyone have any ideas? All mail to and from this domain is GFI-scanned.