[Exchange/OWA] OWA not working through NAT
When trying to use OWA (Outlook Web Access) from outside the local area network in which the server resides, it does not seem to load stylesheets, images etc, just plain text, and no Inbox.
When using OWA from inside the local area network, it loads just fine.
We have tried to forward/map all the ports that Exchange/OWA need, referring to the Microsoft KB.
Also, we have tried it from multiple locations, so it is not a browser issue.
Specs:
OS: Windows 2003 SBS Server SP2
Exchange 2003+OWA
Browsers: IE6, IE7.
When using OWA from inside the local area network, it loads just fine.
We have tried to forward/map all the ports that Exchange/OWA need, referring to the Microsoft KB.
Also, we have tried it from multiple locations, so it is not a browser issue.
Specs:
OS: Windows 2003 SBS Server SP2
Exchange 2003+OWA
Browsers: IE6, IE7.
LeeDerbyshire
Have a look at the Exchweb virtual directory in IIS Manager, and make sure that anonymous access is still enabled on it and propagated to the subdirectories.
ASKER
@LeeDerbyshire:
We have checked the permissions, and the permissions are exactly like you said, anonymous access is allowed through the IUSR account.
We have checked the permissions, and the permissions are exactly like you said, anonymous access is allowed through the IUSR account.
You'll need to examine an external OWA session in your IIS logs, and compare it with an internal session. You may see several external resource requests that result in a status beginning with 4 (e.g. 401, 403 or 404), indicating some kind of failure. Note that the times in IIS Logs are in GMT.
ASKER
@LeeDerbyShire:
Thank you, that was a pretty good idea, because it returns 403 errors while retrieving the ExchWeb files, I have made sure that the IUSR has full rights on the ExchWeb directory, but it still does not work.
Thank you, that was a pretty good idea, because it returns 403 errors while retrieving the ExchWeb files, I have made sure that the IUSR has full rights on the ExchWeb directory, but it still does not work.
The 403 might mean that SSL is required. If you have not required SSL on the Exchange VDir, then make sure that it is also not required on Exchweb.
ASKER
@LeeDerbyShire:
I've made sure that SSL is required for the vdir exchange and for the ExchWeb dir, and made a temporary SSL certificate, but now it just returns a 500 Internal Server Error.
I've made sure that SSL is required for the vdir exchange and for the ExchWeb dir, and made a temporary SSL certificate, but now it just returns a 500 Internal Server Error.
Adding SSL seems to have just complicated things. Try removing SSL from both Exchange and Exchweb, and try OWA again. If it still looks a mess, show us all the IIS log entries that are generated when you log into OWA.
ASKER
I have just tried to go without SSL, but it still returns a 500 error somewhere, I've found another post where it was recommended to clear the Jet DB's, but that requires me to stop/start NETLOGON and NTFRS, which I can't do at this point, because it's a used domain controller.
Anything in the Event Logs when the 500 error is generated?
"We have tried to forward/map all the ports that Exchange/OWA need, referring to the Microsoft KB."
Which MS KB? Because OWA on an SBS is not configured manually. You instead should only use the Configure Email and Internet Connection Wizard (CEICW -- linked as "Connect to the Internet on the To-Do list in the Server Management Console) to configure things.
A visual how-to for that is here: http://sbsurl.com/ceicw
At this point, I'd suggest that you allow IIS to fully rebuild the Exchange directories by following Method 2 in http://support.microsoft.com/kb/883380
Then run the CEICW to properly configure OWA.
Jeff
TechSoEasy
Which MS KB? Because OWA on an SBS is not configured manually. You instead should only use the Configure Email and Internet Connection Wizard (CEICW -- linked as "Connect to the Internet on the To-Do list in the Server Management Console) to configure things.
A visual how-to for that is here: http://sbsurl.com/ceicw
At this point, I'd suggest that you allow IIS to fully rebuild the Exchange directories by following Method 2 in http://support.microsoft.com/kb/883380
Then run the CEICW to properly configure OWA.
Jeff
TechSoEasy
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.