Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSPI handshake failed with error code 0x8009030c...Someone help please Expand / Collapse
Author
Message
Posted Tuesday, March 13, 2012 5:11 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, August 8, 2012 9:05 AM
Points: 9, Visits: 11
a new instance of SQL Server 2008 was installed and it would only allow you enter with Windows authentication. When you try sa logon it fails. Please what's the issue? I saw this error in the Event viewer log, thought it might be connected:

SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. [CLIENT: 192.168.43.69].

Any solutions?

Charles.
Post #1265811
Posted Tuesday, March 13, 2012 5:20 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Thursday, February 11, 2016 9:48 AM
Points: 2,073, Visits: 1,351
have u had a look at this
http://www.secretgeek.net/boring_sql_one.asp

Have u tried connecting to the server any other way?


Jayanth Kurup
Post #1265818
Posted Tuesday, March 13, 2012 11:05 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, August 8, 2012 9:05 AM
Points: 9, Visits: 11
Hi
Jayanth_Kurup,

I discovered I could connect via Widows Authentication, but when I changed the password it still didn't work.
So I checked the error log and found that the installation was not configured to accept mixed mode authentication.

So I got in again via Windows Auth and changed the settings.

http://msdn.microsoft.com/en-us/library/ms188670.aspx.

It's Okay now. Thanks.
Post #1266135
Posted Monday, June 24, 2013 10:04 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Sunday, February 21, 2016 1:18 PM
Points: 36, Visits: 337
Hi Jaynath,
I am a newbie. Now I found answer for this problem. How do I find out user name. Since the logs just gives me [Client: 00.000.00.00]. And I work from a remote location. So If you could guide me that would be great help.
Thanks in advance
Post #1466967
Posted Tuesday, August 25, 2015 9:44 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, November 9, 2015 7:01 AM
Points: 41, Visits: 184
@wondermorris8

I am experiencing the same issue... Did you figure out how to find the user\account?
Post #1714341
Posted Wednesday, August 26, 2015 8:12 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Sunday, February 21, 2016 1:18 PM
Points: 36, Visits: 337
Hi Arc211, yes I found solution on how to find user by IP address.
In cmd prompt type ping -a youripaadress

This will let you know user machine.

Sorry didn't check this mail earlier. Hope this can still help.
Post #1714829
Posted Wednesday, September 2, 2015 8:41 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, November 9, 2015 7:01 AM
Points: 41, Visits: 184
I was actually talking about the SQL SERVER Login.... I can see the computer that is trying to make the connection but not the account.
Post #1716447
Posted Thursday, November 5, 2015 1:25 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, November 9, 2015 7:01 AM
Points: 41, Visits: 184
I'm experiencing the same issue again, but I still don't know how to determine which user account is the culprit.... Can anyone help?
Post #1734187
Posted Thursday, December 3, 2015 3:41 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, June 30, 2016 1:20 AM
Points: 13, Visits: 66

I've faced the same issue, but i solved.

Issue:
SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. The logon attempt failed [CLIENT: xxx.xxx.xx.xx]

Solution
Domain controller not behave correctly , multiple gateway some time dis-join or redundancy on single network. change and correct DNS address.

Run -- > type --> ncpa.cpl --> click Ethernet--> properties --> IP V4--> Check primary / Secondary DNS IP address.

connect SQL through window authentication, it will work.


Regards
Mubashir


Post #1742220
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse