[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 252
  • Last Modified:

Exchange 2003 and IIS 6.0 different server

Hi,

I have setup 2 servers with Windows Server 2003 R2 Enterprise SP2. Server 1 has IIS 6.0 and Exchange 2003 SP2 (mail server) and server 2 has only IIS 6.0 (web server) installed. Server 1 is my mail server (internal and external) and server 2 is going to host all my websites. So I have port 80 in my router (single public IP address) forwarded to server 2 otherwise my customers cannot reach their websites. In order to use OWA (no SSL or https) on the exchange box I have to forward port 80 to my mail server. How can I configure IIS on server 2, when my customers are using http://owa.domain.com for example, routing OWA trafiic internally to server 1 using server1/exchange. Do I have to create a website or virtual directory? I tried it but cannot forward it ot http://server1/exchange. Am I missing something? Doing something wrong? What is the best way?

Thanks in advance!
0
djaycee
Asked:
djaycee
  • 4
  • 2
1 Solution
 
needleboyCommented:
Hi there,

the best way is to connect to OWA over secure connection (HTTPS).
Just forward TCP port 443 to server 1 and use HTTPS instead of HTTP.

Marko
0
 
djayceeAuthor Commented:
Hi Marko,

Thanks for your answer but that's just what I don't want. And also can't do because some of my customers use https also...

Hans
0
 
needleboyCommented:
Hi djaycee,

You must implement better firewall solution like Microsoft ISA/TMG server.
You can route traffic like that using Microsoft IIS.
Microsoft ISA is L7 firewall and can filter traffic using the dns names used for your websites.
Almost unlimited number of internal websites and inside hosts are supported.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
djayceeAuthor Commented:
Hi Marko,

Ok, and if no ISA present, are there any other solutions?
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
Another public IP or use a different port.  I've never heard of a way to "extract" OWA off the Exchange server.  You might be able to add a second exchange server to be a front end server - if you wanted to spend money on another exchange license.
0
 
djayceeAuthor Commented:
Hi Everyone.

Thanks for the comments. I've tried some things and with a litle help from everything I read I did it. Open port 81 on the firewall and letting all traffic for OWA being routed through server 2 (only IIS) to server 1 port 81. This did the tric and everything is working like I planned it. Now you only see in the address bar that OWA is routed to port 81. Well that's something I can live with. Maybe in the future I get that right too. But for now it's OK. Thanks for the help.
0
 
djayceeAuthor Commented:
No comments.
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now