Solved

Exchange 2007 OWA - Works internally, but not externally

Posted on 2011-02-14
15
607 Views
Last Modified: 2012-05-11
I feel like I am missing something simple.

I replaced a server running an inexpensive mail server program with a new Windows 2008 server with MS Exchange 2007.  The only thing that is not working os OWA.  I can access OWA with no problems from the network.  When I try to access it from outside, however, I get the "Page cannont be displayed" error.

I have reviewed the PIX firewall settings and we have both ports 80 and 443 open and directed to the Exchange server.  Is there something on the Exchange server that needs to be changed to permit access from off the network?

Thanks

0
Comment
Question by:tcampbell_nc
  • 8
  • 5
  • 2
15 Comments
 
LVL 5

Expert Comment

by:LLMorrisson
ID: 34890809
Is the URL for OWA the same internally as externally, or different?

Make sure the service URLs for the outlook web app are appropriately correct on your server config, client access role.
0
 
LVL 1

Author Comment

by:tcampbell_nc
ID: 34890900
They are different.  The internal has the FDQN of the server.  The external was blank.  I filled it in with the Internet address that resolves to our webmail access.  It still does not work.  Do I need to stop Exchange and restart it for that setting to take effect?
0
 
LVL 5

Expert Comment

by:LLMorrisson
ID: 34890915
Do you used a self-signed certificate or a real one?
0
 
LVL 1

Author Comment

by:tcampbell_nc
ID: 34890936
Self Signed
0
 
LVL 10

Expert Comment

by:ChopperCentury
ID: 34891709
Is the outside URL and IP address registered with the correct DNS A record through your domain registrar?
The outside facing address of your Exchange will need only port 443 permitted for outside traffic on your PIX.
The outside address with need to be NAT'd to your inside address of the Exchange Server....preferably to an Exchange 2003 Front End Server (but it is ok if you only have one server).
0
 
LVL 1

Author Comment

by:tcampbell_nc
ID: 34892005
Yes.

The outside Address is registered with an A Record.  NAT in in place on the PIX.  Only one server.
0
 
LVL 10

Expert Comment

by:ChopperCentury
ID: 34892080
Under the Authentication tab inside the properties of owa....check the box for Basic Authentication
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
LVL 1

Author Comment

by:tcampbell_nc
ID: 34892111
Not getting to an authentication screen.
0
 
LVL 10

Expert Comment

by:ChopperCentury
ID: 34892140
From the outside....if you ping https://webmail.me.com (your information), does it resolve to the outside ip address you have NAT'd to the Exchange server?
If Yes, is your External URL configuration in owa properties set to https://webmail.me.com/owa?

0
 
LVL 1

Author Comment

by:tcampbell_nc
ID: 34892199
Yes for the ping.

Sort of for the External url setting.  It was empty.  Now it is correct, but I have not had a chance to restart the server yet.  Does that setting require a restart?
0
 
LVL 10

Expert Comment

by:ChopperCentury
ID: 34892261
Exchange 2010 will prompt you if you need to restart the server or IIS after changes are made. If you received no prompt then you should be good.
0
 
LVL 1

Author Comment

by:tcampbell_nc
ID: 34892333
I have Exchange 2007


Just restarted the server.  No change.
0
 
LVL 10

Accepted Solution

by:
ChopperCentury earned 500 total points
ID: 34892388
You might try a port scanner on the outside ip address to make sure you are able to get to port 443 on the exchange server.
0
 
LVL 1

Author Comment

by:tcampbell_nc
ID: 34894071
Chopper,

You may have just solved my problem.  The port scanner showed that port 443 was not responding.  A much closer look at my PIX firewall config showed a typo on the Permit for https.  There is a 168 instead of a 169 in the outside IP address.  

I'll be back on site tomorrow to see if this was my problem.
0
 
LVL 1

Author Closing Comment

by:tcampbell_nc
ID: 34898542
OWA is functioning now.  I located a typo in the PIX firewall after confirming there was no port 443 access to the server.

Thanks
0

Featured Post

Why are Office 365 signatures so complicated?

Trying to setup transport rules for Office 365 email signatures and can’t quite figure it out? Having to test the signature over and over? Make things simple by using Exclaimer Cloud - Signatures for Office 365.

Question has a verified solution.

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

Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
Since pre-biblical times, humans have sought ways to keep secrets, and share the secrets selectively.  This article explores the ways PHP can be used to hide and encrypt information.
In this video we show how to create a Distribution Group 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 >>…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

912 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

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now