June 14, 2016 at 8:06 am
Hello
I'm unable to launch SSMS on "server A" to connect to a SQL instance on "server B".
I get error...
Cannot connect to "server B" Additional information: The target principal name is incorrect. Cannot generate SSPI context. (Microsoft SQL Server)
On "server B", the SQL Server default instance is running using default port 1433. The port has been verified as enabled.
SQL Server Network Configuration->Protocols for MSSQLServer->TCP/IP, I see these IP addresses
IP1 - ##.##.###.### Active/Enabled = Yes
IP2 - ::1 Active/Enabled=Yes
IP3 - ###.#.#.# Active/Enabled=Yes
IP4 - fe80::5efe:##.##.###.###%13 Active/Enabled=Yes
If I set IP2, IP3, IP4 Enabled= False, I receive the same error from SSMS on "server A"...
Cannot connect to "server B" Additional information: The target principal name is incorrect. Cannot generate SSPI context. (Microsoft SQL Server)
If I set IP2, IP3, IP4 Active = False, I receive the error "WMI Provider Error: The specified file is read only. [0x80071779]" on server B while in SQL Server Configuration Manager
The IP address configuration does not seem to be correct. Before following the advice in the link below, I want to make sure the configuration is correct. Why would an IP address show as fe80::5efe:##.##.######%13?
https://support.microsoft.com/en-us/kb/811889
This is being looked at by multiple departments (DNS, windows admins, vendor) and I can't make sense of what I am seeing and why I can't connect. I have a "server C" that I can connect to and the only difference is that it is in a different data center and doesn't have the incorrect looking IP addresses.
Thank you in advance for any help
Thanks
Dave
June 14, 2016 at 8:39 am
are you connecting through the same connection on both the machines.
by any chance the first user is locked out?
send login details for more clarity.
Regards
Durai Nagarajan
June 14, 2016 at 9:06 am
Does this help: http://www.sqlservercentral.com/Forums/Topic1182295-391-1.aspx
Usually SSPI has to do with the service account on the server not connecting to AD correctly.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply