We have anSBS 2008 server which is running just fine. However OWA cant be accessed externally via https://XXX.XXX.XXX.XXX/owaall of a sudden (it was fine last week) I checked all the firewall ports and the router has NAT setup to allow 443, 80, 987, and 25 to point at the servers IP address (192.168.1.10) This is the odd bit - I spent ages looking through the logs and nothing is reported, I tried accessing the site from different locations and using different browsers on different PC's. All of a sudden I tried accessing it from my iPhone - hey presto the pages comes up in Safari! Any ideas? its driving me mad! To recap - https://XXX.XXX.XXX.XXX/owacannot be accessed externally on any device other than an iPhone. It works perfectly internally. ANother addition to this post - when I run the fix my network wiuzard it comes up with one issue shown below: could this be an SSL issue? does an iphone bypass SSL. Can I try turning off SSL for OWA? Component ID #4 If the Fix My Network wizard shows that component ID #4 is broken, this means that the TSGateway service is not configured to correctly use the SSL certiifcate configured within IIS. Continuing to fix this error within the wizard will configure TSGateway property to use the SSL certificate configured inside of IIS and restart the TSGateway service so it will pick up the correct certificate.

Just a thought - when we used to access it via https://xxx.xxx.xxx.xxx/owa we'd get a certificate error to whcih we'd always press continune. However now we just get "page can not be displayed". However I think that an iphone never asks for a cert (you'd never see this screen shot on an iphone)

On Fri, 23 Mar 2012 14:41:05 +0000, James Hamilton 1 wrote: > > >We have anSBS 2008 server which is running just fine. However OWA cant be accessed externally via https://XXX.XXX.XXX.XXX/owaall of a sudden (it was fine last week) I checked all the firewall ports and the router has NAT setup to allow 443, 80, 987, and 25 to point at the servers IP address (192.168.1.10) > >This is the odd bit - I spent ages looking through the logs and nothing is reported, I tried accessing the site from different locations and using different browsers on different PC's. All of a sudden I tried accessing it from my iPhone - hey presto the pages comes up in Safari! > >Any ideas? its driving me mad! > >To recap - https://XXX.XXX.XXX.XXX/owacannot be accessed externally on any device other than an iPhone. It works perfectly internally. > >ANother addition to this post - when I run the fix my network wiuzard it comes up with one issue shown below: could this be an SSL issue? does an iphone bypass SSL. Can I try turning off SSL for OWA? > >Component ID #4 If the Fix My Network wizard shows that component ID #4 is broken, this means that the TSGateway service is not configured to correctly use the SSL certiifcate configured within IIS. Continuing to fix this error within the wizard will configure TSGateway property to use the SSL certificate configured inside of IIS and restart the TSGateway service so it will pick up the correct certificate. You'll probably get a better answer in the SBS forum. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Fri, 23 Mar 2012 14:41:05 +0000, James Hamilton 1 wrote: > > >We have anSBS 2008 server which is running just fine. However OWA cant be accessed externally via https://XXX.XXX.XXX.XXX/owaall of a sudden (it was fine last week) I checked all the firewall ports and the router has NAT setup to allow 443, 80, 987, and 25 to point at the servers IP address (192.168.1.10) > >This is the odd bit - I spent ages looking through the logs and nothing is reported, I tried accessing the site from different locations and using different browsers on different PC's. All of a sudden I tried accessing it from my iPhone - hey presto the pages comes up in Safari! > >Any ideas? its driving me mad! > >To recap - https://XXX.XXX.XXX.XXX/owacannot be accessed externally on any device other than an iPhone. It works perfectly internally. > >ANother addition to this post - when I run the fix my network wiuzard it comes up with one issue shown below: could this be an SSL issue? does an iphone bypass SSL. Can I try turning off SSL for OWA? > >Component ID #4 If the Fix My Network wizard shows that component ID #4 is broken, this means that the TSGateway service is not configured to correctly use the SSL certiifcate configured within IIS. Continuing to fix this error within the wizard will configure TSGateway property to use the SSL certificate configured inside of IIS and restart the TSGateway service so it will pick up the correct certificate. You'll probably get a better answer in the SBS forum. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP