Announcement

Collapse
No announcement yet.

Creating a 2nd OWA website

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

  • Creating a 2nd OWA website

    Hi Everybody,

    I have a front end exchange server running OWA in location A and 2 backend exchange servers in location A and location B. OWA only works for users in location A. What i want to know is it possible to create a seccond OWA website on the same IIS/exchange server on the fronteand and point that website at location B?

    I hope this is not too confusing.
    Mark

  • #2
    Re: Creating a 2nd OWA website

    This is not so complicated:
    When a user trying to access his mailbox, the FE checks where the user's mailbox is located (on which BE) in the AD and gets his info from the right BE server.

    If you need another FE you can install second FE in location B with a different DNS name and let the users in location B use this one.
    In case of crash of one of the FE, the users from the other location will be able to login and get their mailbox from the working FE.
    CNE 5, CCA, MCSE NT4.0-2003, MCSE 2003 messaging, Exchange Server MVP.
    Tzahi Kolber - IT Supervisor
    Polycom Israel.

    Comment


    • #3
      Re: Creating a 2nd OWA website

      Ok maybe i my front end is not set up right. If a user from location A logs on to OWA everything is ok. If a user from location B (their mailbox is in a different location to OWA server but same domain) tries to log on to OWA they get error 503 service unavailable.

      Mark

      Comment


      • #4
        Re: Creating a 2nd OWA website

        1. Check the connectivity between the FE and the second BE.
        2. See the next KBs:
        http://support.microsoft.com/kb/823159
        http://support.microsoft.com/kb/837285
        CNE 5, CCA, MCSE NT4.0-2003, MCSE 2003 messaging, Exchange Server MVP.
        Tzahi Kolber - IT Supervisor
        Polycom Israel.

        Comment


        • #5
          Re: Creating a 2nd OWA website

          I can't see it being a connectivity issue and all three servers were fresh installs of 2003.

          Mark

          Comment


          • #6
            Re: Creating a 2nd OWA website

            I should say that you won't need to do anything like set up a second OWA website on the same server.

            The same FE\OWA server should let your users have access to mailboxes on server A as well as server B, providing there is connectivity, as TK has said.

            So, here are a few silly questions, just so we understand your setup, sorry:
            1. What's the connectivity between location A abd B?
            2. Can users on server A email users on Server B?
            3. And vice-versa?
            4. Both servers on the same domain? And the OWA?
            5. Both servers and the OWA are visible in ESM?
            6. From site A, can you go to http://serverB/exchange and login OK?

            If you can do no.6, then you do indeed have an OWA-ish connectivity between the sites. Well, it proves that port 80 is open and you could get to your mailboxes OK.

            If you have internet access on your current OWA server, you can also test this on the server.

            Let us know how you do.

            Cheers,



            robbyb

            Comment


            • #7
              Re: Creating a 2nd OWA website

              1. What's the connectivity between location A abd B?

              VPN connection between both sites. Servers see each other as iff they are next to each other with all traffic between them allowed.

              2. Can users on server A email users on Server B?

              Yep all users are in the same domain and emaill works fine

              3. And vice-versa?

              Yep no problem

              4. Both servers on the same domain? And the OWA?

              Yes both servers on same domain and OWA but not the same subnet

              5. Both servers and the OWA are visible in ESM?

              Yes

              6. From site A, can you go to http://serverB/exchange and login OK?

              No OWA is at site A, Site A users can log in but site B users can not. I was told that this was because Site B users did have their mailboxes at Site B therefore this will not work.

              Thanks for the help

              Mark

              Comment


              • #8
                Re: Creating a 2nd OWA website

                Hmm. Now I am confused. You say:

                "No OWA is at site A, Site A users can log in but site B users can not. I was told that this was because Site B users did have their mailboxes at Site B therefore this will not work."...

                ..but I thought you originally said that there was a frontend\OWA at Site A?

                But we'll get there. With all that connectivity, this should all work OK. It shouldn't matter which server the user's mailbox is on.

                So could you confirm the following:
                1. Which site is the OWA\Front End box at?
                2. Do you have mailboxes on the Exchange Server at Site A?
                3. Do you have mailboxes on the Exchange Server at Site B?

                Could you also test the following and let us know:

                1. From an IE browser on an internal PC at Site A, can you go to http://serverB/exchange and see an OWA login OK?

                2. And how about from Site B, going to http://serverA/exchange?

                Do let us know the results of these tests - I'm sure they'll go some way towards helping to solve the problem.

                Regards,

                robbyb

                Comment


                • #9
                  Re: Creating a 2nd OWA website

                  So could you confirm the following:
                  1. Which site is the OWA\Front End box at?
                  2. Do you have mailboxes on the Exchange Server at Site A?
                  3. Do you have mailboxes on the Exchange Server at Site B?

                  Sorry my fault. To clear it up, I have OWA on a front end server at site A and a beackend at Site B and A. Users at Site A have mail boxes at Site A and users at SIte B have mail boxes at Site B. Site A users are ok they can log onto OWA. Users at site B can not log onto the frontend at Site A and see their mail box at Site B.


                  Could you also test the following and let us know:

                  1. From an IE browser on an internal PC at Site A, can you go to http://serverB/exchange and see an OWA login OK?

                  No this does not exist only frontend server at site A has OWA

                  2. And how about from Site B, going to http://serverA/exchange?

                  Yep no problem but cant see any Site B mail boxes


                  Thanks a lot for your help!

                  Mark

                  Comment


                  • #10
                    Re: Creating a 2nd OWA website

                    More questions, sorry Mark.

                    But I am starting to get there. You've got two servers at Site A:
                    1 OWA server
                    1 Mailbox Server

                    At Site B, you have
                    1 Mailbox Server.

                    Got it. And users at Site A are cool because they can log onto the OWA and get to their messages but users at Site B are uncool cause they can log onto the OWA but can't get to their mailboxes. Got it.

                    So, moving on. On my questions, for Q1 you said:

                    1. From an IE browser on an internal PC at Site A, can you go to http://serverB/exchange and see an OWA login OK?

                    No this does not exist only frontend server at site A has OWA
                    But even though there is no OWA at Site B, internally, on a PC inside your company at Site A, you can still start up a browser and go to: http://serverB/exchange. It should still work. So please have a go and let us know what you get.

                    For Q2, you said:

                    2. And how about from Site B, going to http://serverA/exchange?

                    Yep no problem but cant see any Site B mail boxes
                    But would like you to not use your OWA server address to do this, but instead, please type in http://serverA/exchange at a browser at a PC over at Site B. Doing so will test connectivity between the two sites.

                    Doing these two tests, and I'm expecting a difference, so do let us know what you get, with any error messages. Screen shots would be cool too.

                    Here's a new question:

                    Q3 Just checking, but all your users (Site A and Site B) are accessing OWA from the outside world? And this is where the problem is for Site B users?

                    And my last for now

                    Q4 Could you tell us a bit more about what happens when a Site B user tries to use OWA? Could you let us know specifically what error message they are getting?

                    Sorry about all those questions - robbyb

                    Comment


                    • #11
                      Re: Creating a 2nd OWA website

                      So, moving on. On my questions, for Q1 you said:



                      But even though there is no OWA at Site B, internally, on a PC inside your company at Site A, you can still start up a browser and go to: http://serverB/exchange. It should still work. So please have a go and let us know what you get.

                      Yes it redirects me back to Site A backend server only if i use http not https

                      For Q2, you said:

                      But would like you to not use your OWA server address to do this, but instead, please type in http://serverA/exchange at a browser at a PC over at Site B. Doing so will test connectivity between the two sites.

                      Error can not find page http 500 internal server error

                      Q3 Just checking, but all your users (Site A and Site B) are accessing OWA from the outside world? And this is where the problem is for Site B users?

                      yes this is correct


                      Q4 Could you tell us a bit more about what happens when a Site B user tries to use OWA? Could you let us know specifically what error message they are getting?

                      http 404 file or directory can not be found


                      Thanks Again

                      Comment


                      • #12
                        Re: Creating a 2nd OWA website

                        On Q1, you've said: Yes it redirects me back to Site A backend server only if i use http not https

                        Now that's wierd, in a strange kind of way. I would expect, if you are at Site A, and you type http://serverB/exchange, that there should be an attempt to connect to the server at Site B. It shouldn't be redirecting to Site A and the server at Site A.

                        This makes me think that someone has set up some kind of redirect within your internal DNS servers.

                        On Q2, you said for contacting OWA via http://serverA/exchange: Error can not find page http 500 internal server error

                        That too is strange. If you were at Site B and got this error, then this might indicate that IIS on Server A could have a problem. But as you say, OWA is working to access mailboxes on Server A, so we should just tip toe away from this...


                        But Q4 , where you get [/B]http 404 file or directory can not be found[B], is interesting. Checking on the web and this error also points to a connectivity issue.

                        So, here are some directions to look:

                        Check to see if your OWA server can resolve your serverB's name, and actually get to the server. So, from a DOS prompt on the OWA server try (assuming your firewall allows pings and such):

                        1. Ping serverB by IP address.
                        2. Ping serverB by name.

                        Let us know what happens?

                        I'm also a bit suspicious of DNS. Could you check that DNS is resolving to the correct IP address for each server? In particular, please check that there isn't any kind of forwarding in place. So please check:

                        1. tracert serverA from the OWA server. See how it hops and that it ends up at the IP address for serverA

                        2. tracert serverB from the OWA server. See how it hops and again that it ends up at the IP address for serverB.

                        Good luck.

                        robbyb

                        Comment

                        Working...
                        X