Machine software unabel to connect to new SQL server

[JaredBusch]

I have a client with a Fusion Arch CNC SawJet.

The client has recently upgraded from Server 2003 and SQL 2005 to Server 2012 R2 and SQL 2014.

Their LOB app connects to the new SQL database just fine.

This CNC machine does not.

This machine is running Windows XP

Just looking at the list of Ciphers, I have a feeling that this is the problem.

My Google is failing me, but I cannot find where to determine what SQL Server supports for encryption on log in.

[JaredBusch]

I realize that IIS Crypto is for IIS and not SQL Server. But I also knew it would provide a comprehensive list of what the OS supported.

[s.hackleman]

Similar environment here, you may try altering the sql servers compatibility mode. I have seen seen that work on older manufacturing automation systems as an easy fix.

[JaredBusch]

Jsut found this in the registry. It was set to 1 by default. I changed to to 0.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Client]
"DisabledByDefault"=dword:00000000

[JaredBusch]

Checking that key led me to this.

https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/operations/manage-ssl-protocols-in-ad-fs

[momurda]

@jaredbusch said in Machine software unabel to connect to new SQL server:

Jsut found this in the registry. It was set to 1 by default. I changed to to 0.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Client]
"DisabledByDefault"=dword:00000000

@jaredbusch This is the problem. That error is a handshake error means it cant negotiate.
XP supports ssl 3.0
SQL 2014 does as well, this shouldnt be a problem.
Have you checked how the odbc settings on xp is connecting to the sql server?

[JaredBusch]

@momurda said in Machine software unabel to connect to new SQL server:

@jaredbusch said in Machine software unabel to connect to new SQL server:

Jsut found this in the registry. It was set to 1 by default. I changed to to 0.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Client]
"DisabledByDefault"=dword:00000000

@jaredbusch This is the problem. That error is a handshake error means it cant negotiate.

I know it is a handshake problem.

Have you checked how the odbc settings on xp is connecting to the sql server?

It is a .Net connection string. not an OBDC DSN. This connot be checked as it is part of the executable.

[JaredBusch]

Just enabled SSL2.0 will see what that does. Nothing else was listed Disabled by defualt. but meh.

[momurda]

Do you have .net4 installed on this xp client?