October 25, 2021 at 5:34 pm
We have one user who face this issue while connecting to SQL server ''Cannot generate SSPI context" (win authentication) When i checked the user account the account looks good and there is no password issue. Same user is able to connect SQL using command prompt. what could be the reason
October 26, 2021 at 11:12 am
have the user reboot his client pc.
Be wary for stored credentials
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
October 26, 2021 at 12:53 pm
I told the user to reboot the VDI and after rebooting multiple times the issue still persist but when the user takes RDP to the server it works. Not able to find the reason.
October 26, 2021 at 1:18 pm
did you check this?
How to troubleshoot the "Cannot generate SSPI context" error message
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
October 28, 2021 at 3:45 am
In my experience, this error is most commonly caused by a missing SPN. A PowerShell module called DBATools has a wealth of SQL Server related commands, some of which identify and resolve SPN issues.
Take a look at this sample and investigate how to use set-dbaspn with the below command.
test-dbaspn -computername SQLServerComputerName
October 31, 2021 at 3:25 pm
+1 for potentially being SPN related - if the user's password hasn't expired.
When connecting locally via an RDP session, the connection will be using shared memory not TCP, so authenticates via NTLM not Kerberos, skipping any SPN related problems.
https://sqlrider.net - My technical blog
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy