Exchange Server 2003 - OWA Issue

[dmilleruk1]

I don't know weather this is an IIS 6 or Exchange issue, but i will ty to explain anyway.

I have OWA setup with SSL in SBS Server 2003 w/Exchange.

If try to access OWA via

https://servername/exchange

or

https://IPaddress/exchange,

internally on the server or from the workstations, it presents a "page cannot be displayed" error.

But if i try

https://servername/exchweb/bin/auth/owalogon.asp?url=https://servername/exchange&reason=0

I am able to logon to my exchange mailbox. Once logged in all folders work expect the public folder, which again displays "page cannot be displayed". The same message displays again when i click log off.

After trying the microsoft kb article for recreating OWA virtual directories via the IIS resources metabase explorer tool, I tried reinstalling IIS and the exchange server using the /DisasterRecovery switch. Which hasn't resolved the issue. It seems like something is corrupt in the setup. Do I need to rebuild the server and start again or can anybody provide help on what try next? .

Thanks

 

[TechyMcSe2k]

if you are accessing it internally, you do not need the https(443) only http(80); unless you restricted it so.

Also, on the IIS for the OWA - exchange, can you right click and browse it? or does it scream for https only?

________________________________________
Achieving a perception of high intelligence level can only be limited by your manipulation skills of the Google algorithm!

 

[dmilleruk1]

Even with SSL removed and browsing through the exchange directory through IIS the problem still occurs. Could it be a problem with the Servers DNS?

 

[58sniper]

what if you try

http://server/exchange/username

replacing username with your actual username.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[dmilleruk1]

58sniper i have tried your suggestion, same thing happens "page not displayed

 

[dgallegos]

This happened at a site and i looked up how to delete the virtual directory's in IIS and reinstall something sounds like it went wacky with the OWA setup. In all cases this just recreates the virtual directory's in IIS flawlessly and working about 95% of the time.