May 21, 2015

The internet Cannot Generate Sspi Context Vpn Connection has made it possible for people to share information beyond geographical borders through social media, online videos and sharing platforms as well as online gaming platforms. Cannot generate SSPI context." Nothing appears in the SQL Server log. VPN creds are same, can rdp to host using same creds and am a domain admin. The target principal name is incorrect. Cannot generate SSPI context. The SQL Connection settings uses the SQL server IP address. I have checked the SPN records and there are no duplicates. I can ping the SQL server and telnet to port 1433 fine while connected to the VPN. DNS records resolve the server fine (however the connection uses IP address). There are 2 kinds of following errors (depends on the VPN): 1. "Login Failed. The login is from an untrusted domain and cannot be used with Windows authentication. (Microsoft SQL Server, Error: 18452)" 2. "Cannot Generate SSPI Context" Can you help me?

Remember that the “Cannot Generate SSPI context” problem described in this post only happens when connecting to a local server; thus, the “127.0.0.1” is applicable. If the connection string is prefixed with “tcp”, then you do need to modify your connection string to specify “127.0.0.1” as .

The target principal name is incorrect. Cannot generate Cannot generate SSPI context. Make sure you aren't connected to a VPN (or make sure you are connected, if needed). Test to see if it works, if it works, stop here. :-) Make sure IPV6 is disabled (no idea why). Remote in to your server as the Admin. Re: VPN & Cannot generate SSPI context. | TechTalkz.com

VPN & Cannot generate SSPI context. | Vista Forums

A hotfix resolves this problem. To work around this problem, manually create a host entry for the IP address in the client computer. To reproduce the problem, create and configure the dynamic IP address of the server computer, and then connect to the server computer by using SQL Query Analyzer or Rowset Viewer from a client computer.