Solved

OWA Forwarding External requests to internal FQDN

Posted on 2008-10-20
4
632 Views
Last Modified: 2012-08-14
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
Comment
Question by:zillabunny
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 1

Expert Comment

by:abcsltd
ID: 22757305
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
 

Author Comment

by:zillabunny
ID: 22757337
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
 
LVL 1

Accepted Solution

by:
abcsltd earned 500 total points
ID: 22758408
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

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
A list of top three free exchange EDB viewers that helps the user to extract a mailbox from an unmounted .edb file and get a clear preview of all emails & other items with just a single click on mailboxes.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
This video discusses moving either the default database or any database to a new volume.

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question