ActiveSync Works but Exchange will not connect

We've recently configured a new Server 2012 with exchange 2013. Everything seems to have gone well.

For some reason, We are unable to connect to the exchange server from a clients PC using the exchange option however, if we choose activeSync then we are able to access the mail. What is the difference between activeSync and Exchange option in outlook and what could be causing the issue?

I've already checked the DNS and the client machine is connected to the domain. The owa can be used successfully on the clients PC. I've tried everything I can think of to debug the issue and I think it will be something stupid that I have forgotten to do to enable this. Has anyone got any suggestions as to what this may be?

I will note however that there is no internet at all and this is just through an internal network that has been configured. So the emails I have tested have been to local email addresses.

Also, the error that I am recieving when I connect from outlook via exchange option is:
The action cannot be completed. The connection to microsoft exchange is unavailable. Outlook must be online or connected to complete this action.

  • Edited by LSorsby Monday, August 03, 2015 1:11 PM Added more information
August 3rd, 2015 1:06pm

Hi Darren,

This is a new installation so I haven't got any clients working on this yet. The new installation also didn't seem to work either unfortunately.

Free Windows Admin Tool Kit Click here and download it now
August 4th, 2015 6:58am

Allen,

I know that it isn't recommended however as this is a small business I haven't got much option as I only have the one server at my disposal.

Get-OutlookAnywhere:

Hostname: servername.domain.tdl (which is the one I'm using to try and connect to the exchange) This also resolves if I ping that domain from the client pc.

Authentication: Ntlm

SSL: internal clients require ssl (this is a self-signed cert) which I have put into the trusted root CA on the client PC

Get-OutlookProvider:

Server seems to be null

CertPrincipalName also seems to be null

Get-ClientAccessServer:

autodiscover URI is https://servername.domain.tdl/Autodiscover/Autodiscover.xml

identity is the servername

August 4th, 2015 7:06am

Just to add to the issue: I've just run:

Get-ClientAccessServer | Test-OutlookWebServices -Identity alias@domain.co.uk -MailboxCredential (Get-Credential)

This prompted me for the username and password. However all four of them failed.

Autodiscover: outlook provider failed

Exchange Web Services: failed

Availability Service Skipped

Offline address book: failed

Could this be an SSL issue?


Free Windows Admin Tool Kit Click here and download it now
August 4th, 2015 9:34am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics