outlook client error

We have a 2 microsoft servers, one running Windows Server 2008 Standard edition which is our Domain Controller, and one running Windows 2012 Standard Edition, and this runs Exchange 2010.

Our clients are running windows V7 Pro 64 bit and outlook 2007.

All seems to be working fine, apart from one client, who gets the following warning on starting outlook.


the fsascreenshotedit.png
the ssl referred to is not the one we use. ie it should read owamail.domainname.co.uk

It all seems to work OK if we select yes to proceed, but I would like to understand why this is happening, and what I can do to resolve it.

Any advice appreciated.

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.

Leroy LuffHead of IT & DIgitalCommented:
It might be a DNS issue where the client is connecting externally and not internally.

Does external clients connect with no issues using outlook Anywhere?
nigelbeatsonAuthor Commented:
I will have to check that as he does not usually use owa.

It's just odd that it is only this one client that has this problem.

the Ssl listed in the warning shows as autodiscover.domainname.co.uk and not the owamail.domainname.co.uk

Will SzymkowskiSenior Solution ArchitectCommented:
The certificate needs to have mail.domain.com and autodiscover.domain.com and your need to configure your Virtual directories with the same name for this cert error to not appear. If the cert DNS names do not match the virtual directories that is when you run into this issue.

Check my HowTo for configuring Split DNS and virtual directories correctly.


Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

nigelbeatsonAuthor Commented:
Ok I can confirm that when using owe the problem does NOT arise.

I will read through your suggested info thanks.

If it was a central issue, what I don't understand is why it only affects one user?

nigelbeatsonAuthor Commented:
Owe should read owa. Sorry!
nigelbeatsonAuthor Commented:
There are a couple of clients now displaying this behaviour, the remaining clients (around 25) remain unaffected and working OK.

Can anyone assist in explaining why we should just have a problem with the 2 clients??

If it was a DNS problem or an SSL certiffictae problem, I would have expected it to affect everyone??

Can anyone help?

Many thanks
Will SzymkowskiSenior Solution ArchitectCommented:
If it is affecting only 2 clients then it is likely a caching issue. Try re-creating a new Outlook profile and if that does not work then try re-creating a new Windows Profile.


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:
that was it! created a new outlook profile and that fixed it!

many thanks to all
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.