mdj8384
asked on
MS Exchange 2007 Autodisover fails 401 unauthorized
Environment: Exchange 2007, WinServer 2008, Sunbelt Vipre Email
Like many other posts... I get an unsuccessful autodiscover with error 1016 followed by error 1006. (see below)
I also get a 401 error in the Vipre logs.(see below)
I have applied K281308 and Method1 in KB896891 as mentioned in other posts, but I still get the error.
All other Autodiscover services seem to be working. OWA works, The CTL-shift on the Outlook icon autodiscovery test works, my iphone works. Setting up 2007,2010 mailboxes works.
I just can't get this part of autodiscovery to work. Vipre won't assist with my SPAM issues until the "get-outlookwebservices|fl " is clean.
EXCHANGE
GET-OUTLOOKWEBSERVICES | FL
Id : 1003
Type : Information
Message : About to test AutoDiscover with the e-mail address brc@domain.com.
Id : 1007
Type : Information
Message : Testing server server3.domain.local with the published name https://server3.domain.com/ews/exchange.asmx & .
Id : 1019
Type : Information
Message : Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://server3.domain.com/autodiscover/autodiscover.xml.
Id : 1013
Type : Error
Message : When contacting https://server3.domain.com/autodiscover/autodiscover.xml received the error The remote server returned an error: (401) Unauthorized.
Id : 1006
Type : Error
Message : The Autodiscover service could not be contacted.
SUNBELT VIPRE LOG PORTION FOLLOWS:
Info	2716	10	2010 -11-08T09: 58:26	8 3641730708 28	Reci pient policies:
Info	2716	10	2010 -11-08T09: 58:26	8 3641730711 67	Mess age direction is: Inbound
Info	2716	10	2010 -11-08T09: 58:26	8 3641730720 28	Star ting retrieval of user objects for each mail recipient.
Info	2716	10	2010 -11-08T09: 58:26	8 3641731566 81	[Exc hangeWebSe rvicesProv ider::GetR ecipientMa ilstoreInf o] About to get the EWS URI and root folder for dtraylor@domain.com...
Info	2716	10	2010 -11-08T09: 58:26	8 3641731572 63	[Exc hangeWebSe rvicesHelp er::GetEws UriForMail box] About to perform autodiscovery for dtraylor@domain.com...
Info	2716	10	2010 -11-08T09: 58:26	8 3641731575 83	[Aut odiscovery ] ?? Starting SCP lookup for domainName='domain.com', root path=''
Info	2716	10	2010 -11-08T09: 58:26	8 3641731947 86	[Aut odiscovery ] ?? Searching for SCP entries in LDAP://CN=Configuration,DC =lslbc,DC= local
Info	2716	10	2010 -11-08T09: 58:26	8 3641732232 43	[Aut odiscovery ] -? Scanning for SCP pointers, Domain=domain.com
Info	2716	10	2010 -11-08T09: 58:26	8 3641732351 08	[Aut odiscovery ] -- No SCP pointers found for Domain=domain.com in configPath='CN=Configurati on,DC=lslb c,DC=local '
Info	2716	10	2010 -11-08T09: 58:26	8 3641733010 32	[Aut odiscovery ] -? Scanning for SCP urls for the current computer Site=Default-First-Site-Na me
Info	2716	10	2010 -11-08T09: 58:26	8 3641733061 25	[Aut odiscovery ] += adding (prio 1) 'https://server3.domain.com/autodiscover/autodiscover.xml' for the Site=Default-First-Site-Na me from 'LDAP://CN=SERVER3,CN=Auto discover,C N=Protocol s,CN=SERVE R3,CN=Serv ers,CN=Exc hange Administrative Group (FYDIBOHF23SPDLT),CN=Admin istrative Groups,CN=LSLBC,CN=Microso ft Exchange,CN=Services,CN=Co nfiguratio n,DC=lslbc ,DC=local' to the top of the list (exact match)
Info	2716	10	2010 -11-08T09: 58:26	8 3641733093 56	[Aut odiscovery ] =? Trying 'dtraylor@domain.com' at 'https://server3.domain.com/autodiscover/autodiscover.xml'
Info	2716	10	2010 -11-08T09: 58:26	8 3641744882 67	[Aut odiscovery ] !! Error: System.Net.WebException: The remote server returned an error: (401) Unauthorized. at System.Net.HttpWebRequest. GetRespons e() at Ninja.Core.MailDirectorySe rvices.Exc hangeWebSe rvicesAcce ss.Autodis cover.Disc overTryUrl (String emailAddress, NetworkCredential nc, String url, Boolean authoritative, Boolean allowSelfSignedCerts)
Info	2716	10	2010 -11-08T09: 58:26	8 3641744891 71	[Aut odiscovery ] -- No response returned from SCP URLs, trying default URLs:
Info	2716	10	2010 -11-08T09: 58:26	8 3641744894 38	[Aut odiscovery ] += 'https://domain.com/autodiscover/autodiscover.xml'
Info	2716	10	2010 -11-08T09: 58:26	8 3641744896 37	[Aut odiscovery ] += 'https://autodiscover.domain.com/autodiscover/autodiscover.xml'
Info	2716	10	2010 -11-08T09: 58:26	8 3641744898 61	[Aut odiscovery ] =? Trying 'dtraylor@domain.com' at 'https://domain.com/autodiscover/autodiscover.xml'
Info	2716	10	2010 -11-08T09: 58:26	8 3641745043 39	[Aut odiscovery ] -! Info: System.Net.WebException: The remote name could not be resolved: 'domain.com' at System.Net.HttpWebRequest. GetRequest Stream() at Ninja.Core.MailDirectorySe rvices.Exc hangeWebSe rvicesAcce ss.Autodis cover.Disc overTryUrl (String emailAddress, NetworkCredential nc, String url, Boolean authoritative, Boolean allowSelfSignedCerts)
Info	2716	10	2010 -11-08T09: 58:26	8 3641745049 68	[Aut odiscovery ] =? Trying 'dtraylor@domain.com' at 'https://autodiscover.domain.com/autodiscover/autodiscover.xml'
Info	2716	10	2010 -11-08T09: 58:26	8 3641745169 37	[Aut odiscovery ] -! Info: System.Net.WebException: The remote name could not be resolved: 'autodiscover.domain.com' at System.Net.HttpWebRequest. GetRequest Stream() at Ninja.Core.MailDirectorySe rvices.Exc hangeWebSe rvicesAcce ss.Autodis cover.Disc overTryUrl (String emailAddress, NetworkCredential nc, String url, Boolean authoritative, Boolean allowSelfSignedCerts)
Info	2716	10	2010 -11-08T09: 58:26	8 3641745176 02	[Aut odiscovery ] ?? Trying GET redirect URL on non-SSL URL 'http://autodiscover.domain.com/autodiscover/autodiscover.xml'
Info	2716	10	2010 -11-08T09: 58:26	8 3641745289 88	[Aut odiscovery ] !! Exception: System.Net.WebException: The remote name could not be resolved: 'autodiscover.domain.com' at System.Net.HttpWebRequest. GetRespons e() at Ninja.Core.MailDirectorySe rvices.Exc hangeWebSe rvicesAcce ss.Autodis cover.GetR edirectUrl (String domainName)
Info	2716	10	2010 -11-08T09: 58:26	8 3641745295 37	[Exc hangeWebSe rvicesHelp er::GetEws UriForMail box] Completed autodiscovery in 2 hops.
Info	2716	10	2010 -11-08T09: 58:26	8 3641745298 46	[Exc hangeWebSe rvicesHelp er::GetEws UriForMail box] Autodiscover did not return a response.
Info	2716	10	2010 -11-08T09: 58:26	8 3641745301 10	Fini shed retrieval of user objects for each mail recipient.
Like many other posts... I get an unsuccessful autodiscover with error 1016 followed by error 1006. (see below)
I also get a 401 error in the Vipre logs.(see below)
I have applied K281308 and Method1 in KB896891 as mentioned in other posts, but I still get the error.
All other Autodiscover services seem to be working. OWA works, The CTL-shift on the Outlook icon autodiscovery test works, my iphone works. Setting up 2007,2010 mailboxes works.
I just can't get this part of autodiscovery to work. Vipre won't assist with my SPAM issues until the "get-outlookwebservices|fl
EXCHANGE
GET-OUTLOOKWEBSERVICES | FL
Id : 1003
Type : Information
Message : About to test AutoDiscover with the e-mail address brc@domain.com.
Id : 1007
Type : Information
Message : Testing server server3.domain.local with the published name https://server3.domain.com/ews/exchange.asmx & .
Id : 1019
Type : Information
Message : Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://server3.domain.com/autodiscover/autodiscover.xml.
Id : 1013
Type : Error
Message : When contacting https://server3.domain.com/autodiscover/autodiscover.xml received the error The remote server returned an error: (401) Unauthorized.
Id : 1006
Type : Error
Message : The Autodiscover service could not be contacted.
SUNBELT VIPRE LOG PORTION FOLLOWS:
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
Info	2716	10	2010
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I backed out the changes made with Method One of KB 896861 and installed changes for Method Two which Disables Loopback Checking.
The results are attached.
It looks like Autodiscover passed.
However, at the bottom of the attachment.... the domain listed has a typo and seen in the typodomain.com 1013 and 1017 error entries. Where do I go to fix that domain name typo?
outlookwebservices-for-expert-ex.txt
The results are attached.
It looks like Autodiscover passed.
However, at the bottom of the attachment.... the domain listed has a typo and seen in the typodomain.com 1013 and 1017 error entries. Where do I go to fix that domain name typo?
outlookwebservices-for-expert-ex.txt
Do the RPC Virtual directories exist under Default Web Site of IIS? If not then that means the RPC over HTTP component is not installed.
ASKER
shreedhar,
Thank you for your help.
I will check on the RPC virtual directories.
Do you think I should open an new record for the new problem in this thread since the Autodiscover is working?
Thank you for your help.
I will check on the RPC virtual directories.
Do you think I should open an new record for the new problem in this thread since the Autodiscover is working?
ASKER
This will be my last entry on this thread.
I found where the typodomain is specified (mentioned in above thread ID: 34191738)
The results from the "get-outlookanywhere | fl" showed the external URL was spelled incorrectly.
Also, on the support.sunbeltsoftware.co m website has some info about a mismatch certificate between internal and external URLs when searching on Autodiscovery. This may be my ultimate resolution, however, the registry hack for disableloopbacks fixed the Autodiscovery for now and Vipre is working correctly.
Thanks for the responses.
I found where the typodomain is specified (mentioned in above thread ID: 34191738)
The results from the "get-outlookanywhere | fl" showed the external URL was spelled incorrectly.
Also, on the support.sunbeltsoftware.co
Thanks for the responses.
ASKER
Like NCES in that post, I ran Method One as a possible solution In the Microsoft KB 896861, but still have the error. I guess I will have to resort to Method Two although I'm a little concerned with the exposure.
I will make the changes and report back.
Thanks again.