OWA https redirect error - Not working on inside

[shakamon]

I have my OWA working great from the internet using forms based authentication and https redirect.

However, when trying to acess OWA from my internal network, it seems as though the https redirect is hanging.

In the botton screen left there is a message causing the IE browser to hang up:
Waiting for

https://webmail.xxxx.com/exchweb/bin/auth/owalogon.asp?url=https://webmail.xxx.com/exchange&reason=0

It blinks like it is trying to load, but just cannot. Its like it just wont authenticate

Also of note, It won't display any of the logos either.

"Only the dead fish follow the stream"

 

[58sniper]

Do you have a DNS forward lookup zone for xxx.com, and an A record for webmail in your internal DNS?

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[shakamon]

I had it as a cname, then changed it to an a record. Even tried point it towards the external IP address. All the same results. The a record points to

http://webmail.xx.com

When I changed it to hit the external IP, wanna here af funny thing here? It works fine in firefox 2.0 fine from the inside. STill from IE 6 and 7.0 it just seems to hang.

The fact that is wont show the logos either I believe is related here. COuld it be the http redirect or cert issue. Maybe even a perms issue?

"Only the dead fish follow the stream"

 

[58sniper]

let's take it to the bare basics. kill the redirect, clear your cache, and try

http://webmail.xx.com/exchange

from inside.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[shakamon]

No luck. With cleared cache, and tested from a never before used system even.

Let me explain the exact behavior.
The outside clients are having issues seeing the images (logo_Nav.gif and logi_microsoft.gif and our company logo)on the initial form as well as the internal clients.

Internal IE 6 and 7 clients cannot login from the inside as as something is hanging. From the outside Firefox, IE 6 and 7 are fine.

On the inside, firefox does not show above gif,but lets you log in. If you browser back, the images are there.

Currently I have the internal clients pointing to the external IP DNS wise. Even as a caname or a record, behavior is the same. Totally kooky like its an IE rendering issue somewhere.


Here it the redirect statement:

https://webmail.xxx.com/exchange

with: exact URL entered above and a permanent redirection for this resource radio buttons checked.

With the redirect turned off,I had it go to the designated file, no luck. because of the SSL cert it wouldn't even print the page.

The page must be viewed over a secure channel
The page you are trying to access is secured with Secure Sockets Layer (SSL). 
--------------------------------------------------------------------------------

Please try the following:

Type https:// at the beginning of the address you are attempting to reach and press ENTER. 
HTTP Error 403.4 - Forbidden: SSL is required to view this resource.
Internet Information Services (IIS)

"Only the dead fish follow the stream"

 

[shakamon]

No luck. With cleared cache, and tested from a never before used system even.

Let me explain the exact behavior.
The outside clients are having issues seeing the images (logo_Nav.gif and logi_microsoft.gif and our company logo)on the initial form as well as the internal clients.

Internal IE 6 and 7 clients cannot login from the inside as as something is hanging. From the outside Firefox, IE 6 and 7 are fine.

On the inside, firefox does not show above gif,but lets you log in. If you browser back, the images are there.

Currently I have the internal clients pointing to the external IP DNS wise. Even as a caname or a record, behavior is the same. Totally kooky like its an IE rendering issue somewhere.


Here it the redirect statement:

https://webmail.xxx.com/exchange

with: exact URL entered above and a permanent redirection for this resource radio buttons checked.

With the redirect turned off,I had it go to the designated file, no luck. because of the SSL cert it wouldn't even print the page.

The page must be viewed over a secure channel
The page you are trying to access is secured with Secure Sockets Layer (SSL). 
--------------------------------------------------------------------------------

Please try the following:

Type https:// at the beginning of the address you are attempting to reach and press ENTER. 
HTTP Error 403.4 - Forbidden: SSL is required to view this resource.
Internet Information Services (IIS)

"Only the dead fish follow the stream"

 

[pogi05]

I've been experiencing similar problems you have, minus the problem with the logos not showing up. Also both firefox and IE don't work internally.

I have an Exchange 2003 SP1 hosting OWA, RPC over HTTP and OMA.

The only change I've made in my system was that I added a forward look up zone A host to resolve webmail.xxx.com into it's internal server IP. After having weird issues with this and other applications, another personnel deleted the lookup zone. NOW, IE or firefox cannot even view the default webpage without the https redirect enabled. It works fine from the outside, and I can see the default web page. Also, with the redirect enabled, it still doensn't work internally of course, but "hangs" forever from the outside.

Let me know if you'd made any progress on your situation...

I'd like to get to the bottom of this problem.

Thanks,
Chris

 

[shakamon]

I had some consultants that changed the web perms and I was unaware of this change, which we all know is the death of an admin.

This solved it.

http://support.microsoft.com/?kbid=280823

Item 6c specifically solved my issue.

"Only the dead fish follow the stream"

 

[pogi05]

shakamon,

That solved my redirect problem externally.... But I am still having MAJOR IIS issues on our internal network. It's not so much a big deal since no one would use OWA in the office, but it would be nice to know what happened.

Thanks for the redirect fix.

Chris