Exchange 2007 Autodiscover using SRV recrods

I am having an issue with testing Outlook Anywhere using the SRV record method. The record is setup for our domain but when I run the Test e-mail AutoDiscover from Outlook 2007 I am told that the SRV recrod failed with an error of 0x800C8206

2 Lines from Outlook 2007 Log file:
"Srv Record lookup for domain.org starting"
"Srv Record lookup for domain.org FAILED (0x800C8206)"

I have been trying to find out what 0x800C8206 translates to and haven't yet found anything. I know that the autodicover service works because I also made an A record of "autodiscover.domain.org" and the XML response is returned.

In addition I am also able to query the DNS record of _autodiscover._tcp.domain.org from the system I am testing from and the correct record is returned.

I would like to use the SRV record method becuase we host many different domains for various companies. Having to setup mutlple CAS servers with SSL's would be a bit too expensive.

Any help would be appreciated.
upictechAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

milindnCommented:
Error code translates into NOT FOUND. How long did you wait after creating the SRV record? I would wait for at least 24 hours to see the changes replicated across the DNS servers on internet.

http://support.microsoft.com/kb/940881

M
upictechAuthor Commented:
"In addition I am also able to query the DNS record of _autodiscover._tcp.domain.org from the system I am testing from and the correct record is returned."

However the record has been created for at least two weeks or more now.
RaghuvCommented:
Hi,

Remove the Internal A record which you created as "autodiscover.domain.org" and then test Autodiscover.

Let us know if it's still failing.

Cheers!
upictechAuthor Commented:
I am able to test externally and internally by simple means. The A record created inside of our local domain has nothing to do with the issue I am having. I also remember to clear the DNS cache between tests and I will ocassionally reboot to be double sure.

Any more suggestions are appreciated thank you.
upictechAuthor Commented:
I have finally received a solution to this issue. The value of 0x800C8206 means that too many redirection attempts were made; which is what Microsoft Support told me. In order to fix the issue you need to do one of two things. Once the registry changes were put in place the issue was immediately resolved.

1. Fix the website that is doing too many redirection (see olkdisc.log below).
2. Use on the client side registry settings to turn off redirection.

You can find the settings here:

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\AutoDiscover

The values that can be changed are as follows. 0 = enabled, 1 = disabled; the following settings is what I used to resolve the issue.

"PreferLocalXML"=dword:1
"ExcludeHttpRedirect"=dword:1
"ExcludeHttpsAutodiscoverDomain"=dword:1
"ExcludeHttpsRootDomain"=dword:1
"ExcludeScpLookup"=dword:0
"ExcludeSrvLookup"=dword:0
"ExcludeSrvRecord"=dword:0

From olkdisc.log:

