Sql-server – Cannot Generate SSPI Context when connecting to the remote Computer

odbcsql serverwindows-server

I am connecting to Windows Server 2008 R2 which has SQL server 2005 installed via ODBC from a client machine. Recently I started getting this error

Cannot generate SSPI Context.

I have gone through similar questions but have not got any helpful answer.

Best Answer

There is a problem with the SPN of the SQL Server. Look at the Microsoft Kerberos Configuration Manager tool. https://www.microsoft.com/en-us/download/details.aspx?id=39046

This will look at the SQL Server and tell you what the SPN issue is with the machine and provide you a script to resolve. The script will need to be run by someone with Domain Admin permissions. This tool essentially automates the manual steps found in this article. https://support.microsoft.com/en-us/help/811889/how-to-troubleshoot-the-cannot-generate-sspi-context-error-message

Related Solutions

Postgresql – limit access to postgresql 8.4 databases via ODBC on the server side

ODBC is a client tool and does not affect the way that Postgresql verifies access. I don't know if its any different for a postgresql server on windows, but in linux, there is a file called pg_hba.conf. This file is usually located in the data directory of the server install. In Linux, you typically find it in /var/lib/pgsql/data/.

This file allows you to define which ip addresses can access your postgresql server and how they may access it. Types of access include trust (no password), md5 (password), etc.

So for example, if your access users are on say 192.168.0.10 and you want them to use a password you would add this entry.

# TYPE  DATABASE    USER        IP-ADDRESS    IP-MASK             METHOD
host    all         access_user         192.168.0.10    255.255.255.255     md5

In postgresql you would then have to create the user and give him the ability to login.

1. psql -d nameofdatabase
2. CREATE ROLE access_user WITH LOGIN PASSWORD 'jw8s0F4';
3. GRANT SELECT ON nameoftable TO access_user;

Good luck

Sql-server – SQL Alert: 020 – SSPI handshake failure. Tracking the cause

Usually when you get the SSPI notification (or from the error log ), you will see the IP address from which the app\user tried to connect. The IP may be internal or external.

Just launch the command line and type:

NSlookup IP

(using the IP address from the log). This will give you the hostname from which the connection request came.

Best Answer

Related Solutions

Postgresql – limit access to postgresql 8.4 databases via ODBC on the server side

Sql-server – SQL Alert: 020 – SSPI handshake failure. Tracking the cause

Related Question