[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3074
  • Last Modified:

http/1.1 503 service unavailable

We recently brought up a new exchange 2003 server with sp1 on windows 2003 server within the same admin group.
We moved some users from another exchange 2003 to the new one.

now users are not able to logon to the OWA 2003 They get the following error

http/1.1 503 service unavailable

any help will be appreciated
0
cdaya
Asked:
cdaya
  • 3
  • 2
1 Solution
 
eatmeimadanishCommented:
Sounds like OWA is not setup right on the other machine.

1) Setup SSL.  I have noticed many problems with permissions until I setup SSL, then they seem to go away.  
http://www.msexchange.org/tutorials/SSL_Enabling_OWA_2003.html

2) Use a Frontend server for OWA (can not view mail on this server)
http://www.msexchange.org/tutorials/Configuring-Exchange2003-HTTP-Remote-Access.html

0
 
cdayaAuthor Commented:
The issue with users not being able to access OWA are on a new backend server that i installed. I have 3 other backend mailbox servers on which the users are fine accessing their mailbox via OWA.
So it cannot be authenication issue or SSL issue.
Do I need to do anything on the new backend server.
0
 
David WilhoitCommented:
Is the backend server in a different domain? Have you checked to see that the RUS is working? Have you verified that you can connect to OWA directly on the backend server itself?

D
0
Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

 
cdayaAuthor Commented:
the backend is on same domain. RUS is working
when i do newserver\exchange it goes to one of my existing servers
0
 
David WilhoitCommented:
then something else is wrong. OWA is installed on every E2Kx server, so unless IIS isn't running, then the OWA server has to answer. http//:servername/exchange, regardless of whether or not the mailbox is available, should get you to the authentication box or the FBA screen on that server. Can you open OWA from the server itself?
0
 
cdayaAuthor Commented:
I found the issue. Everything is fine with the FE and BE servers
our network group forgot to allow add to ACL list for this new site. Once all routes were added on cisco switch everything went fine.
Thanks for all the help
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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