SBS 2003 OWA not working with external address
Hi
I’ve got a server running SBS 2003 and I’ve just installed a SSL certificate for remote.domainname.com and externally the certificate works fine and I can access OWA through https://remote.domainname.com/exchange. If I go to this address internally it doesn't work. if I go to http://servername/exchange it loads OWA fine. I've done a bit of research into how to get the same address https://remote.domainname/exchange working internally and externally and there's a few forum posts which talk about setting up split DNS, I've followed a couple of guides and cant quite get it working correctly.
If anyone could assist that would be greatly appreciated.
Thanks
I’ve got a server running SBS 2003 and I’ve just installed a SSL certificate for remote.domainname.com and externally the certificate works fine and I can access OWA through https://remote.domainname.com/exchange. If I go to this address internally it doesn't work. if I go to http://servername/exchange it loads OWA fine. I've done a bit of research into how to get the same address https://remote.domainname/exchange working internally and externally and there's a few forum posts which talk about setting up split DNS, I've followed a couple of guides and cant quite get it working correctly.
If anyone could assist that would be greatly appreciated.
Thanks
ASKER
The reason I want it to work internally and externally is because of mobile devices such as iPhones, they are used in the office connected to wifi and also outside the office so need to be setup with the same address in the email config.
ASKER
I have another client server which are also sbs 2003 and have the same type of ssl, it was setup a while ago but if I go to https://remote.domainname.com/exchange from inside and outside the network it loads fine and mobile devices work fine. So I know it can be done, I've gone through and compared the dns settings, iis settings and site bindings and can't see any differences so I'm not really sure why it works fine for one client but not the other.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hey
its not premium just the standard version.
I've setup the Forward lookup zone and A record as you have asked and that's now working fine :) I'm sure I tried that before and was getting a username and password pop up when trying to access the site but I must have done something wrong
Thanks for your help :)
its not premium just the standard version.
I've setup the Forward lookup zone and A record as you have asked and that's now working fine :) I'm sure I tried that before and was getting a username and password pop up when trying to access the site but I must have done something wrong
Thanks for your help :)
Glad I could help.
You wouldn't normally use secure HTTP to access your Exchange server from the LAN, which may be part of the problem.
As the internal and external methods you described both work, why not just set up appropriate shortcuts on the users' browser toolbars so that they can select whichever one fits the circumstances?