Solved

unable to access owa externally

Posted on 2004-09-19
2
359 Views
Last Modified: 2008-02-20
I am able to access email through my owa client sitting on my local network but only by the local ip address.  Not sure why, but I can't access the site by name nor can I access the site externally by public IP.  I have checked everything. My external DNS records are correct, I can resolve the name to the correct ip address and my firewall is open on port 443 as needed.  I'm not an IIS person, but everything is pointing to it as the problem.  How does IIS advertise itself?  How does the firewall know that https requests need to go to the exchange server?
0
Comment
Question by:sunny10
2 Comments
 
LVL 104

Accepted Solution

by:
Sembee earned 125 total points
ID: 12102410
IIS doesn't annouce  itself, you have to send the traffic to it.

First - the internal and external DNS records need to be different.
Internally you need your clients to look at the internal IP address of the Exchagne server. This is achieved by adjustign the DNS as required.
If you are using a generic name for OWA (mail.domain.com for example) but the server is called something else (server1.domain.com) then add an additional entry in to your local DNS for mail.domain.com and point it at the IP address of the Exchange/OWA server.

Externally the clients need to be pointing at the external IP address of your connection. If you have mutiple IP addresses then it needs to be the one assigned to the Exchange/OWA server.

This is known as split DNS.

Confirm that it is working as you like internally, and then move forwards to get external to work.

Next. Your firewall.
You are probably using NAT/Port Forwarding. Configure the firewall to forward requests on port 443 received on the relevant external IP address to the internal IP address of your Exchange/OWA server.
You haven't said which firewall you are using, but if you have already setup forwarding for port 25 (SMTP) then I would just copy the configuration and change the port to 443.

Simon.
0
 

Author Comment

by:sunny10
ID: 12122738
Your line of questioning got me started on the right track, when I went back and checked the router I noticed that the port forwarding had been set up incorrectly.  Once I fixed the IP address everything worked.  Thanks for your help.
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

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

Lotus Notes – formerly IBM Notes – is an email client application, while IBM Domino (earlier Lotus Domino) is an email server. The client possesses a set of features that are even more advanced as compared to that of Outlook. Likewise, IBM Domino is…
We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…

832 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