SSPI handshake failed with error code 0x8009030c and Login failed for user''

Question

I got the following error when tried to connect to local machine in the non-domain environment with Windows Authentication by SSMS.

"SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security."

"Login failed for user''. the user is nothing associated with a trusted SQL server connection."

questions

1,if I saw the "SSPI handshake failed ", does it means it must used Kerberos but failed? or it is also possible used the NTLM but failed?

2,Any ideas for this issue?

---

Please click the Mark as Answer button if a post solves your problem!

Answer 1

"Non-domain environment"  Can you explain this please?

Does the Server you are having issues with not belong to a domain; e.g. is it on it's own workgroup?  If so then you cannot use domain credentials to access SQL Server; however you can use local Server credentials.

---

Please click "Mark As Answer" if my post helped. Tony C.

Answer 2

yes, workgroup, and used the local account, such as machinename\account

---

Please click the Mark as Answer button if a post solves your problem!

Answer 3

Ok thanks Micheal

The account that is failing does it have sysadmin access?

If not what is the default database for the login and does the user have access to this database?

Is the Account disabled in SQL Server?

Is the Account disabled or locked out on the Windows Server?

---

Please click "Mark As Answer" if my post helped. Tony C.

Answer 4

Hi Michael,

Firstly, "SSPI Handshake Failed" error happens usually when connection failed between the server and domain controllers or failed Kerberos authentication. For more details about "SSPI Handshake Failed" error, please review this FAQ.

Secondly, regarding to your error message, it could be caused by loopback check. To resolve the issue, please set the DisableLoopbackCheck registry entry to 1 by performing the following steps.

1.Click Start, click Run, type regedit, and then click OK.

2.Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

3.Right-click Lsa, point to New, and then click DWORD Value.

4.Type DisableLoopbackCheck, and then press ENTER.

5.Right-click DisableLoopbackCheck, and then click Modify.

6.In the Value data box, type 1, and then click OK.

7.Exit Registry Editor.

8.Restart the computer.

There is a similar blog about your scenario for your reference.
http://www.bhcblog.com/2009/10/08/fix-for-login-failed-for-user-the-user-is-not-associated-with-a-trusted-sql-server-connection/  

Thanks,
Lydia Zhang

If you have any feedback on our support, please click here.

---

Lydia Zhang
TechNet Community Support

Answer 5

Thank you all,

At the end it proved DNS issue caused the error.

---

Please click the Mark as Answer button if a post solves your problem!