Outlook Web Access

Hi All,

We have recently installed a Server within a clients off - SBS 2008 (2nd hand)

This is a fresh install and everything works fine apart from the owa externally, it works internally fine using either https://servername/owa or https://remote.domain.com/owa

We can't even access the remote site from externally.

When we type in the static ip address into a browser it shows the IIS7 page for the http (port 80 redirect is working fine)

You would think it's an issue with the open ports but I have all the ports open on the Draytek 2830n router - 80,443,987 - i have even tested these on here - http://www.yougetsignal.com/tools/open-ports/

IIS seems to be running fine too, all the virtual directories are under the SBS Web Applications site and running.

I have even turned the server firewall off to see if that was blocking, still no luck.

Another strange thing is that when we open outlook a certificate pops up with autodiscover.domain.com as well as a few others of m.domain.com / mobile.domain.com / sites.domain.com - we do however have a RAPID SSL cert installed for remote.domain.com

Any ideas?

R
ryank85Asked:
Who is Participating?
 
Cliff GaliherCommented:
Sounds like you have a wildcard DNS record causing some problems. Note that this Woolf be an external record and not anything to do with SBS.

Additionally, some routers, and I know Draytek to be one of them, have an option to allow remote connections via SSL. Of that option is enabled, it will supersede and control port 443, despite any port forwarding rules you have. That would also mean any open port testing website/software would back with a positive result because the router IS responding on 443...but that traffic is not reaching your server.
0
 
Simon Butler (Sembee)ConsultantCommented:
Was the certificate installed through SBS? There are multiple web sites and things can get complicated if the wizards in SBS were not used.

Outlook clients will connect to autodiscover.example.com by default as part of their configuration process. You either need to change the SSL certificate for something that can include that as one of the additional domains, or you need to configure SRV records for autodiscover on your external DNS.

Simon.
0
 
ryank85Author Commented:
Hi

I installed the SSL cert through SBS Console, I can't even access the OWA using the static ip address either

I have rebooted the router again and now when I test the 443 port is doesn't show this as open.

When you say an external DNS issue, so this could be something on their hosting side, i.e 123-reg?

I will check the router for the SSL option

thanks

R
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
ryank85Author Commented:
cgaliher - absolutely spot on with the SSL solution, changed the SSL option in the router to 449 and OWA worked - this must be a new option in the latest firmware as i've not seen that before.

With regards to the certicate popups would you recommend moving away from 123-reg or would this be something different, I notice on some hosting platforms you have either an A Record or CNAME record of autodiscover.domain.com - i notice this domain doesnt under their DNS settings on 123-reg

thanks again
R
0
 
Cliff GaliherCommented:
Whether you relocate or not is up to you. But cleaning up your external records would be a requirement either way.
0
 
ryank85Author Commented:
All sorted, we installed rollup 9 for exchange and everything works ok now

R
0
 
ryank85Author Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for ryank85's comment #a39333021

for the following reason:

resolved ourselves
0
 
Cliff GaliherCommented:
Your first and primary question was about OWA not working externally. Granted you did resolve the certificate issue yourself (which is why lumping multiple questions in EE should be discouraged) but the FIRST question you asked was about OWA. You rightly acknowledged that the router was the cause as I pointed out. You did NOT resolve the issue without the assistance of EE.
0
 
ryank85Author Commented:
Apologies, cgaliher resolved the OWA issue. I resolve the issue about the certificate.

Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.