asciiassasin
asked on
Cannot connect to Exchange 2013 from outside network.
I have set up Exchange 2013 on a new Windows 2012 server that is running in Hyper-V. There is also a Domain Controller running in Hyper-V.
We can connect to the Exchnage server internally without a problem, but when I try and connect from outside on my Nexus 4, using our IP address, I get an error that says...
We can connect to the Exchnage server internally without a problem, but when I try and connect from outside on my Nexus 4, using our IP address, I get an error that says...
microsoft.exchange.webservices.data. ServiceReq uestExcept ion: The request failed. Error message is 'HTTP error: Forbidden (403)'
'->
microsoft.exchange.webservices.data. HttpErrorE xception.H TTP error: Forbidden (403)
Are you trying to use OWA to connect externally or active sync? Make sure SSL is turned off on the IIS directories for OWA or Active Sync internally on your backend exchange server and try again.
Is do you have TCP port 443 open to your Exchange server with a certificate applied to the server? Usually forbidden on HTTP means only HTTPS is allowed. I believe the phones try both automatically but the server may only be accepting HTTPS. If that isn't open to the server on the firewall then it won't work.
ASKER
There is no SSL certificate. Company hasn't purchased one and will not.
HTTP and HTTPS (80 & 443) are being forwarded to the Exchange server from the router. Should these be forwarded to the Domain Controller instead?
192.168.10.8 is the Domain Controller and 192.168.10.9 is the Exchnage 2013 server.
HTTP and HTTPS (80 & 443) are being forwarded to the Exchange server from the router. Should these be forwarded to the Domain Controller instead?
192.168.10.8 is the Domain Controller and 192.168.10.9 is the Exchnage 2013 server.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That was it! OWA should have been pointed to the Exchange Server - NOT the Domain Controller.
I suppose you could configure DNS on the DC to route that...but it is working as is.
Thanks for your help!
I suppose you could configure DNS on the DC to route that...but it is working as is.
Thanks for your help!