Y
Yuh-Rong Leu
My customer wants us to disable TLS 1.0 on its NPS/SQL server. The NPS server is configured to use SQL Logging.
I run "netsh nps dump yes > c:\nps.txt" to dump the NPS settings, and I can see set sqllog connection = "Provider=SQLOLEDB.1;Password=sapasswd;Persist Security Info=True;User ID=sa;Initial Catalog=WinocDB;Data Source=.;Connect Timeout=30"
It means SQLOLEDB is used as the provider. However, SQLOLEDB does not support TLS 1.2, so I try to run netsh nps set sqllog connection = "Provider=MSOLEDBSQL;Server=.;Database=WinocDB;User ID=sa;Password=sapasswd" to change the provider to MSOLEDBSQL, which supports TLS 1.2.
NPS can connect to the SQL server as it passes the SQL connection test on the NPS MMC console.
However, SQL Logging does not work with this connection string. There is an NPS Event ID 4404 error stating that SQL Logging failed with error code 0x80040e5d ("Parameter name is unrecognized").
A stored procedure named "report_event (@doc ntext)" exists in the WinocDB database.
I believe the OLE DB client of NPS is not compatible with the new MSOLEDBSQL driver, and needs to be updated so that TLS 1.2 can be supported.
Is any workaround possible?
Continue reading...
I run "netsh nps dump yes > c:\nps.txt" to dump the NPS settings, and I can see set sqllog connection = "Provider=SQLOLEDB.1;Password=sapasswd;Persist Security Info=True;User ID=sa;Initial Catalog=WinocDB;Data Source=.;Connect Timeout=30"
It means SQLOLEDB is used as the provider. However, SQLOLEDB does not support TLS 1.2, so I try to run netsh nps set sqllog connection = "Provider=MSOLEDBSQL;Server=.;Database=WinocDB;User ID=sa;Password=sapasswd" to change the provider to MSOLEDBSQL, which supports TLS 1.2.
NPS can connect to the SQL server as it passes the SQL connection test on the NPS MMC console.
However, SQL Logging does not work with this connection string. There is an NPS Event ID 4404 error stating that SQL Logging failed with error code 0x80040e5d ("Parameter name is unrecognized").
A stored procedure named "report_event (@doc ntext)" exists in the WinocDB database.
I believe the OLE DB client of NPS is not compatible with the new MSOLEDBSQL driver, and needs to be updated so that TLS 1.2 can be supported.
Is any workaround possible?
Continue reading...