Announcement

Collapse
No announcement yet.

Exchange 2003 OWA via a seperate IIS 5 Server

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

  • Exchange 2003 OWA via a seperate IIS 5 Server

    Hi,

    I'm looking for some help with configuring our OWA access. I have done a lot of searching both on here and on Google and can't find anything to say that I either can or can't do what I want to do, so I'm hoping that somebody here may be able to help me.

    Our scenario is that we have Exchange 2003 sitting on a Windows 2003 Server. This is an existing set up and works fine. OWA access directly from this server is also fine as it installed when initially set up. However, our main web server is on a different machine and this is the one that is externally facing. It is a Windows 2000 Server running IIS 5.

    Surely there must be a way that I can set up our web server to point to the Exchange server through some kind of virtual directory or link? I have tried pointing it to http://server1/exchange but it will not accept this as it is not a qualified local address. I have also tried changing an existing set up virtual directory to point to another URL as a redirect (I don't get this option for a new virtual directory) but this either fails on authentication or logs straight in to the webmail with our domain's admin account.

    Any help would be most appreciated as I'm sitting here tearing my hair out!

    Many thanks,

    Mark.
    Network Support Engineer

  • #2
    Re: Exchange 2003 OWA via a separate IIS 5 Server

    You can't use a virtual directory in the way that you have outlined.

    You would need to have another Exchange 2003 license and configure a frontend/backend scenario.
    The machine would also have to be a member of the domain to work correctly.

    However I would not recommend using Windows 2000, or mixing OWA with public traffic. The fact that Exchange has to be installed on a domain member makes the security of the server a nightmare.

    I would actually go further and suggest that you revise having a public web site on Windows 2000!

    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: Exchange 2003 OWA via a seperate IIS 5 Server

      Hi Simon,

      Thanks for your reply. At least that solves that then.

      So you wouldn't recommend using OWA outside of our internal network because of the security implications? I have seen and used it before, but wasn't aware that it left such a big security hole?

      Thanks,

      Mark.

      Comment


      • #4
        Re: Exchange 2003 OWA via a separate IIS 5 Server

        Exchange requires access to the domain controllers. The number of holes that are required in the firewall for that to work just makes any kind of DMZ useless.

        Then simply inviting anonymous traffic to visit a domain machine is bad practise. Limit your risk to begin with.

        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