outlook 2016 wont connect to exchange 2016

we have just re built or exchange 2016 server which is running on Windows 2016 server standard in a VM.

We have configured our internal and external url's and configured all of our users etc.

I can access the mailboxes using owa internally and externally, but when we try to connect using outlook 2016, we get part way through the setup and we are asked for the user name and password. nothing we enter here seems to work. I have tried the automatic and manual connections but we just cant get outlook to connect locally.

Can anyone help in trying to resolve this extremely frustrating problem?

Many thanks.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Please use the Exchange Troubleshooting Assistant and then post any error in the results :

MAS (MVE)EE Solution Guide - Technical Dept HeadCommented:
HI nigelbeatson,
Did you try after restating the server?
Did you configure mapi virtual directory?
Please check this article and configure MAPI Virtual directories.
Scott CSenior EngineerCommented:
Try the Connectivity Analyzer...https://testconnectivity.microsoft.com/

Test for Outlook connectivity and Autodiscover.  See what that says.

Is it safe to assume that this was working before the Exchange rebuild?
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Todd NelsonSystems EngineerCommented:
Review this reference...

You may need to restart the autodiscover app pool...

Restart-WebAppPool MSExchangeAutodiscoverAppPool

Open in new window

nigelbeatsonAuthor Commented:
many thanks to all, as I have now resolved the issue.

It was a strange permissions issue, where the user in question did not have the correct inheritance permissions set.

Thanks to all who tried to help.

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
nigelbeatsonAuthor Commented:
many thanks
Scott CSenior EngineerCommented:
solved own issue
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

From novice to tech pro — start learning today.