wedmonds1
asked on
Exchange 2013 and Outlook 2007, 2010, 2013 Cannot connect
Hi Chaps,
I have wasted so much time on this that I am hoping someone can hold my hand and take me through some basic steps.
I have two servers both running Server 2012 Standard.
x 1 = Mainserver01 Domain Controller
x 1 = Mainserver02 Exchange 2013
At this time I am only interested in getting my internal clients to connect via outlook and this is proving to be the most difficult thing I have ever encountered.
I have previously deployed a single server that hosted both the Domain Controller and Exchange and all went well. This could be internal DNS related as I am not an expert but I am open and happy to try anything. Happy to carry out tests again and again if it means I get this sorted with your help.
Internally I can connect via https://servername.internaldomain.local/owa
Mail sends and receives via this and all is good.
However, I cannot get any outlook clients to connect.
When I start up (for example) Outlook 2010, it automatically fills in the users details and they all appear to be correct. I get
Establish network connection - Ticked Green
Search for username@externaldomain.co
Then it hangs at log on to server and says: The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
When I click OK, I am presented with the check name screen and it shows the GUID long number as the exchange server xxxxxx@externaldomain.com
and =SMTP: username@externaldomain.co
Server: mainserver02.internaldomai
I click More Settings and then go to the Connection Tab and tick Connect to Microsoft Exchange using HTTP and click Exchange Proxy Settings.
In there I complete "https://mainserver02.internaldomain.local"
I tick on fast networks
I select NTLM (i have tried them all at some point!)
It simply will not connect... anyone got any suggestions??
Hope so ... its an experts exchange! :)
I have wasted so much time on this that I am hoping someone can hold my hand and take me through some basic steps.
I have two servers both running Server 2012 Standard.
x 1 = Mainserver01 Domain Controller
x 1 = Mainserver02 Exchange 2013
At this time I am only interested in getting my internal clients to connect via outlook and this is proving to be the most difficult thing I have ever encountered.
I have previously deployed a single server that hosted both the Domain Controller and Exchange and all went well. This could be internal DNS related as I am not an expert but I am open and happy to try anything. Happy to carry out tests again and again if it means I get this sorted with your help.
Internally I can connect via https://servername.internaldomain.local/owa
Mail sends and receives via this and all is good.
However, I cannot get any outlook clients to connect.
When I start up (for example) Outlook 2010, it automatically fills in the users details and they all appear to be correct. I get
Establish network connection - Ticked Green
Search for username@externaldomain.co
Then it hangs at log on to server and says: The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
When I click OK, I am presented with the check name screen and it shows the GUID long number as the exchange server xxxxxx@externaldomain.com
and =SMTP: username@externaldomain.co
Server: mainserver02.internaldomai
I click More Settings and then go to the Connection Tab and tick Connect to Microsoft Exchange using HTTP and click Exchange Proxy Settings.
In there I complete "https://mainserver02.internaldomain.local"
I tick on fast networks
I select NTLM (i have tried them all at some point!)
It simply will not connect... anyone got any suggestions??
Hope so ... its an experts exchange! :)
Get a trusted SSL certificate would be the first thing I would do.
Then ensure that the external host name on the server resolves internally to Exchange and you have set all of the internal and external URLs to the correct setting.
My article here: http://semb.ee/hostnames goes through the process for Exchange 2010, the script at the end works for Exchange 2013 also.
Simon.
Then ensure that the external host name on the server resolves internally to Exchange and you have set all of the internal and external URLs to the correct setting.
My article here: http://semb.ee/hostnames goes through the process for Exchange 2010, the script at the end works for Exchange 2013 also.
Simon.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It works and I can replicate and explain it!
ASKER
All others still do not connect using 2013 and 2007.
Also server itself with outlook 2013 installed directly on it will not connect.
I exported the working cert from the working machine and imported as CA on another 2010 machine and it still fails. Further investigation makes me think it could still be a cert problem as I cannot see my newly imported cert in the CA. I view it from IE and it shows up on working outlook 2010 but not on the new one I am trying to get working.
any ideas chaps?