The TLS protocol defined fatal alert code is 70 (SOLUS).

[Koldov]

I posted a thread in the Server 2012 forum about this, but received no replies (not surprising as it covers a vast array of things that could be wrong)...

 

So I installed Wireshark on the server to capture packets (as the error was happening every 6 seconds it didn't take long) and narrowed it down to the following...

 

 

I opened SOLUS and noticed a stuck download (no idea why, could be something to do with the change in URL but I sorted that last month so I can't see any reason for it to suddenly kick off last night), anyway I cancelled it and the errors stopped immediately.

 

So, now the question is why was SOLUS even attempting to negotiate with the TLS v1 protocol (or does it always try this first), on the other hand is there something configured incorrectly on my server?

 

Made even more strange as I increased logging and the next 2 events said:

 

An SSL client handshake completed successfully. The negotiated cryptographic parameters are as follows.

 

Protocol: TLS 1.2

CipherSuite: 0xC028

Exchange strength: 256

 

An SSL server handshake completed successfully. The negotiated cryptographic parameters are as follows.

 

Protocol: TLS 1.2

CipherSuite: 0xC028

Exchange strength: 256

 

But it still seemed to fail and just repeat every 6 seconds....

 

I am going to set a download for tonight and see if it completes or fails and I come in to a full event log again!

[BOOT]

Server 2012 has limited support for modern CipherSuites, so those errors are expected. Consider upgrading.