Announcement

Collapse
No announcement yet.

OWA Premium cannot find users in GAL

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

  • OWA Premium cannot find users in GAL

    I have two exchange 2003 servers on front end and one back end. The front end exchange server is in the DMZ and the back end exchange server is inside the LAN.

    When users try to find users in the Global address list using OWA in Premium mode. They cannot find any users. OWA just keeps searching.

    They can find users in the GAL if they are using Basic mode.
    Last edited by nvarsovia; 1st December 2007, 00:47.

  • #2
    Re: OWA Premium cannot find users in GAL

    Why have you got the frontend server in the DMZ? Do you think that improves your security? If you do then you are mistaken.

    Does it work on the backend server correctly? Are the backends and frontends at the same patch level?

    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 Premium cannot find users in GAL

      Everything work fine. Everything is on the same patch levels. I can even find users in the GAL in Basic mode. It is when users try to use Premium mode on IE 6 and above that it does not work? When they use any other browser OWA defaults to Basic mode.

      Where do you think I should put my Front End Server?


      Thanks
      nvarsovia

      Comment


      • #4
        Re: OWA Premium cannot find users in GAL

        Frontend server should be inside the firewall with the backend server. Frontend servers are not deployed for security reasons, but for performance. The amount of holes and changes that you have to make to Exchange to get a frontend server to work in a DMZ basically makes the DMZ firewall look like swiss cheese. Put it inside and then open the one or two ports that are required only.

        It isn't clear - does OWA work correctly for all functionality if you connect to the backend server directly, rather than the frontend?

        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


        • #5
          Re: OWA Premium cannot find users in GAL

          If you are referring to Users connecting to the backend server using any version of Microsoft Outlook. Yes everything is working. THe only complaints I got from MS Outlook clients is the Archive folders which is a totally different story or issue.


          I just tried connecting to the backend server using OWA and it works perfectly. I guess the data cannot find its way back from the frontend to backend and back to the frontend server


          Also the backend server has been working for a few years now.

          Comment


          • #6
            Re: OWA Premium cannot find users in GAL

            Not interested in whether Outlook works, just whether OWA works.
            If OWA works when connecting directly to the backend server then the frontend server being in the DMZ is where I would look at the cause of the problem. I would suggest you bring it inside where it belongs and test it again.

            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


            • #7
              Re: OWA Premium cannot find users in GAL

              The problem is solved. It was an ISAPI filter that I have configure before and wasn't working properly. I had to reinstall the ISAPI filter and then everything worked out fine

              Thanks

              Simom Special thanks to you

              Comment

              Working...
              X