Sign up ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I am getting this error in my server's windows event log:

An TLS 1.0 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.

When I try to connect to a web service on a windows 7 box from a windows server 2003 box.

How do I add a cipher suite to one that the other supports?

(fixing clients is ideal, but failing that a server solution is fine - I have access to all boxes involved, I just want some basic encryption between them for privacy).

Along with hours of googling and reading, I have tried:

  • Checked server windows event viewer (found cipher suite error)
  • Added cipher suites to test1 from (didn't help)
  • Added TLS 1.0 to protocols in cipher suites in the server's windows registry (no change)
  • Install IIS tools hoping that adds more protocols to Schannel (it doesn't)
  • Export certificate for clients, again, but with private key included (no change)
  • Check that installed cipher suites match on server and client (can't find where win2k3 lists them)
  • Add TLS_RSA_WITH_AES_256_CBC_SHA (installed by above hotfix) to server's cipher suites (nope, already on there)
share|improve this question

2 Answers 2

Windows 7 uses the new CNG (Cryptography Next Generation) API when choosing ciphers. CNG for Windows 2003 is not available as far as I know.

You can however, install these AES based cipher suites for use on Windows 2003:


These are the first suites Windows Vista and Windows 7 clients will try to negotiate for use with TLS 1.0 and above, and are also supported by OpenSSL clients.

In order to use these, install KB948963

share|improve this answer
Thanks! I should have mentioned that I already tried that - it didn't solve the problem for me. Maybe the other box still rejects them because CBC is no longer considered safe? They are in it's cipher suites list, though, so what else can I do? :( – MGOwen Jun 17 '13 at 13:37
up vote 0 down vote accepted

The solution was to generate my certificate again, this time forcing RSA and SHA1 (though SHA1 should be the default anyway). For some reason Win Server 2k3 couldn't or wouldn't use the right ciphers with a default makecert certificate. Here is the command line that worked for me:

makecert -pe -r -ss my -sr localMachine -n "" -e 01/01/2098 -a sha1 -eku -sky exchange -sp "Microsoft RSA SChannel Cryptographic Provider" -sy 12

For details see and .

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.