• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 646
  • Last Modified:

OWA Forwarding External requests to internal FQDN

I added a second Mail server to my network, moved mail boxes, after the mail box move when I go to the OWA site I'm getting the log in(old serveR) but accoutns moved from the old server to the new server are getting a 404 DNS Error and url is the INTERNAL FQDN address, not the external URL

These are microsoft exchange 2003 mail servers
0
zillabunny
Asked:
zillabunny
  • 2
1 Solution
 
abcsltdCommented:
If you require both servers to be running on the network at the same time you could change the port of the OWA on the new 2nd Excahnge server and then add a port forward on the router or firewall.

Then you would need to create a website redirect or get users to type http://domain.com:new port to get to the 2nd server
0
 
zillabunnyAuthor Commented:
ok this is almost excatly what I need to do. Can you please give me some info on the website redirect, when I forwaded HTTPS traffic to the new internal IP it began working perfect



What changes do I need to make in IIS to have the new port correctly set up.

Thanks!

0
 
abcsltdCommented:
The way I have done it in the past is to setup a new website in IIS which has a seperate host header.  For this to work I recomened that you create a new cname value with your DNS server or domain hosting company so that if you type ms2.domain.com it points to your IP address.

Then on the primary IIS server (e.g. the one you forward port 80 to) create a new website with the host header name created above (e.g. ms2.domain.com) and run it on port 80. create a blank index.html file in the root directory of the new website.

In IIS go to the new website and right click on the newly created index.html and click properties, in the field "The content for this resource should come from" click the button that says "A redirection to a url" and then type in the FQDN address of your server with the port number your second server is running on e.g. https://domain.com:port.

Then when your users type ms2.domain.com they are presented with the webmail login screen.

Another way would be to create a new virtual directory on the primary IIS server called exchange2 and do the same redirection as outlined above. The only difference being that the user has to type domain.com/exchange2.

This is a 301 redirect or permenant website redirection and there are quite a few resources online for step by step walkthrough.

Hope this helps.


0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

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