Trouble with Exchange 2007 Autodiscover

Our 3rd party spam filter is not working correctly due to an error with Autodiscover. It seems to be an issue with our certificate. We have a self signed certificate and I think it has all the correct local and remote domains names. Here is the error I get when running Test-OutlookWebServices:
1005       Error When accessing https://remote.mydomainame.com/autodiscover/autodis
                 cover.xml the error "RemoteCertificateNameMismatch:CN=remote.mydomainname.com, O=My Company Inc, DC=mycompany, DC=com" was report
                 ed.

Why is it giving me a name mismatch ?
WiddleAviAsked:
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.

Gareth GudgerCommented:
Have you seen this forum thread? Lots of great links on it too.
http://social.technet.microsoft.com/Forums/exchange/en-US/2404ddf4-ffd7-45ac-bf2c-a0d639ca17e5/how-do-i-change-the-autodiscover-address

I would always recommend going for the 3rd party certificate. It will save you a lot of trouble in the long run.
http://supertekboy.com/certificates-for-microsoft-exchange/
0

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
WiddleAviAuthor Commented:
I will try info in that link in the morning. Unfortunately the customer right now does not want to spend on a 3rd party certificate.
0
Simon Butler (Sembee)ConsultantCommented:
You can get a trusted SSL certificate for less than $80/year.
The self signed certificates are not supported for use with ActiveSync or Outlook Anywhere. If the customer has spent the money on Exchange server, CALs, Windows licences and hardware, not spending the money on an SSL certificate seems petty. I don't know how much your time is worth, but I tell my clients the maths is quite simple - every time you want to add a client, it will take 10-15 minutes to get it setup, plus the same again each time the self signed certificate is replaced. Or you can get a trusted certificate which is a lot less than one hour of my time and not have to worry about it.

Self-Signed certificates are simply not worth the hassle.

Simon.
0
WiddleAviAuthor Commented:
Thanks for pointing me in the right direction. In the end the problem was I was using the remote.ourdomain.com in the CN but did not include it together with the list of alternate domain names. I created a new cert had remote.outdomain.com as the CN and again in the list of alternate domain names.
0
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.