Autodiscover... Still...

[GRitchie]

Still having Autodiscover problems on a new Exchange 2013 server.

 

When running Test-OutlookWebServices on a mailbox, it says 'Autodiscover: Outlook Provider' 'FAILURE'

 

Been hacking away for days, hopefully someone can shed some light on the situation.

Ask as many questions as you need!

[iom100]

Have you used https://testconnectivity.microsoft.com?

[GRitchie]

Yeah - autodiscover etc. all comes back okay (the odd one gives a trusted root warning, but that's only due to a self-signed certificate)

[iom100]

You're going to want to get a proper certificate on there, with the correct names.

[GRitchie]

As much as I'd like to, we cannot - due to budget limitations.

The issue isn't with the cert; autodiscover works perfectly externally and I distribute the self-signed cert via a GPO to suppress warnings.

[HPlum78]

get-clientaccessserver

[GRitchie]

Returns the internal server hostname

[HPlum78]

sorry | fl at the end and could do with having a look at the output if possible, also what have you got as your _TCP autodiscover SRV dns?

[GRitchie]

Excuse some of the server names shown (not my choice at the time)

 

I have now removed the SRV record as it didn't solve things, didn't want to leave half fixes laying around when they weren't working; should I create one of those again or?

[HPlum78]

did your SRV point to the AutoDiscoverServiceInternalUri so mail.cartmelprioryschool.co.uk on port 433?

[GRitchie]

I can't remember to be exact. Are you able to advise on what it should be and which zone?

 

Thanks.

[HPlum78]

Should be in the cps.local zone. Let me know . H

[GRitchie]

Hello,

Looks like this now - that right?

[GRitchie]

UPDATE: This has fixed the wizard not autofilling the account from AD.

It still errors with the same 'Cannot connect to Exchange Server' etc:

 

Pressing 'OK' displays this box:

[GRitchie]

To add to the confusion, if I set outlook up with no email accounts and then 'Test Email Auto-configuration' it all seems to be okay?

 

[mdrabble]

In DNS do you have a DNS zone for external domain name?

 

If not, add it as a primary zone and then add your mail server name and autodiscover into that new zone

Edited September 18, 2015 by mdrabble

[GRitchie]

Zone for the external:

 

Edit: 10.105.16.13 is the internal IP of the Exchange Server.

[mdrabble]

add AutoDiscover in to the zone as well using the same ip

[GRitchie]

as an A record and with PTR?

It was previously, I literally just removed it!

[mdrabble]

I have mine as A Name

[GRitchie]

Okay, all created.

I should be able to /flushdns on a client to force propagation shouldn't I?

[mdrabble]

yep flush dns and then try pinging autodiscover url

[GRitchie]

Okay, that now resolves the internal server IP address (from a ping)

 

UPDATE:

Still the same errors within Outlook

[HPlum78]

 

So outlook seems to be using the SRV DNS entry although not getting the mail sever!, while I think about that lets take a look at the SCP. The above is a screen shot of AD Sites and Services take a look at that on your network drill down to your mail server and look at the attribute editor and check that the serviceBindingInformation attribute is https://mail.cartmelprioryschool.co.uk/autodiscover/autodiscover.xml

 

H

[GRitchie]

Just checked that @HPlum78 - all looks correct