Announcement

Collapse
No announcement yet.

OWA not displaying

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

  • OWA not displaying

    Hello all!

    I am not sure if I am just being stupid or what... Right now I have two Exchange 2003 servers in my domain. The first is slowly being phazed out and the second, is obviously going to be to the main mail server. The issue I am having is that I have users on both, and they all need to be able to access OWA at some point.

    Now, I know that I had this working as my account is on the new server.
    We have a firewall set up that is doing Destination NAT to the new server using port 88 (port forwarding 88 to 80 on the new server). LIke I said, this WAS working. It still works for my Blackberry (that is, I still get my email on my Blackberry at mail.ourcompany.com:88\exchange).

    The thing is, when I try to go to OWA now when I am at home, I get the login screen (username and pass) but when I enter that info, it just sits there and times out. I have noticed that the browser is trying to open the internal name of the machine (that is, server.company.local) instead of the external, port forwarded name.

    My question to you folk is this... what am I missing? I can't figure out why it now will not load correctly and it is making me crazy.

    Thank you all!

    Shawn

  • #2
    Re: OWA not displaying

    OK, update... not sure what the deal was, or still is i guess, but I have worked around the issue by adding another external DNS entry for the new server and giving it it's own external IP address.

    I can now access OWA on either server, depending on the IP that I use. This is actually pretty good in my opinion as it will keep all OWA requests on the new IP once all of the mailboxes are moved over.


    Shawn

    Comment


    • #3
      Re: OWA not displaying

      The behaviour you are seeing is correct.
      OWA doesn't like alternative ports and if it isn't able to connect to the server then it will attempt to redirect to the correct server, using the server's real name.
      The only sure fire way to have a single point of entry for multiple servers is to use a frontend server.

      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 not displaying

        Unless I am reading this wrong, couldnt you set up port translation rules on the firewall to perform PAT and NAT, so you connect externally on port 88 which translates the port and IP to internal:80?

        Think thats the way I would look at it initially.

        Comment


        • #5
          Re: OWA not displaying

          Originally posted by g7rpo View Post
          Unless I am reading this wrong, couldnt you set up port translation rules on the firewall to perform PAT and NAT, so you connect externally on port 88 which translates the port and IP to internal:80?
          I have never seen that work correctly. OWA likes to use port 80 and 443 only.
          You cannot use other ports for EAS, OMA and RPC over HTTPS either. They are all hard coded to 443/80.

          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


          • #6
            Re: OWA not displaying

            Originally posted by g7rpo View Post
            Unless I am reading this wrong, couldnt you set up port translation rules on the firewall to perform PAT and NAT, so you connect externally on port 88 which translates the port and IP to internal:80?

            Think thats the way I would look at it initially.
            You can do that as i have done this before but only in exceptional circumstances. But as already said some of the other features are broken because there hardcoded to use the default ports.

            Comment

            Working...
            X