Refresh page: Search for the page again by clicking the Refresh button. The timeout may have occurred due to Internet congestion. Check spelling: Check that you typed the Web page address correctly. The address may have been mistyped. Access from a link: If there is a link to the page you are looking for, try accessing the page from that link.
I solved the issue by registering a record for the external name in my internal DNS and pointing the firwall policy for publishing a mail server to that name, instead of the internal (WINS) name.
I am having trouble enabling a secure area of a website. At first I was getting the "dreaded 500 error". After reading Tom's article I made the changes that it seemed to call for and was able to move on... to a new error. I am now getting the 12206 - proxy chain loop error.
Setup: ISA and IIS are running on the same server. The regular HTTP pages are accessible with no errors. I have the secure pages in their own directory and have that directory setup as its own destination set. I added a line to the HOSTS file to translate the 10.0.0.1 into the www address and restarted the server. Now I am getting the proxy loop error. If I change the Web Publishing Rule for the destination set for the secure folders to Require SSL for published site the error changes to 403 access is forbidden. So I am assuming that the it is being directed back to the "outside" world and trying to come back into the www address a second time when it should be looking to the internal HOSTS file. How can I fix this?
Posts: 2
Joined: 14.Jun.2004
From: Kansas City, MO
Status: offline
Hello,
I finally got ISA and OWA working the way I wanted. After creating a new access rule allowing https from local host to Exchange FE all is well. I would have thought the Publishing mail server wizard would have taken care of this automatically.
I followed the instructions, based on a seperate stand alone CA server, not connected to the Domain I'm working in. Can't do that yet as we still are figuring out how to set up the complete PKI infrastructure and all...
When I open the secure OWA site from the ISA server, I get an error message unlike you showed in the article: "Revocation information for the security certificate for this site is nog available. Do you want to proceed?"
Nevermind the question above... I re-ran the publishing wizard on the ISA server, and now it works fine...
One other question though: Users would like to connect streight to http://owa.domain.tld, without having to add the /Exchange part.
normally one would solve that by using a forwarder in the root of the site (something like an auto refresh) however, standard there is nothing in the webroot itself published. What would be a secure way to fix that?
Posts: 1
Joined: 26.Aug.2004
From: Sydney
Status: offline
Hi Tom, This is indeed a good article. I followed the steps to publish an OWA server but there is a problem: the OWA wizard uses the HTTPS protocol instead of HTTPS Server protocol and I cannot change that. Of course, it doesn't work, is it something else I should check?
Posts: 101
Joined: 8.Feb.2001
From: Farmington Hills, MI
Status: offline
The article was very helpfull, although I get an error at the very last step. I get to the form based authentication page provided by the ISA firewall, but when I enter my UN and PW, I get the following error:
Unknown Request The request could not be resolved by the server.
I tried every variation I could think of on the username: username, domain/username, domain.com/username, domain.local/username.....