I have installed a new exchange 2013 server (standard) on a server 2012 R2.

Its up and running and I can access it just fine through owa.

I have made autodiscover service records, cnames and when I run the remote connectivity analyzer and test outlook connectivity

it goes green. and so do the other tests.

But when I actually do try to set it up with an outlook 2013 client. The auto discovery works fine.

Everything gets filled in, I click next and finish  and then outlook 2013 client cannot start due to Error.

It says I have to make a connection before I can sync.

I have installed a certificate, not self signed but a real one.

There is just nothing around describing it from a to z how to get a setup working without having a hosting party involved but just a local exchange 2013 server connected to internet with certificate, and a local installed office 2013 outlook client that needs to connect to it.  Why if it works fine with the webclient is it such a pest to get it to work with an outlook client???

if the certificate is good, the autodiscovery works, why does it still not just connect. Its a big mistery to me but perhaps I miss some easy clue.. internal and external urls are the same and its just 1 server no load balancing involved or special high availability stuff.. Just simple 1 to 1 setup.    I was really amazed that it did not work right away.. 

Well I am open to good solutions or hints to continue to hunt it down. I did turn on logs in registry for outlook client and see some unautorized access responce 401 5   with the autodiscover.sync.1.log  and thats quite strange. but perhaps it helps someone to figure out what goes wrong.

Check your Outlook Anywhere configuration.  You might also use the Outlook Test E-mail Autoconfiguration feature to see what URLs are returned.

Wen I start outlook without an email account, to get to that Outlook Test E-mail Autoconfiguration feature the results look ok XML logs also. The urls are correct. the correct guid name shows up. Autodiscovery succes (0x00000000).

Now its a bad screen to look at since the lines are to long and only the xml part can be copied, and ofcourse if you don't know what you are looking for it makes it hard to use. Exchange HTTP, Server name is the same one as configured in outlook anywhere, a user name, HSL  Mutual authentication:yes  4 urls (ews oab), negotiate.

The outlook anywhere has the correct server names, SSL offloading and negotiate. 

Its so strange that it configures outlook and then it won't work.  I am thinking more in some service not running, a firewall rule that blocks something or something on the exchange server that stops it for connecting correctly after outlook is finished autoconfiguring.

When I look in autodiscover.sync.1.log  I do see:

http request: https://domain.com/autodiscover/autodiscover.xml

http response: 65535 12017 http request canceled

http request https://autodiscover.domain.com /autodiscover/autodiscover.xml

http response: 401 5 unauthorized access

Its beyond me why it would auto configure correctly on a domain joined vda 8.1 with outlook 2013 client and with the correct user and still won't work.

It seems there is something that needs to be done that I did overlook. in owa exchange sends and recieves mail so that part is working. 

perhaps there is something wrong with rpc ? firewall? or some rights issue? settings on iis I have looked around quite a bit and see people having the same problems without solutions.

Since its a totally new setup I don't understand why it is so hard to get outlook 2013 client to work with exchange 2013. The must be something basic missing. I first thought it was just because of the SSL certificate, but since thats valid it is still no go.

Is the computer domain-joined?  It looks like the Autodiscover process that's being used is for a non-domain-joined machine.

It's having problem with Autodiscover according to your notes.  The https://domain.com/... URL failing is normal because Outlook always tries that first although nobody in the world published Autodiscover using that URL.  The second one should be passing if you're expecting Autodiscover to work.  Do you have a valid certificate that's trusted by the client?  Are you authenticating with a valid account?

Hi Robert,

to me it sounds the outlook provider is misconfigured. unfortunately the http://www.testexchangeconnectivity.com/ does not provide proper results for a client on your own domain, as it does not check the internal SCP.

As Outlook uses a different service from OWA, etc., you need to check your service. Please provide the output of your Exchange Management Shells

Test-OutlookWebServices | fl

please also provide the output of

get-outlookprovider | fl

and also check if the "use rpc proxy" setting in Outlook is checked for both, fast networks as well as slow networks. (for now I assume this is the setting that is wrong)

please let us know the output to prevent you from trial and error.

Regards,
Martin

 

Hi Robert,

Thank you for your question.

Did this issue occur on the same site?

If Exchange and outlook are different site, we could disable anti-virus to check if the issue persist.

If Exchange and outlook are same site, we could check configuration as above suggestion.

We could rebuild the virtual directory which is EWS by the following link:

https://technet.microsoft.com/en-us/library/ff629372%28v=exchg.141%29.aspx

Notice: this is a link which is about Exchange 2010, but it adapt to Exchange 2013.

In addition, we could check IIS log and send them to ibsexc@microsoft.com for our troubleshooting.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

I tried something else and did take a look at this part

On all Exchange 2013 SP1 Client Access servers, add the COMPLUS_DisableRetStructPinning Windows environment variable by performing the following steps.

1. In a Command prompt window, run systempropertiesadvanced and click Environment Variables.

2. In the System variables section, click New and enter the following information.

   • Variable name   COMPLUS_DisableRetStructPinning

   • Variable value   1

3. When you are finished, click OK.

Configuration