The SSL connection request has failed

Hi,

I am getting an error from our Exchange Server 2007 on Windows 2008 once everyday and time seems to be random.

ID= 36874; Src= Schannel; User= ; Catg= ; D/T= 03/12/2015 02:06:38; EventDesc= An SSL connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The SSL connection request has failed.

No users are having any connection problems but I am not sure about why the server is constantly reporting the error message. A few users are using their mobile to connect to Exchange via SSL VPN, would this be the cause?
EducadAsked:
Who is Participating?

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

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

David Johnson, CD, MVPOwnerCommented:
SSL has been vulnerable to many exploits so it has been replaced by TLS some clients are trying SSL and getting rejected by the server but they are continuing down the security suites until they find one that both the client and server have
0
EducadAuthor Commented:
Does Exchange 2007 support TLS?
0
David Johnson, CD, MVPOwnerCommented:
yes exchange supports TLS indirectly since cypher suites are configured for the operating system.
0
kevinhsiehCommented:
Maybe someone is scanning your system, or a legitimate user is trying to connect and is having problems. If your system is publicly accessible I suggest running a report from SSL Labs to see what your configuration is. You can then adjust the settings on the server to make sure that the server is as secure as possible while still providing compatible connections to your clients.

Any change you make will require that you restart the server. :( If you have any other SSL/TLS severs, I suggest fixing those first so you have the cipher suite and TLS and SSL registry settings correct before you have to do a bunch of reboots on the Exchange server,

https://www.ssllabs.com/ssltest/
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
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
SSL / HTTPS

From novice to tech pro — start learning today.