• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 496
  • Last Modified:

OWA issues

I'm running Exchange 2010 via SBS2011.  My Remote Web Workplace works fine remotely and internally.  However OWA does not.  I must add https:// in the beginning of the url in order for it to work.  If I don't, I get the 'Problem Loading Page' error.

Ideas?
0
creativenetworks
Asked:
creativenetworks
  • 8
  • 7
1 Solution
 
xenoninfotechCommented:
Hi

You should be accessing owa by https://   only .

Have you installed a trusted certificate.

Thanks

Xenoninfotech
0
 
Suliman Abu KharroubIT Consultant Commented:
0
 
creativenetworksAuthor Commented:
yes using a GoDaddy 3rd party UCC SSL
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Suliman Abu KharroubIT Consultant Commented:
Had you checked the provided link ?
0
 
creativenetworksAuthor Commented:
Reading it now.  What's unusual is that internal to the LAN, whey you type www.domainname.com/owa it goes to the proper website, but external to the lan, it does not and requires you type https:// in front of it in order for it to work.
0
 
Suliman Abu KharroubIT Consultant Commented:
Seems that you are publishing OWA on TMG or another firewall.... make sure that http port 80 is forwarded to exchange server...

but again it is not a good idea to access it without https.

If the firewall is TMG, you need to create a deny rule to redirect http://mail.domain.com/ https://mail.domain.com/owa
0
 
creativenetworksAuthor Commented:
It's a sonicwall TZ200.  Port 80 shows open via port checker.
0
 
Suliman Abu KharroubIT Consultant Commented:
try to telnet from outside to exchange public ip on port 80?
0
 
creativenetworksAuthor Commented:
I just rechecked and port 80 is showing closed.  what the heck?
0
 
Suliman Abu KharroubIT Consultant Commented:
Check the firewall, and if you enable http, make sure to confure http to https redirection as per the above link.
0
 
creativenetworksAuthor Commented:
when I check the bindings in IIS they all point correctly.
0
 
Suliman Abu KharroubIT Consultant Commented:
and the sonicwall firewall ? does it configured to forward http traffic to exchange server ?
0
 
creativenetworksAuthor Commented:
I'm not a sonicwall expert but it looks right
0
 
Suliman Abu KharroubIT Consultant Commented:
If you can access http from internal then it must be the sonicwall blocking http traffic from external or not forwarding it to exchange server ..
0
 
creativenetworksAuthor Commented:
You've got to be right.  I'm gonna call Sonicwall.
0
 
creativenetworksAuthor Commented:
Had to create a NAT policy in Sonicwall that went from Public IP to Private open.  Opened Port 80 then could access OWA successfully.,
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 8
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now