Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Autodiscover fails for Outlook 2007 only

Posted on 2013-11-01
8
Medium Priority
?
1,411 Views
Last Modified: 2013-11-12
Hello Everyone,

For some reason, auto discover is failing for outlook 2007 only. Auto-discover works fine for the users with outlook 2010 and 2013. We have combed through every possible setting that could be affecting this. The auto discover and mail DNS records are point to the correct server. We have gone through IIS, and verified correct links. We have rebuilt the EWS directory. When running the outlook Email test auto configuration, it fails every attempt to pull in auto discover settings. If you need additional information, just let us know and we will be happy to post.

Thank you,
0
Comment
Question by:IntegratedBizTech
[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
  • 2
8 Comments
 
LVL 23

Expert Comment

by:Patrick Bogers
ID: 39617723
What exchange server are you running and what events are displayed in the clients computers events?
0
 

Author Comment

by:IntegratedBizTech
ID: 39617991
It's exchange server 2010, there are no error messages in the event log, prior, during, or after running outlook. The error message returned by the test email autoconfiguration are as follow.
"attempting URL https://mail.company.com/autodiscover/autodiscover.xml found through SCP
Autodiscover to https://mail.company.com/autodiscover/autodiscover.xml starting
getlasterror=o; httpstatus=200.
Autodiscover to https://mail.company.com/autodiscover/autodiscover.xml FAILED (0x800c8202)
Autodiscover to https://mail.company.com/autodiscover/autodiscover.xml starting
getlasterror=12030; httpstatus=200.
Autodiscover to https://company.com/autodiscover/autodiscover.xml FAILED (0x800c8203)
Autodiscover to https://autodiscover.company.com/autodiscover/autodiscover.xml starting
getlasterror=12175; httpstatus=o.
getlasterror=0; httpstatus=401
getlasterror=0; httpstatus=401
getlasterror=0; httpstatus=200.
Autodiscover to https://autodiscover.company.com/autodiscover/autodiscover.xml FAILED (0x800c8202)
Redirect check to http://autodiscover.company.com/autodiscover/autodiscover.xml starting
Redirect check to http://autodiscover.company.com/autodiscover/autodiscover.xml FAILED (0x80004005)
Srv Record lookup for company.com starting
Autodiscover URL redirection to https://mail.company.com/autodiscover/autodiscover.xml
Autodiscover to https://mail.company.com/autodiscover/autodiscover.xmll starting
getlaterror=0; httpstatus=200.
autodiscover to https://mail.company.com/autodiscover/autodiscover.xml FAILED (0x800c8202)
Srv record lookup for company.com FAILED (0x800c8202)"

A few additonal notes.  We discovered that autodiscover not work for outlook 2010 as well, but you can still access the out of office assitant and offline address book. All of which you shouldn't be able to if autodiscover is not working correctly, but Offline address book and out of office will not work in outlook 2007. The autodiscover for outlook 2010 was working a week ago. The error message for outlook 2010 is the same as the one posted above.
0
 
LVL 23

Expert Comment

by:Patrick Bogers
ID: 39618497
Hmm what about the certificate? is it still valid for the internal URL?
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39618601
Does the host name in the error message resolve to the INTERNAL IP address of the server?
If so, is the SSL certificate still valid?

Does OWA etc work?
Another option would be to recreate the Autodiscover virtual directory, using the wizard in EMC.

Simon.
0
 

Author Comment

by:IntegratedBizTech
ID: 39618983
The host can resolve over the internal IP address of the server. All the mail settings pull in because the computer are joined to the domain, so it is resolving over internally. The SSL certificate is still valid. We have one Certificate for this domain.This is the Certificate we have is attached to this post. The certificate is for the mail.company.com but we have a cname record in DNS for autodiscover.company.com to point over to the mail.company.com. All versions of outlook do get an SSL certificate error. It states
"autodiscover.company.com

Information you exchange  with this site cannot be viewed or viewed or changed by others. However, there is a problem with this site's certificate.

The security certificate is from a trusted certifying Authority (Check)
The security certificate date is valid (check)
The name on the security certificate is invalid or does not match the name of the site (failed
"
When viewing the record, it brings up the same information for the cert as it does from the EMC.

We have already tried recreating the Autodiscover Virtual Directory with no success. OWA also works fine with no issue, internally or externally.
certificate.txt
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39619009
"This is the Certificate we have is attached to this post. The certificate is for the mail.company.com but we have a cname record in DNS for autodiscover.company.com to point over to the mail.company.com"

There is your problem.
You cannot do Autodiscover like that.
The client is trying to use Autodiscover.example.com, which resolves, but isn't on the DNS record.

You need to do one of two things.
1. Remove the CNAME and replace it with an SRV record, both internally and externally.
2. Add Autodiscover.example.com to the SSL certificate. That will probably mean a different kind of certificate being purchased.

Simon.
0
 

Accepted Solution

by:
IntegratedBizTech earned 0 total points
ID: 39627377
We have resolved the problem. We had to remove client access and re-install client access and rebuild the virtual directory's in IIS, After doing that, Auto-discover worked both internally and externally. Did not have to purchase a new certificate. Thank you all for your help.
0
 

Author Closing Comment

by:IntegratedBizTech
ID: 39641084
We figured out the solution without any intervention.
0

Featured Post

Enroll in October's Free Course of the Month

Do you work with and analyze data? Enroll in October's Course of the Month for 7+ hours of SQL training, allowing you to quickly and efficiently store or retrieve data. It's free for Premium Members, Team Accounts, and Qualified Experts!

Question has a verified solution.

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

I don't pretend to be an expert at this, but I have found a few things that are useful. I hope that sharing them here will help others, so they will not have to face some rather hard choices. Since I felt this to be a topic of enough importance and…
If something goes wrong with Exchange, your IT resources are in trouble.All Exchange server migration processes are not designed to be identical and though migrating email from on-premises Exchange mailbox to Cloud’s Office 365 is relatively simple…
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…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.
Suggested Courses

604 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