从 Windows 2022 尝试时，“用户登录失败”错误未记录在错误日志中
[英]"Login failed for user" error not recorded in error log when attempted from Windows 2022
问题描述
SSMS (18.12.1) & ODBC (Native Client 11, ODBC 17) on Windows 2022 login failed and nothing in SQL Server Error log. 
SSMS (18.12.1) & ODBC (Native Client 11, ODBC 17) on Windows 2022 login failed and nothing in SQL Server Error log. Message from SQL Server is " Login failed for user... " even with known good creds , SQL Server Authentication.来自 SQL 服务器的消息是“用户登录失败... ”，即使具有已知的良好信誉，SQL 服务器身份验证。
Interestingly, there is no error recorded in the SQL Server Error log for login attempts from this Windows 2022 client.有趣的是，SQL 服务器错误日志中没有记录来自此 Windows 2022 客户端的登录尝试的错误。 Wireshark logs a response packet "Login failed for user..." coming from the active node in the failover cluster just before the conversation is ended but there is no record of this in the SQL Server Error log. Wireshark 在会话结束之前记录来自故障转移集群中活动节点的响应数据包“用户登录失败...”，但在 SQL 服务器错误日志中没有记录。 Logins from other systems (older versions of Windows) are successful with same creds and failed attempts are logged from older clients when improper creds are used.使用相同凭据从其他系统（旧版本的 Windows）登录成功，如果使用不正确的凭据，则会从旧客户端记录失败的尝试。
SQL Server 2012 Failover Cluster on Windows 2012-R2 SSMS 18.12.1 on Windows Server 2022 (TLS 1.0, 1.1, 1.2 and 1.3 enabled) SQL Server Authentication Cluster IP is NAT'd SQL Server 2012 Failover Cluster on Windows 2012-R2 SSMS 18.12.1 on Windows Server 2022 (TLS 1.0, 1.1, 1.2 and 1.3 enabled) SQL Server Authentication Cluster IP is NAT'd
0 个解决方案
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.