Announcement

Collapse
No announcement yet.

OWA Error 503 Service Unavailable Exchange 2003

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • OWA Error 503 Service Unavailable Exchange 2003

    Hi guys

    Let me show you my scenario (very complicated, i guess)

    I got a HW FW first, a Linux FW, as a second line of defense, and a Exchange 2003 SP2 FE. my BE is a Exchange 2000, last SP, on a W2K Server DC with the last SP. My organization borned as a Exchange 2000 Org.

    All my messages are redirected from the Linux FW to the Exchange 2003. All messages are coming in and out without problems.

    Before the arrive of Exchange 2003, the OWA service was placed with the Exchange 2000, without problems. Now, with the mail redirected to the new Exchange 2003, all users with the OWA functionality get the message "HTTP/1.1 503 Service Unavailable". They use the same link as usual, "http://www.mydomain.com:8080/exchange"

    Internally, the users use the IP address of the BE server and access OWA as http://192.168.1.16:8080/exchange, if they try to use OWA of the FE server http://192.168.1.18:8080/exchange, they gets the same message.

    Well. anybody can give a light (or a candle, if you can) to solve this problem?

    Thank you

    JeanLucPicard.

  • #2
    Re: OWA Error 503 Service Unavailable Exchange 2003

    Why you use proxy http://www.mydomain.com:8080/exchange and change the default OWA port?

    http://support.microsoft.com/?kbid=280132

    Also, I guess that the firewalls doesnt setup correctlly and the Linux box cant be use for OWA publish as it should (Sometimes using Squed works but I prefer ISA 2004 for publish OWA).
    Best Regards,

    Yuval Sinay

    LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

    Comment


    • #3
      Re: OWA Error 503 Service Unavailable Exchange 2003

      Maybe I didnt describe the scenario correctly

      When I redirected the message traffic to the Exchange 2000, for the first time, OWA was fine. Then, I installed a Exchange 2003, redirect the traffic to it, and marked it as FE, as Master in the routing group, and when I try to use OWA, it doesnt work. But all messages are flowing normally. I redirect the messages to the first Exchange 2000, but OWA is out of service.

      I'm thinking that Exchange 2000 OWA with Exchange 2003 doesnt work together.

      Well, next week I will decomission the Exchange 2000. I hope that help.

      Any idea to how to remove Exchange 2000 without problems?

      Thanks for the advice.

      JLP

      Comment


      • #4
        Re: OWA Error 503 Service Unavailable Exchange 2003

        Using Exchange 2003 as fornt and Exchange 2000 as back should works fine. However, users with mailboxes on the backup servers with get OWA of Exchange 2000.

        Im thinking that you will need to create a diagram of your networks with IP/OS Version, Service Pack Level, firewall settings etc. There maybe some bad settings in the environment.

        http://www.microsoft.com/downloads/d...displaylang=en
        Best Regards,

        Yuval Sinay

        LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

        Comment


        • #5
          Re: OWA Error 503 Service Unavailable Exchange 2003

          I have a similar OWA problem I would like to solve.

          In my single AD 2003 native domain, I have 3 total Exchange servers:
          1 old 5.5 SP4 BE server (Win2000 SP4) with 250+ mailboxes
          1 new Ex2003 SP2 BE server (Win2003 SP1) with 2 mailboxes; also runs ADC
          1 new Ex2003 SP2 FE server (Win2003 SP1) with 0 mailboxes

          All EX servers sit within my network behind two firewalls and a router. Although the FE will eventually service Inet OWA clients through a single mapping using SSL, I have a fundamental problem logging in from inside my network with no firewalls or routers or SSL involved. Rest assured that the traffic is all open vanilla plaintext with no intervening network devices to consider yet.

          HERE'S WHAT HAPPENS:
          I can successfully open OWA from the BE 2003 server if I log in to either of the 2 mailbox accounts there. If I try to do the same from the FE 2003 server, the authentication appears to succeed but I never get my Inbox messages to load, rather a perpetual message that it is "LOADING". (= BUMMER #1) If I attempt to log on as a 5.5 mailbox user, I get a 503 error in IE. (= BUMMER #2) It makes no difference whether I logon from my PC across the network or using IE directly on the console of the 2003 FE server; the result is exactly the same.

          After reinstalling Exchange2003, SP2, deleting & reinstalling the Ex2003 web sites in IIS and wringing my hands, there was no improvement. NADA! So, for the absolute heck of it, I decided to uncheck the checkbox that configured my FE server as a front end exchange box and rebooted it as a normal full Ex2003 server. To my WILD surprise, when I now login as one of my 2 working 2003BE mailboxes using OWA on this server, I'm successfully authenticated but then the address in my browser is replaced by that of the BE 2003 server and I'm re-prompted for my logon creds. WHAT THE HEY!?! If I logon to the redirected address, I successfully open these 2 mailboxes in OWA but on the BE 2003 server. Unfortunately, I still get the 503 error if I try to use OWA to get to one of the 5.5 accounts.

          QUESTION #1: Shouldn't the "former FE" server have simply connected me to my mailbox directly? Am I incorrect in expecting a FE server to do this? Does anyone have an insight as to why the FE checkbox is an issue for a FE server?

          QUESTION #2: Why I get the 503 error if I attempt to log on as a mailbox user housed on the BE 5.5 server. Doesn't a background service like the Site Replication Service handle the redirection to the appropriate BE server in Exchange2003 mixed mode? Is it simply a requirement that I first move my 5.5 mailboxes to a 2003 BE server before it is accessible using OWA 2003?

          Sorry for the length and I hope I haven't bored or offended anyone. BTW this is a very nicely run forum!

          Thanks in advance.

          Comment


          • #6
            Re: OWA Error 503 Service Unavailable Exchange 2003

            Why did you tack your query onto the end of someone elses thread and hijack it? Why not start a new one and make life easier for everyone especially for JeanLuc. He may want to beam followup questions into HIS thread!
            1 1 was a racehorse.
            2 2 was 1 2.
            1 1 1 1 race 1 day,
            2 2 1 1 2

            Comment


            • #7
              Re: OWA Error 503 Service Unavailable Exchange 2003

              Sorry. I didn't realize my tacking this on is considered offensive behavior. I mistakenly thought it would be helpful to keep a related post in the same thread. I apologise to JeanLuc.

              Please disregard my post.

              jmattern

              Comment


              • #8
                Re: OWA Error 503 Service Unavailable Exchange 2003

                Just create a new thread and get your questions answered.
                1 1 was a racehorse.
                2 2 was 1 2.
                1 1 1 1 race 1 day,
                2 2 1 1 2

                Comment


                • #9
                  Re: OWA Error 503 Service Unavailable Exchange 2003

                  No problem JMatter, but I hope you can solve your problem, 'cos I didnt yet.

                  Let me describe my scenario, more deeply. (I have AD 2000, SP4, 1 Domain with 2 DC's).

                  Several years ago, the company just has a Linux Firewall, redirecting all traffic to a Exchange 2000 on a DC, but, unfortunatly, an attack force to the management to buy a Fortinet FW. Now the scenario shows 2 FW, the first one (Fortinet) faced to internet, and the second one (Linux) connected to the Fortinet and the internal network.

                  Then, someone adds a second Exchange 2000, on a third DC, move the mailboxes to the new server, and left the old Exchange 2000 running. All traffic was redirected (SMTP, Port 80, and 8080) to the new server. Everything was fine.

                  Then, I added a Exchange 2003 SP2 on a Windows 2K3 with SP1 member server, redirecting all traffic to this new server and marked it as a FE. The users can open the OWA web page, gets the authentication window, but nothing happens.

                  Then, I moved all mailboxes from the Exchange 2000 to the Exchange 2003, decomissioned the old Exchange 2000 (the first one) and now the users cannot get the OWA web page.

                  Now, three months later, the GM is upset because he cannot read his mail from home and everyone blame to the Exchange 2003

                  This is my sad story. I know that Exchange 2003 is a good application, but here, I'm alone with this statement.

                  Someone can give me a hand on it, please?

                  Comment

                  Working...
                  X