Autodiscover service and related issues

Discussion:

(too old to reply)

ian middleton

2007-11-21 18:02:00 UTC

We are having some problems with autodiscover. We have a NLB Exchange 2007
CAS server. Clients accessing it via OWA are able to use full set of
features (OOF, Meeting Assistant, etc). However, if we connect using Outlook
2007 these features are unavailable. New user settings ARE automatically
detected and basic connection settings are fine.

The autodiscover DNS A record points to the IP address of our NLB cluster.

When we test the settings from Outlook we get the following:

Attempting URL https://<nlb>.<my domain>/Autodiscover/Autodiscover.xml found
through SCP
Autodiscover to https://<nlb>.<my domain>/Autodiscover/Autodiscover.xml
starting
Autodiscover request completed with http status code 404
Autodiscover to https://<nlb>.<my domain>/Autodiscover/Autodiscover.xml
FAILED (0x80004005)
Autodiscover to https://<my domain>/Autodiscover/Autodiscover.xml starting
Autodiscover to https://<nlb>.<my domain>/Autodiscover/Autodiscover.xml
FAILED (0x800C8203)
Autodiscover to https://autodiscover.<my
domain>/Autodiscover/Autodiscover.xml starting
Autodiscover request completed with http status code 404
Autodiscover to https://autodiscover.<my
domain>/Autodiscover/Autodiscover.xml FAILED (0x80004005)
Local autodiscover for <my domain> starting
Local autodiscover for <my domain> FAILED (0x8004010F)
Redirect check to http://autodiscover.<my
domain>/Autodiscover/Autodiscover.xml starting
Redirect check to http://autodiscover.<my
domain>/Autodiscover/Autodiscover.xml FAILED 90x80072EE7)

Any sensible suggests welcomed at this point.

Rodney R. Fournier [MVP]

2007-11-21 18:53:46 UTC

Permalink

What address are you using for NLB? What certs do you have on the CAS
servers? Are you using Subject Alternative Names (SAN)?

Cheers,

Rodney R. Fournier

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner

Post by ian middleton
We are having some problems with autodiscover. We have a NLB Exchange 2007
CAS server. Clients accessing it via OWA are able to use full set of
features (OOF, Meeting Assistant, etc). However, if we connect using Outlook
2007 these features are unavailable. New user settings ARE automatically
detected and basic connection settings are fine.
The autodiscover DNS A record points to the IP address of our NLB cluster.
Attempting URL https://<nlb>.<my domain>/Autodiscover/Autodiscover.xml found
through SCP
Autodiscover to https://<nlb>.<my domain>/Autodiscover/Autodiscover.xml
starting
Autodiscover request completed with http status code 404
Autodiscover to https://<nlb>.<my domain>/Autodiscover/Autodiscover.xml
FAILED (0x80004005)
Autodiscover to https://<my domain>/Autodiscover/Autodiscover.xml starting
Autodiscover to https://<nlb>.<my domain>/Autodiscover/Autodiscover.xml
FAILED (0x800C8203)
Autodiscover to https://autodiscover.<my
domain>/Autodiscover/Autodiscover.xml starting
Autodiscover request completed with http status code 404
Autodiscover to https://autodiscover.<my
domain>/Autodiscover/Autodiscover.xml FAILED (0x80004005)
Local autodiscover for <my domain> starting
Local autodiscover for <my domain> FAILED (0x8004010F)
Redirect check to http://autodiscover.<my
domain>/Autodiscover/Autodiscover.xml starting
Redirect check to http://autodiscover.<my
domain>/Autodiscover/Autodiscover.xml FAILED 90x80072EE7)
Any sensible suggests welcomed at this point.

ian middleton

2007-11-21 22:31:01 UTC

Permalink

NLB address is 192.168.123.179

made up from 2 blade servers
blade 1 =192.168.123.152
and blade 2 =192.168.123.153

and Exchange 2007 server has a self-signed SSL certificate

we are not using Subject Alternative Name

thanks for looking at this

Post by Rodney R. Fournier [MVP]
What address are you using for NLB? What certs do you have on the CAS
servers? Are you using Subject Alternative Names (SAN)?
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner

ian middleton

2007-11-23 14:21:04 UTC

Permalink

we have progressed a little if i add the nlb into the do not proxy local
adresses exceptions box eg

nlbcl-bl-3-4.domain.com
even though its already covered by the 192.168.123.*
which is where nlbcl-bl-3-4.local.mount.n-yorks.sch.uk point back to in dns.
thius seems to clear aLL But offline address book see below

12:47:26 Synchronizer Version 12.0.6024
12:47:26 Synchronizing Mailbox 'Ian Middleton'
12:47:26 Synchronizing Hierarchy
12:47:27 Done
12:47:29 Microsoft Exchange offline address book
12:47:29 0X80190197

ideas welcomed

Post by ian middleton
NLB address is 192.168.123.179
made up from 2 blade servers
blade 1 =192.168.123.152
and blade 2 =192.168.123.153
and Exchange 2007 server has a self-signed SSL certificate
we are not using Subject Alternative Name
thanks for looking at this

Rodney R. Fournier [MVP]

2007-11-23 19:14:34 UTC

Permalink

You need a public cert for Audodiscovery, I believe the self-signed one only
works with internal addresses, but I could be wrong. I have only used real
Public ones.

Cheers,

Rodney R. Fournier

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner

Post by ian middleton
we have progressed a little if i add the nlb into the do not proxy local
adresses exceptions box eg
nlbcl-bl-3-4.domain.com
even though its already covered by the 192.168.123.*
which is where nlbcl-bl-3-4.local.mount.n-yorks.sch.uk point back to in dns.
thius seems to clear aLL But offline address book see below
12:47:26 Synchronizer Version 12.0.6024
12:47:26 Synchronizing Mailbox 'Ian Middleton'
12:47:26 Synchronizing Hierarchy
12:47:27 Done
12:47:29 Microsoft Exchange offline address book
12:47:29 0X80190197
ideas welcomed

Post by ian middleton
We are having some problems with autodiscover. We have a NLB
Exchange
2007
CAS server. Clients accessing it via OWA are able to use full set of
features (OOF, Meeting Assistant, etc). However, if we connect using Outlook
2007 these features are unavailable. New user settings ARE automatically
detected and basic connection settings are fine.
The autodiscover DNS A record points to the IP address of our NLB cluster.
Attempting URL https://<nlb>.<my
domain>/Autodiscover/Autodiscover.xml
found
through SCP
Autodiscover to https://<nlb>.<my
domain>/Autodiscover/Autodiscover.xml
starting
Autodiscover request completed with http status code 404
Autodiscover to https://<nlb>.<my
domain>/Autodiscover/Autodiscover.xml
FAILED (0x80004005)
Autodiscover to https://<my domain>/Autodiscover/Autodiscover.xml starting
Autodiscover to https://<nlb>.<my
domain>/Autodiscover/Autodiscover.xml
FAILED (0x800C8203)
Autodiscover to https://autodiscover.<my
domain>/Autodiscover/Autodiscover.xml starting
Autodiscover request completed with http status code 404
Autodiscover to https://autodiscover.<my
domain>/Autodiscover/Autodiscover.xml FAILED (0x80004005)
Local autodiscover for <my domain> starting
Local autodiscover for <my domain> FAILED (0x8004010F)
Redirect check to http://autodiscover.<my
domain>/Autodiscover/Autodiscover.xml starting
Redirect check to http://autodiscover.<my
domain>/Autodiscover/Autodiscover.xml FAILED 90x80072EE7)
Any sensible suggests welcomed at this point.