Announcement

Collapse
No announcement yet.

owa issue

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

  • owa issue

    We have 3 branches connected with leased lines SITEA,SITEB and SITEC. SITEA has the DC and exchange server 2003 Ent installed on win2003 enterprise server and other 2 sites have AD and Exchange server 2003 ent installed which belong to the same organization.SITEA has 50 mail boxes, SITEB has 50 mail boxes and SITEC has 50 mailboxes. My problem is when ever a user from SITEB and SITEC tries to logon to a mailbox from internet using OWA he couldnt but at the same time if a user from SITEA tries to logon to his mailbox he can. How can i make all the SITEB and SITEC users logon to owa from internet. Your precious advice will be a great help to me.

    Thanks
    Skak
    ________
    Depakote lawyer
    Last edited by Skak12; 13th April 2011, 13:23.

  • #2
    Re: owa issue

    Hi,

    Can your users access OWA internally from Site A and B?

    I take it you have port 80 (or 442 for SSL) forwarded from your external IP to your Exchange server on SITE A?

    Read into settings up a frontend / backend topology so your external users connect to the frontend server which then requests information from your backend servers:

    http://www.msexchange.org/tutorials/...rver_2003.html

    Hope this helps

    Michael
    Michael Armstrong
    www.m80arm.co.uk
    MCITP: EA, MCTS, MCSE 2003, MCSA 2003: Messaging, CCA, VCP 3.5, 4, 5, VCAP5-DCD, VCAP5-DCA, ITIL, MCP, PGP Certified Technician

    ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

    Comment


    • #3
      Re: owa issue

      Are all of the servers exposed to the internet directly on port 80/443 (depending if you are using SSL or not)?

      If not, then that is your problem.

      With multiple Exchange servers you have two ways of allowing access to OWA...

      1. Each server is exposed to the internet and the users connect to the correct server.
      2. An additional server is introduced which is configured as a frontend server.

      While it is possible for users to login to one server and be redirected to the correct server, in practise this doesn't work very well for most sites. This is because the redirection will be to the other server's real name.

      For example, if your main server is servera.domain.local and the server being redirected to is serverb.domain.local, then Exchange will redirect your browser to serverb.domain.local which will not resolve over the internet.

      As already pointed out, you probably need to look at deploying a frontend server. This can be a standard Exchange 2003 server, but it cannot hold any mailboxes. This will allow you to have a single URL for all users, no matter which server their mailbox is physically located on.

      Simon.
      --
      Simon Butler
      Exchange MVP

      Blog: http://blog.sembee.co.uk/
      More Exchange Content: http://exchange.sembee.info/
      Exchange Resources List: http://exbpa.com/
      In the UK? Hire me: http://www.sembee.co.uk/

      Sembee is a registered trademark, used here with permission.

      Comment


      • #4
        Re: owa issue

        Do'h - Just realised I have SSL as port 442 instead of 443 - Damm you fat fingers

        Michael
        Michael Armstrong
        www.m80arm.co.uk
        MCITP: EA, MCTS, MCSE 2003, MCSA 2003: Messaging, CCA, VCP 3.5, 4, 5, VCAP5-DCD, VCAP5-DCA, ITIL, MCP, PGP Certified Technician

        ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

        Comment

        Working...
        X