Nov 11, 2015 · 4170 41st Ave S, Suite 101 Fargo, ND 58104 +1 888 319-3663
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 . Cannot Generate SSPI context Solutions | Experts Exchange As the title states, I am getting the "Cannot Generate SSPI context" errors when I try to connect to a remote SQL Server DB. My computer runs on DomainA, and the server I'm trying to connect to runs on DomainB, but I connect to DomainB via VPN before attempting the SQL logon. I am able to ping the server on DomainB by name and it resolves Cannot connect to SQL DB over PPTP VPN - Devolutions Forum 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).
Sep 05, 2008
Fix "Cannot generate SSPI context" while connecting to SQL
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.
Cannot connect to SQL DB over PPTP VPN - Devolutions Forum 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). VPN & Cannot generate SSPI context. | TechTalkz.com Mar 21, 2008 Home - Domain Web Center 2017-10-11 WE 20:01 – Start on DomainWebCenter.com 2017-11-17 FR 20:31 – Do not allow comments (Visited 9,615 times, 6 visits today)