Outlook 2013 have certificate warning with sbs2011 (Exchange 2010). Selfsigned cert is used. Only domain-members have the problem

Hi,

we have a sbs2011 with Exchange 2010. As domain we have via wizard in the console used remote.realdomainname.com . If i ping remote.realdomainname.com it ping sthe ip of the local server. In DNS there is the right Entry i think. On top we entered the line "192.168.10.2 remote.realdomainname.com" in the hosts file.
We have some workstations which are members of the network-domain and some workstations are only in a workgroup.
Only the workstations which are domainmembers, throw a warning at the start of Outlook. Outlooks says that the certificate realdomainname.com is not valid.
Outlook tries to go out on the webserver a looks at this ssl-certificate instead of looking directly over lan to the exchange-server.
I tried to use proxy-settings in outlook without any success.

Any ideas ?

loosain
loosainAsked:
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.

MIRSYSCommented:
Well it's probably because you didn't create an A record for "autodiscover.yourrealdomain.com" in the internal DNS.
Also don't use hostfile entries. If your DNS is functioning well you wouldn't need it.
However I'm not clear on how you wouldn't get a certificate warning on all clients given you're not using a trusted cert.
0
loosainAuthor Commented:
The cert on the server is trusted. But the non-domain-members talk directly with the server and trust his cert. The domain-members go via internet and use the ssl-cert of the webserver. I don´t know the reason. Therefor i added the hosts entries for testing. ITs much faster and easier than testing by configuring dns-server...
0
MIRSYSCommented:
like I said it's probably because they are doing a lookup to autodiscover.
What does the certificate warning say exactly?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

loosainAuthor Commented:
It says that the certificate is not valid because of wrong domainname and validation time is over.
That´s because it is the ssl-certificate of the webserver not of the local exchange server. There is no ssl in use on webserver so there is an old provider-cert there.
I dont get the point why those computers which are domain-members look at the internet and the non-domain-members look directly to the exchange server.
If it would be a dns problem, it should have been fixed by adding remote.domain.com and autodiscover.domain.com to the hosts file.
0
MIRSYSCommented:
what happens when you manually configure outlook and enter the hostname of the server?
Or are you trying to use outlook anywhere?
0
loosainAuthor Commented:
Just tested - same warning by manually configuring it.
Normaly outlook finds out by itself name, server etc if the computer is domain-member. Now i just tried to enter those data manually. It worked and outlook connected but there was again this certification warning belonging to the certificate of the internet-webserver.
0
loosainAuthor Commented:
It must have been something with active directory, because only domain-members are trying to connect over internet. The other computers cant connect to AD and then they just talk via lan to the exchange server (as i want them to)
0
loosainAuthor Commented:
Found out something new:
If i start "Email Autoconfiguration" in Outlook it always shows the wrong url for inernal and external Url:
yourrealdomain.com instead of remote.yourrealdomain.com

So i (just for testing) add server-ip with yourrealdomain.com in hosts...
No warning, no error ! But now i cant surf to the website yourrealdomain.com, because it is placed on the webserver and not on the Exchange-server...
What can i do to change the information about internal urls provided to the clients via autoconfiguration ?
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
loosainAuthor Commented:
The clue was to make a working SSL-cert for the webserver. In DNS we let show autodiscover.domain.tld to the wrong IP. Then Outlook tries remote.domain.tld .This is hosted by the Exchange-Server and therefor there is the right cert there. Now everything works
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
Outlook

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.