Autodiscover Exchange 2013

I know this has been asked before and the advice given probably would have been OK 2 days ago but I am now mired down in this problem and I cannot accurately assess where I am at and where I should go.

The problem; autodiscover fails every test at https://testconnectivity.microsoft.com/¿ with a 404 Not Found error. I think I agree with it because I am not finding the xml files that it is probably looking for. The process works after you enter every detail of connecting to the server which makes autodiscover not very auto,

In addition my outlook clients are getting certificate errors on "connecting to proxies" on the exchange server as well as general certificate errors. The internal urls (\\exchangeserver\owa etc.) show yellow cert errors in chrome and I actually fixed these internal urls to point to the same as the externals so why they are even working I am not sure.

Externally https://mail.example.com/owa ... ecp etc are fine with nice little locks in the address bars.  

The SSL cert is a wild card and on top of that this is a 2012 essentials setup with onsite exchange and the split DNS/reverse proxy described here

Every time I find a resource/white paper/technet article I get sent off into group policies, cert servers, dns and AD. I have to stop and find out where I should start resolving issues i.e. which one would have the best chance of resolving the others.

Thanks for any assitance
mohrkAsked:
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.

Simon Butler (Sembee)ConsultantCommented:
Autodiscover works differently internally and externally.
Furthermore there are two web sites for Exchange 2013.
When you applied the SSL certificate, did you do it through IIS or through Exchange? It could be that you have applied it to the wrong web site and therefore it is listening with the wrong web site.

Check which web site is listening on port 443.

Simon.

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
mohrkAuthor Commented:
Simon,

Unfortunately in the midst of this I found the server hardware inadequate to run Exchange. A poorly done hardware upgrade resulted in the loss of the exchange installation. I believe I have the cert issue resolved in that I very closely followed a process that resulted in what appeared to be the correct and expected results.

Thank you for your time. If you want I am going to add another question regarding the virtual directories because, of course, nothing ever goes right for me.

Thanks
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.