English Deutsch Français Italiano Español Português 繁體中文 Bahasa Indonesia Tiếng Việt ภาษาไทย
All categories

Hi!

I have a company domain (local) wich has multiple servers in this environment.
- Domain controller (ip 10.10.10.2)
- Exchange server (ip 10.10.10.5)
- Webserver (ip 10.10.10.3)

This environment is attached to the internet with a fixed ip adress, with the nessecairy ports opened (80 and 25).

But now, i want to "serve" websites, but also want to allow my users to login to their mails trough OWA (outlook web access) but this service also runs on port 80, just as my webserver.

This is where i'm stuck. In our router/firewall, you have to forward internet traffic, for the webserver for example, to port 80, but when people want to login to the OWA, its another internal ip, but the same external port 80...

Can someone help me figure this out?

2007-11-18 11:33:47 · 5 answers · asked by sonic393 3 in Computers & Internet Computer Networking

That's just what i wanted to keep away of, asking users to set ports in their url adress...

Their should be another way than this, no? Why do other company's dont have to put the port number behind the url...

Thanx for trying anyway....

2007-11-18 11:56:14 · update #1

5 answers

You're going to need to do one of the following.

1. Get a second IP and point your webpage at that
2. You should be doing this anyway as it's good practice - Run OWA with SSL so they would use https:// to connect.
3. Setup virtual hosting. When you create the website, or after set the 'host header value' to the dns name of the website you are serving, and when they go to mail.mycompany.com they get exchange but when they go to www.mycompany.com they get your website.

Now just as a note, if you are going to be doing web pages and OWA, etc. you really should be using a real firewall and not just relying on a router. I would suggest a Cisco ASA or a SonicWall. This as the additional benefit of allowing you to do VPN into your network which is an even better practice for remote email. Also you should really consider segregating your network so externally facing services are in a DMZ.
But that is a whole other subject so I'll just leave it with those reccomendations.

2007-11-18 12:51:46 · answer #1 · answered by zypher1083 2 · 1 0

Change the port on OWA to port 8080 it is setable you know! Go to server management and change it. Then your webserver will work on port 80 as normal and when you users want to check mail they just go to http://youdomain.com:8080
You will need to then forward 8080 to your OWA server IP. All of it works just fine.

See http://support.microsoft.com/kb/240753
for details

Should do it.

ADDED -- OK then like the answer below -- get a second Public IP and point that one to your OWA server - now you dont need to worry about the port.

2007-11-18 11:49:28 · answer #2 · answered by Tracy L 7 · 0 1

Depends on the size of the server. Exchange uses lots of space so most people use a seperate server for it. But if your website is small, you can use it on the same server.

2016-04-04 21:24:33 · answer #3 · answered by Erica 4 · 0 0

Why are all the answers so dull and short these days?

2016-08-26 07:14:55 · answer #4 · answered by ? 4 · 0 0

I was wondering the same question myself yesterday

2016-09-19 16:58:16 · answer #5 · answered by toshiko 4 · 0 0

fedest.com, questions and answers