Announcement

Collapse
No announcement yet.

OWA setup and configuration issue

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

  • OWA setup and configuration issue

    Hello,
    I'm trying to setup OMA in my network and am having some problems. OWA works fine, however OMA is giving me problems. I have a BE-FE setup using Exchg 2003.

    My FE has two sites: Default(stopped), and FEWebSite
    The FEWebsite has Exchange, ExchWeb, OMA, Public virtual directories. Both Exchange and OMA has the \.\\mailboxstore\smtp\mbx in the local path.
    Under the OMA properties, all checkboxes are checked, and the application name is: /LM/W3SVC/1/root/OMA, scripts only, ExchangeMobileBrowseApplicationPool under the Application Pool. There is no SSL setup and the security is only Basic.

    My BE has two websites: Default and BEWebSite
    The Default has all the virtual directories, such as Exchange, ExchWeb, OMA, Public, etc.
    The BEWebsite has ExchWeb and Public virtual directories

    Now, when I try to connect to https://mail.smtp/oma, I get a box to type in my username and password, and then I get a page with the following
    [To Parent Directory] -- which on clicking takes me to my OWA page
    FEComputerName-System Attendant
    SystemMailbox{SID}

    Can anyone tell me why this is happening? I can access OWA just fine, and I thought OMA was the easy thing, but its not.. atleast not for me. I have browsed tons of sites including this one and read the information about creating another VD and adding a registry entry, however I'm confused as to which machine should I be putting that in and why is it necessary since OWA works fine. Please help!! Any help or advice is appreciated. Thank you
    --S

  • #2
    Re: OWA setup and configuration issue

    Why do you have two web sites on the backend server? That isn't the standard configuration of Exchange and would be a red flag to me immediately.
    Why is the Default Web Site stopped? Again that is a flag for an error.

    It sounds like someone has attempted to customise or "secure" (I use the term in loose sense) the server.
    Due to the way that Exchange and OMA and Exchange ActiveSync work, trying to get things to work outside of the default web site will usually fail.
    OMA makes internal calls to the /exchange virtual directory and is expecting it to be in a certain place.

    While I appreciate that OWA is working for you, that doesn't mean it is configured correctly.
    I would suggest that you reset the virtual directories and the default web sites back to the out of the box configuration. http://support.microsoft.com/default.aspx?kbid=883380
    Drop the additional web sites so that everything is configured as it should be.

    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


    • #3
      Re: OWA setup and configuration issue

      Hi Simon,

      Thanks for your reply. The reason the Default Website on FEWebsite is stopped, is because we created another one with only the VD's we want. Since we do not want any ActiveSync going on, we didn't put that folder in. So even though OMA makes the calls to /Exchange, it should still be able to find it, since OWA does the same thing right? Also, I forgot to mention the FE server is in the DMZ, so not sure if that makes a difference.

      Thanks again!
      --S

      Comment


      • #4
        Re: OWA setup and configuration issue

        OMA makes internal calls to the /exchange virtual directory on the default web site. Therefore the fact that you have /exchange outside of the virtual web site is going be the first problem.
        The next problem is the fact that you have the frontend server in the DMZ. That is not the place for an Exchange server and whatever reason you put it in there you were wrong. No one has given me a good reason to put a frontend server in the DMZ yet, and I have been asking for three years why you should.
        If you don't want users to use ActiveSync then simple change the settings on the virtual directory to block any access.

        Basically there is enough wrong with the deployment of Exchange that could mean the problem could be anywhere.
        The fact that OWA works is immaterial - a previous working system is not an indication that either it was done correctly or will continue to work in the future.

        Therefore I would suggest that you
        a. Bring the frontend server inside the firewall where it belongs.
        b. Reset both the backend and the frontend virtual directories in IIS back to their default state, removing anything additional Exchange wise, such as additional directories or virtual servers.
        Then test again.

        In your current state there is simply too much to diagnose accurately.

        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

        Working...
        X