?
Solved

unable to access owa externally

Posted on 2004-09-19
2
Medium Priority
?
389 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 500 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

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

Question has a verified solution.

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

Eseutil Hard Recovery is part of exchange tool and ensures Exchange mailbox data recovery when mailbox gets corrupt due to some problem on Exchange server.
Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Suggested Courses

850 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