2 Port Redirects

[SeanAIX430]

My main server is Windows 2003 with 2003 Exchange. It also has my website on it presently. I want to move my website to another machine, but still have my domain name take visitors there. So I have to redirect port 80 on my main server to another IP address.

I also want to setup my mail.domain.com to go to my present server at 192.168.1.100/exchange. Hopefully this way everyone can get to OWA from the outside, by just going to Mail.domain.com

I haven't been able to find any info on how to accomplish this yet. Any Ideas?
Thanks!

 

[SeanAIX430]

Well I think I found the way to change where the website and ftp sites go to right on the services page, it was in the manual, d'oh! I will have to try it and play around from outside to see if it's works.

I still haven't figured out how to setup mail.domain.com to go to 192.168.1.100/exchange though, so any thought would be appreciated!

 

[Castor66]

Hi,

I did reply to this just after you first posted it but something happened and I lost it. So here goes again!

I assume your main problem is that you have one public IP address, correct? If that's not the case then everything below will not apply

Ok, when you have only one address you need to be creative with ports. Assume your external IP is 1.2.3.4 and you have internal IP's of 192.168.1.100 for exchange and 192.168.1.200 for your new web/ftp server. Your external domain names are mail.domain.com and

http://www.domain.com.

Set your external DNS as follows:

mail.domain.com A 1.2.3.4

http://www.domain.com

A 1.2.3.4

Firewall Mappings

1.2.3.4:80 <-> 192.168.1.200:80 (HTTP)
1.2.3.4:21 <-> 192.168.1.200:21 (FTP)
1.2.3.4:25 <-> 192.168.1.100:25 (SMTP)

Question - do you need HTTPS for your web server?

If no then:

1.2.3.4:443 <-> 192.168.1.100:443 (HTTPS)
Create a self-signed certificate and apply it to IIS on your exchange server. Your employees can then access exchange on

https://mail.domain.com/exchange

If yes then:

1.2.3.4:443 <-> 192.168.1.200:443 (HTTPS)
1.2.3.4:8080 <-> 192.168.1.100:443 (HTTPS but through Port translation. Create a self-signed certificate and apply it to IIS on your exchange server. Your employees can then access exchange on

https://mail.domain.com:8080/exchange

The latter solution isn't as nice as the former but will work.

On your webserver put a redirection in place to send the employees off to another site if they just enter

http://mail.domain.com,

i.e.

http://mail.domain.com

brings up your default page. In your default page you have a check on the URL to see if it contains mail.domain.com. If it does then send them off to

https://mail.domain.com/exchange.

Hope this helps?

 

[SeanAIX430]

I'm so sorry, I have several Public IP addresses, so that isn't an issue. Should have included that.

http://www.domain.com

is .35, mail.domain.com is .36

My owa isn't presently https, but I'd like it to be. I still need to figure out the exact steps to do a redirect on the IIS server to go from mail.domain.com to

https://domain.com/exchange.

And that's after I figure out how to get the sonicwall to forward from the .36 address to the .35. Thanks