OWA Not working except locally

Posted on 2007-03-21
Last Modified: 2010-03-06
I have just installed a second Exchange 2003 Server and moved all mailboxes.
When I try to access OWA from a system other than the new Exchange server, it doesn't work.  Page cannot be displayed.

Locally on the Exchange server it works fine.
I'm typing in http://servername/exchange on both local and remote system.

Please advise as to what the issue could be.  This usually works by default after installing Exchange 2003 without having to do anything.  I'm kind of confused.

Question by:mcrossland
  • 2
  • 2
LVL 104

Expert Comment

ID: 18775131
Do you mean any other system on the internal network?
If so, I would check that you have no connection restrictions on the server that could be blocking the traffic.

Windows Firewall etc.
If it works from the server itself, then the problem is not with IIS.

Does work (Where is the IP address of the new server).

LVL 10

Author Comment

ID: 18776216
Unfortunately the server that was provided to me to migrate to ended up being a refurb with bad memory.  Not my  suggestion at all.   I'm ordering a new high end HP Proliant server to replace that one but if I encounter that issue, I will try your suggestion because you are usually right on the money and I actually think of your name when I post to Exchange hoping you will reply.  :)  You are very much appreciated!
Yes the issue WAS with other systems on the internal network and OWA only worked on the console of the actual Exchange Server that HAD OWA installed on it so I will follow up with this next week
when I get the new server installed as it will be the exact software load as the one that took a dive.
I did try and it did not work from other systems on the local network so I am very curious as to what could have been and might be the issue with the new server build.

thanks again,
LVL 104

Accepted Solution

Sembee earned 500 total points
ID: 18783329
I work on the principle that Exchange should work out of the box. If it does not, then it is almost certainly a bad build. If you have gone past the first run screen for the server (which opens the server to the world) and have not knowing run anything else on the server to secure it, then you should be able to access the server from any machine on the local network.

Exchange should work out of the box - if it does not, remove Exchange, wipe the machine and reinstall. A properly built machine should last you for years, so don't try and save yourself a couple of hours at the start getting something to work which should have worked in the first place.

LVL 10

Author Comment

ID: 18783398
Just ordered a new server.   Will go fresh out of the box.  :)

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question