Vista SQL 2005 SP2 Client To Windows XP SQL 2005 (non-sp2) Workstation.

I'm trying to use SQL Management Studio to connect from a Vista SQL 2005 client w/ SP2 over to a Windows XP workstation running SQL server developer edition (non-sp2) using windows authentication.



I'm already preauthenticated by network shares to the xp workstation. This worked just fine in windows xp but stop working in vista.



After searching around, i found out that vista handles trusted authentication differently than windows xp due to changes in the SSPI. Logging in as sql authentication works fine. Logging in as windows authentication does not.



UPDATE: I found out that two workstations running vista and sql 2005 sp2 cannot connect to each other using windows trusted authentication!!!



What the heck?



UPDATE: I found out that my IIS 7.0 using ASP.NET and connecting to SQL 2005 (non sp2) on a Windows 2003 server (SP1) WILL connect to the database using trusted authentication... apparently IIS can access the credentials and pass them to the sql 2005 box just fine. My Sql 2K5 SP2 tools cannot. I'm forced to use SQL authentication to the box.



Same thing applies with a Windows XP SP2 box running SQL 2005 (non sp2).


Here is my sql server error log off of the windows xp workstation:

2007-04-26 15:41:32.34 Logon Error: 17806, Severity: 20, State: 2.
2007-04-26 15:41:32.34 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.254.100]
2007-04-26 15:41:32.34 Logon Error: 18452, Severity: 14, State: 1.
2007-04-26 15:41:32.34 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.254.100]




How can i Fix this issue?



[1] Client side:

What is the connection string in you app or DSN?
N/A
If client fails to connect, what is the client error messages?

Is the client remote or local to the SQL server machine?
Remote

Can you ping your server?
YES

Can you telnet to your SQL Server?
YES

What is your client database provider?
SQL Management Studio

Is your client computer in the same domain as the Server computer?
WorkGroup

What protocol the client enabled?
Shared Memory & TCPIP

Do you have aliases configured that match the server name portion of your connection string?
NO

Do you select force encryption on server and/or client?
NO

[2] Server side:



What is the MS SQL version?
SQL Server 2005

What is the SKU of MS SQL?
Developer

What is the SQL Server Protocol enabled?
Shared Memory & TCPIP

Does the server start successfully?
YES

If SQL Server is a named instance, is the SQL browser enabled?
N/A

What is the account that the SQL Server is running under?
Network Service

Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider?
YES

Do you make firewall exception for SQL Browser UDP port 1434?
N/A

[3] Platform:

What is the OS version?
Client - Windows Vista Final w/ SQL Server 2005 SP2 & Network Client SP2

Server - Windows XP Professional SP2 w/ SQL 2005 Server Developer Edition

Do you have third party antivirus, anti-spareware software installed?
None

[4] Misc:

If you have certificate configuration issue: Please use €œcertutil.exe €“v €“store my€? to dump certificate specific info and post it in your question.
N/A

Tips:

1. Find SQL Server Errorlog: Default to C:Program FilesMicrosoft SQL ServerMSSQL.#MSSQLLOG

2007-04-26 15:41:32.34 Logon Error: 17806, Severity: 20, State: 2.
2007-04-26 15:41:32.34 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.254.100]
2007-04-26 15:41:32.34 Logon Error: 18452, Severity: 14, State: 1.
2007-04-26 15:41:32.34 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.254.100]






[1] Client side:

What is the connection string in you app or DSN?
N/A
If client fails to connect, what is the client error messages?

Is the client remote or local to the SQL server machine?
Remote

Can you ping your server?
YES

Can you telnet to your SQL Server?
YES

What is your client database provider?
SQL Management Studio

Is your client computer in the same domain as the Server computer?
WorkGroup

What protocol the client enabled?
Shared Memory & TCPIP

Do you have aliases configured that match the server name portion of your connection string?
NO

Do you select force encryption on server and/or client?
NO

[2] Server side:



What is the MS SQL version?
SQL Server 2005

What is the SKU of MS SQL?
Developer

What is the SQL Server Protocol enabled?
Shared Memory & TCPIP

Does the server start successfully?
YES

If SQL Server is a named instance, is the SQL browser enabled?
N/A

What is the account that the SQL Server is running under?
Network Service

Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider?
YES

Do you make firewall exception for SQL Browser UDP port 1434?
N/A

[3] Platform:

What is the OS version?
Client - Windows Vista Final w/ SQL Server 2005 SP2 & Network Client SP2

Server - Windows XP Professional SP2 w/ SQL 2005 Server Developer Edition

Do you have third party antivirus, anti-spareware software installed?
None

[4] Misc:

If you have certificate configuration issue: Please use €œcertutil.exe €“v €“store my€? to dump certificate specific info and post it in your question.
N/A

Tips:

1. Find SQL Server Errorlog: Default to C:Program FilesMicrosoft SQL ServerMSSQL.#MSSQLLOG

2007-04-26 15:41:32.34 Logon Error: 17806, Severity: 20, State: 2.
2007-04-26 15:41:32.34 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.254.100]
2007-04-26 15:41:32.34 Logon Error: 18452, Severity: 14, State: 1.
2007-04-26 15:41:32.34 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.254.100]