• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 893
  • Last Modified:

OWA SBS 2003 Not working internally or externally

Hi all
I am having major problems getting access to OWA either internally or exteranally.  when I fire up IE and goto http://myservername/exchange I get a msg similar to to when I you lose net connection this page cannot be displayed
I get the same msg externally when I goto http://myipaddress/exchange
I need to gain access both internally and externally if it is any issue we currently host the mail somewhere else and use a POP3 connector to pull it in.
Thank you
Philip Meason
0
Zanthras1st
Asked:
Zanthras1st
  • 3
  • 2
1 Solution
 
Exch_AdminCommented:
Did you recently change the recipient policy or change how or what email addresses were stamped on users.

This will for sure break OWA. To check if this is the issue, in Exchange system manager, ESM, expand servers, servername, protocols, http, exchange.

pull properties on the exchange container and check the exchagne path.

if the exchange path is domain.local and domain.local is not an email address stamped on users owa will not work and you will get 404 errors.

to fix this problem, stamp domain.local as a secondary address on all your users.

If this does not fix your issue the follow the following steps.

1. IIS under default website, delete the following virtual directories.

a. Exchange
b. Exchweb
c. Exadmin
d. Public

2. At a command prompt type the following commands.

cd\
C:
cd inetpub\adminscripts
adsutil "click ok twice to register the script"
adsutil delete ds2mb

3. Restart the System Attendant and IIS services.

5. Check IIS and the virtual directories will be back.

6. Test OWA
0
 
Zanthras1stAuthor Commented:
Okay Thanks for that I now have internal OWA working again but still no External I am getting a 403 forbidden  IP address has been rejected.  Which is where I was when I broke internal ;0) If you have any further tips on external then I would be happy to hear them but so as not to be completely lazy I did see this problem cropping up in my searches yesterday so in the mean time I'll see if there is an answer out there in EE that will work for me.
Thank you again
Philip Meason
0
 
Zanthras1stAuthor Commented:
As an aside note it was the second part of the answer that got things running again - just in case anyone was wondering.
Regarding the first part of the answer I looked up the exchange path which is set to premierconsultancy.com are internal domain is PMC.local
The reason for this is, I believe, we are using a pop3 connector to pull our mail from a hosted mail box outside of the domain.  Will this effect how OWA works? Will it make any difference to how we log on?
Thanks again
0
 
Zanthras1stAuthor Commented:
One Final note to anyone else who maybe looking to remedy this type of problem I have just installed SP1 for exchange 2003 and I can now OWA for Users and administrator externally.  Hopefully the problems are sorted, if not I am sure I'll be posting again.  Peace
Philip Meason
0
 
Exch_AdminCommented:
You are welcome!
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now