SQLCHECK & SSPICLIENT - Feature Request - Sanity check @@SERVERNAME is equivalent to the requested name

I have been banging my head against the wall for hours trying to figure out why SSPI connections to MS SQL servers suddenly started to fail.

From a blind guess troubleshooting from a completely different direction I found out that the @@SERVERNAME property of the MS SQL server/services/instance was different than what was being contacted in the client.

Knowing this would have saved me a lot of pain and it's something I believe the tools should be able to figure out. At the very least SQLCHECK -- SSPICLIENT may be a different story.

If you need clarification please let me know.

まず、SSPI 接続とサーバー名情報を処理する SQLCHECK および SSPICLIENT のエントリポイントを確認します。要求されたサーバー名を SQL Server の @@SERVERNAME 値と比較する方法を特定し、ツールが不一致を明確に報告できれば作業完了とします。この issue ではファイルもテストも指定されていません。