sql server connect: Hello,

I set up a new SQL 2005 SP1 server. Everything was fine for 2 weeks.
Suddently I got error "cannot generate SSPI context" when connecting to it
from a client PC, as shown below. When I use setspn to check the server I
see the line with port 1709. I check netstat -an and found no one is
listening on 1709. Do you know what created that spn entry? This is a new
SQL Server.

Also do you know why might cause this suddent SSPI error? We did not make
any change to the server or domain accounts running SQL services.

C:\Documents and Settings\ktran315>setspn -l hdqncsql1
Registered ServicePrincipalNames for CN=HDQNCSQL1,OU=Unmanaged
Servers,OU=HDQ,DC=mih,DC=mcorp,DC=mycompany,DC=com:
MSSQLSvc/hdqncsql1.mih.mcorp.mycompany.com:1709
MSSQLSvc/hdqncsql1.mih.mcorp.mycompany.com:1433
HOST/HDQNCSQL1
HOST/hdqncsql1.mih.mcorp.mycompany.com

F:\>sqlcmd -S hdqncsql1 -E
HResult 0x80090322, Level 16, State 1
SQL Network Interfaces: The target principal name is incorrect.

Sqlcmd: Error: Microsoft SQL Native Client : Cannot generate SSPI context.

thanks,

To find out which application is using port 1709, you can use TCPVIEW
from www.microsoft.com/technet/sysinternals/utilities/tcpview.mspx

To troublesoot "Cannot generate SSPI context" errors, see:
http://support.microsoft.com/kb/811889
http://www.sqlservercentral.com/articles/Installation/cannotgeneratesspi
context/929/


--
Razvan Socol

For the official list of port assignments, see
http://www.iana.org/assignments/port-numbers
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.

[quoted text, click to view]