Solved

MS Exchange 2007 Autodisover fails 401 unauthorized

Posted on 2010-11-22
6
1,609 Views
Last Modified: 2012-06-27
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	8364173070828	Recipient policies:
Info	2716	10	2010-11-08T09:58:26	8364173071167	Message direction is: Inbound
Info	2716	10	2010-11-08T09:58:26	8364173072028	Starting retrieval of user objects for each mail recipient.
Info	2716	10	2010-11-08T09:58:26	8364173156681	[ExchangeWebServicesProvider::GetRecipientMailstoreInfo] About to get the EWS URI and root folder for dtraylor@domain.com...
Info	2716	10	2010-11-08T09:58:26	8364173157263	[ExchangeWebServicesHelper::GetEwsUriForMailbox] About to perform autodiscovery for dtraylor@domain.com...
Info	2716	10	2010-11-08T09:58:26	8364173157583	[Autodiscovery] ?? Starting SCP lookup for domainName='domain.com', root path=''
Info	2716	10	2010-11-08T09:58:26	8364173194786	[Autodiscovery] ?? Searching for SCP entries in LDAP://CN=Configuration,DC=lslbc,DC=local
Info	2716	10	2010-11-08T09:58:26	8364173223243	[Autodiscovery] -? Scanning for SCP pointers, Domain=domain.com
Info	2716	10	2010-11-08T09:58:26	8364173235108	[Autodiscovery] -- No SCP pointers found for Domain=domain.com in configPath='CN=Configuration,DC=lslbc,DC=local'
Info	2716	10	2010-11-08T09:58:26	8364173301032	[Autodiscovery] -? Scanning for SCP urls for the current computer Site=Default-First-Site-Name
Info	2716	10	2010-11-08T09:58:26	8364173306125	[Autodiscovery] +=  adding (prio 1) 'https://server3.domain.com/autodiscover/autodiscover.xml' for the Site=Default-First-Site-Name from 'LDAP://CN=SERVER3,CN=Autodiscover,CN=Protocols,CN=SERVER3,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=LSLBC,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=lslbc,DC=local' to the top of the list (exact match)
Info	2716	10	2010-11-08T09:58:26	8364173309356	[Autodiscovery] =? Trying 'dtraylor@domain.com' at 'https://server3.domain.com/autodiscover/autodiscover.xml'
Info	2716	10	2010-11-08T09:58:26	8364174488267	[Autodiscovery] !! Error: System.Net.WebException: The remote server returned an error: (401) Unauthorized.     at System.Net.HttpWebRequest.GetResponse()     at Ninja.Core.MailDirectoryServices.ExchangeWebServicesAccess.Autodiscover.DiscoverTryUrl(String emailAddress, NetworkCredential nc, String url, Boolean authoritative, Boolean allowSelfSignedCerts)
Info	2716	10	2010-11-08T09:58:26	8364174489171	[Autodiscovery] -- No response returned from SCP URLs, trying default URLs:
Info	2716	10	2010-11-08T09:58:26	8364174489438	[Autodiscovery] +=  'https://domain.com/autodiscover/autodiscover.xml'
Info	2716	10	2010-11-08T09:58:26	8364174489637	[Autodiscovery] +=  'https://autodiscover.domain.com/autodiscover/autodiscover.xml'
Info	2716	10	2010-11-08T09:58:26	8364174489861	[Autodiscovery] =? Trying 'dtraylor@domain.com' at 'https://domain.com/autodiscover/autodiscover.xml'
Info	2716	10	2010-11-08T09:58:26	8364174504339	[Autodiscovery] -! Info: System.Net.WebException: The remote name could not be resolved: 'domain.com'     at System.Net.HttpWebRequest.GetRequestStream()     at Ninja.Core.MailDirectoryServices.ExchangeWebServicesAccess.Autodiscover.DiscoverTryUrl(String emailAddress, NetworkCredential nc, String url, Boolean authoritative, Boolean allowSelfSignedCerts)
Info	2716	10	2010-11-08T09:58:26	8364174504968	[Autodiscovery] =? Trying 'dtraylor@domain.com' at 'https://autodiscover.domain.com/autodiscover/autodiscover.xml'
Info	2716	10	2010-11-08T09:58:26	8364174516937	[Autodiscovery] -! Info: System.Net.WebException: The remote name could not be resolved: 'autodiscover.domain.com'     at System.Net.HttpWebRequest.GetRequestStream()     at Ninja.Core.MailDirectoryServices.ExchangeWebServicesAccess.Autodiscover.DiscoverTryUrl(String emailAddress, NetworkCredential nc, String url, Boolean authoritative, Boolean allowSelfSignedCerts)
Info	2716	10	2010-11-08T09:58:26	8364174517602	[Autodiscovery] ?? Trying GET redirect URL on non-SSL URL 'http://autodiscover.domain.com/autodiscover/autodiscover.xml'
Info	2716	10	2010-11-08T09:58:26	8364174528988	[Autodiscovery] !! Exception: System.Net.WebException: The remote name could not be resolved: 'autodiscover.domain.com'     at System.Net.HttpWebRequest.GetResponse()     at Ninja.Core.MailDirectoryServices.ExchangeWebServicesAccess.Autodiscover.GetRedirectUrl(String domainName)
Info	2716	10	2010-11-08T09:58:26	8364174529537	[ExchangeWebServicesHelper::GetEwsUriForMailbox] Completed autodiscovery in 2 hops.
Info	2716	10	2010-11-08T09:58:26	8364174529846	[ExchangeWebServicesHelper::GetEwsUriForMailbox] Autodiscover did not return a response.
Info	2716	10	2010-11-08T09:58:26	8364174530110	Finished retrieval of user objects for each mail recipient.


0
Comment
Question by:mdj8384
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
6 Comments
 
LVL 34

Accepted Solution

by:
Shreedhar Ette earned 500 total points
ID: 34187798
Hi,

Refer this previously answered question:
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_24650721.html

Hope this helps,
Shree
0
 
LVL 1

Author Comment

by:mdj8384
ID: 34191202
Thank you.

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.
0
 
LVL 1

Author Comment

by:mdj8384
ID: 34191738
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
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 34

Expert Comment

by:Shreedhar Ette
ID: 34195649
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.
0
 
LVL 1

Author Comment

by:mdj8384
ID: 34195861
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?

0
 
LVL 1

Author Comment

by:mdj8384
ID: 34199713
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.com 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.

0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Read this checklist to learn more about the 15 things you should never include in an email signature.
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

724 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question