Link to home
Start Free TrialLog in
Avatar of brynstar
brynstarFlag for United States of America

asked on

OWA wont connect remotely

Hello all

My server is setup with SBS 2003, I can send and receive email via the exchange server, and internally when you enter the https://myservername/exchange, the Outlook Web Access login screen appears and I am able to log in to check email.

If i enter https://81.xx.xx.xx/exchange into my Web browser (The static IP of my router) I get a page not displayed screen in firefox but with the following message

"Though the site seems valid, the browser was unable to establish a connection."

Is the static IP/exchange the way to  connect to OWA? Any thoughts or comments would be most appreciated.

Best Regards
Bryn
Avatar of premiumnz
premiumnz
Flag of New Zealand image

You can sometimes access OWA in that fashion.  However it comes down to how IIS is configured and whether the default web site has a blank host header or not.  Are you trying to use an internal IP address or external IP address?  If external, are you outside your organisation?

So you want to get to OWA from outside or inside?
Avatar of brynstar

ASKER

I can get to OWA inside the network fine via https://myserver/exchange

the IP address I am using is my public static IP

I'm inside my network but I have a colleague outside who's trying the external IP to access it
ASKER CERTIFIED SOLUTION
Avatar of premiumnz
premiumnz
Flag of New Zealand image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thank you premiumnz!

Works externally! Result! I'm getting an error though with the secure connection, I need to add an exception to allow the OWA login to load.

The certificate details show the SSL i created in the connect to internet wizard
mail.mydomainname.com

How can I add another certificate to the server so that the https://mystaticip/exchange loads without a security error?

Best Regards
Bryn
Bryn,  SSL certificates must be issued by an authority.  If you issue the certificate yourself then you will need to ensure that the FQDN (fully qualified domain name) matches the one you are using externally.  For example,  if the certicifate says mail.mydomain.com, then simply go to your external DNS provider and add an A record of "mail" to point to this IP address.  Then it will work properly.

Finally if it is self signed certificate, then you need to install the certificate in IE on the remote machine.  Browse to mail.mydomain.com/exchange.  Accept the certificate, then click on the certificate error up the top of IE (7) and select view certificate and then install.  This will ensure that you no longer get prompted.

Cheers.