2100      594941      04/10/09 06:42:50      Autodiscover to https://mydomain.org/autodiscover/autodiscover.xml starting
2100      595237      04/10/09 06:42:50      Autodiscover to https://mydomain.org/autodiscover/autodiscover.xml FAILED (0x800C8204)
2100      595237      04/10/09 06:42:50      Autodiscover URL redirection to https://mydomain.org/?fuseaction=home.404&target=404%3Bhttp%3A%2F%2Fmydomain%2Eorg%3A81%2Fautodiscover%2Fautodiscover%2Exml
2100      595237      04/10/09 06:42:50      Autodiscover to https://mydomain.org/?fuseaction=home.404&target=404%3Bhttp%3A%2F%2Fmydomain%2Eorg%3A81%2Fautodiscover%2Fautodiscover%2Exml starting
2100      595533      04/10/09 06:42:50      Autodiscover to https://www.mydomain.org/?&CFID=1446269&CFTOKEN=19517186 FAILED (0x800C8204)
2100      595533      04/10/09 06:42:50      Autodiscover URL redirection to https://www.mydomain.org/?&CFID=1446269&CFTOKEN=19517186
2100      595533      04/10/09 06:42:50      Autodiscover to https://www.mydomain.org/?&CFID=1446269&CFTOKEN=19517186 starting
2100      596017      04/10/09 06:42:51      Autodiscover to https://www.mydomain.org/?&CFID=1446270&CFTOKEN=29407692 FAILED (0x800C8204)
2100      596033      04/10/09 06:42:51      Autodiscover URL redirection to https://www.mydomain.org/?&CFID=1446270&CFTOKEN=29407692
2100      596033      04/10/09 06:42:51      Autodiscover to https://www.mydomain.org/?&CFID=1446270&CFTOKEN=29407692 starting
2100      596579      04/10/09 06:42:51      Autodiscover to https://www.mydomain.org/?&CFID=1446271&CFTOKEN=45578485 FAILED (0x800C8204)
2100      596579      04/10/09 06:42:51      Autodiscover URL redirection to https://www.mydomain.org/?&CFID=1446271&CFTOKEN=45578485
2100      596579      04/10/09 06:42:51      Autodiscover to https://www.mydomain.org/?&CFID=1446271&CFTOKEN=45578485 starting
2100      596969      04/10/09 06:42:52      Autodiscover to https://www.mydomain.org/?&CFID=1446272&CFTOKEN=27481597 FAILED (0x800C8204)
2100      596984      04/10/09 06:42:52      Autodiscover URL redirection to https://www.mydomain.org/?&CFID=1446272&CFTOKEN=27481597
2100      596984      04/10/09 06:42:52      Autodiscover to https://www.mydomain.org/?&CFID=1446272&CFTOKEN=27481597 starting
2100      597296      04/10/09 06:42:52      Autodiscover to https://www.mydomain.org/?&CFID=1420801&CFTOKEN=53904824 FAILED (0x800C8204)
2100      597296      04/10/09 06:42:52      Autodiscover URL redirection to https://www.mydomain.org/?&CFID=1420801&CFTOKEN=53904824
2100      597296      04/10/09 06:42:52      Autodiscover to https://www.mydomain.org/?&CFID=1420801&CFTOKEN=53904824 starting
2100      597671      04/10/09 06:42:52      Autodiscover to https://www.mydomain.org/?&CFID=1420802&CFTOKEN=21729650 FAILED (0x800C8204)
2100      597671      04/10/09 06:42:52      Autodiscover URL redirection to https://www.mydomain.org/?&CFID=1420802&CFTOKEN=21729650
2100      597671      04/10/09 06:42:52      Autodiscover to https://www.mydomain.org/?&CFID=1420802&CFTOKEN=21729650 starting
2100      598045      04/10/09 06:42:53      Autodiscover to https://www.mydomain.org/?&CFID=1446273&CFTOKEN=48245284 FAILED (0x800C8204)
2100      598045      04/10/09 06:42:53      Autodiscover URL redirection to https://www.mydomain.org/?&CFID=1446273&CFTOKEN=48245284
2100      598045      04/10/09 06:42:53      Autodiscover to https://www.mydomain.org/?&CFID=1446273&CFTOKEN=48245284 starting
2100      598341      04/10/09 06:42:53      Autodiscover to https://www.mydomain.org/?&CFID=1446275&CFTOKEN=83357035 FAILED (0x800C8204)
2100      598341      04/10/09 06:42:53      Autodiscover URL redirection to https://www.mydomain.org/?&CFID=1446275&CFTOKEN=83357035
2100      598341      04/10/09 06:42:53      Autodiscover to https://www.mydomain.org/?&CFID=1446275&CFTOKEN=83357035 starting
2100      598716      04/10/09 06:42:53      Autodiscover to https://www.mydomain.org/?&CFID=1446276&CFTOKEN=67400528 FAILED (0x800C8204)
2100      598716      04/10/09 06:42:53      Autodiscover URL redirection to https://www.mydomain.org/?&CFID=1446276&CFTOKEN=67400528
2100      598716      04/10/09 06:42:53      Autodiscover to https://www.mydomain.org/?&CFID=1446276&CFTOKEN=67400528 starting
2100      599090      04/10/09 06:42:54      Autodiscover to https://www.mydomain.org/?&CFID=1533433&CFTOKEN=55345368 FAILED (0x800C8204)
2100      599090      04/10/09 06:42:54      Autodiscover URL redirection to https://www.mydomain.org/?&CFID=1533433&CFTOKEN=55345368
2100      599106      04/10/09 06:42:54      Autodiscover to https://www.mydomain.org/?&CFID=1533433&CFTOKEN=55345368 starting
2100      599418      04/10/09 06:42:54      Autodiscover to https://www.mydomain.org/?&CFID=1533434&CFTOKEN=65412942 FAILED (0x800C8204)
2100      599418      04/10/09 06:42:54      Autodiscover to https://autodiscover.mydomain.org/autodiscover/autodiscover.xml starting
2100      599433      04/10/09 06:42:54      Autodiscover to https://autodiscover.mydomain.org/autodiscover/autodiscover.xml FAILED (0x800C8203)
2100      599433      04/10/09 06:42:54      Local autodiscover for mydomain.org starting
2100      599433      04/10/09 06:42:54      Local autodiscover for mydomain.org FAILED (0x8004010F)
2100      599433      04/10/09 06:42:54      Redirect check to http://autodiscover.mydomain.org/autodiscover/autodiscover.xml starting
2100      599433      04/10/09 06:42:54      Redirect check to http://autodiscover.mydomain.org/autodiscover/autodiscover.xml FAILED (0x80072EE7)
2100      599433      04/10/09 06:42:54      Srv Record lookup for mydomain.org starting
2100      599433      04/10/09 06:42:54      Srv Record lookup for mydomain.org FAILED (0x800C8206)

I hope this helps others. The primary issue is the fact that Microsoft thought it would be best to try out root domains (https://mydomain.org/Autodiscover/autodiscover.xml) which started the chain reaction of redirects. I've asked that they update this and put these types of checks after the SRV lookup because to met, at least; this makes more sense.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.