January 24, 2012 at 7:46 am
Good day! (actually happy lunar new year to everyone!)
I understand sometimes it is caused by the time is not correct or account is locked, I checked both, both are fine, I just suddenly got this error when trying to remote into my server via VPN (no problem before), I have to remote into the machine first and then open SSMS there, although it is not an urgent issue, but I am wondering why this happens to me?
Thank you.
January 24, 2012 at 9:43 am
There are several reasons that could lead to this error. From your post it does not look like you are using a double hop to connect to the instance.
hopefully, you have googled this issue, if not take a look at the following links.
http://support.microsoft.com/kb/811889
Blog
http://saveadba.blogspot.com/
January 24, 2012 at 10:55 am
Thank you for your input, I already read the first KB before, I think it says I need to configure SPN on my local machine. Correct me if I am wrong.
I am not an active directory person, there has never been such a problem before, there is a big headache if the AD guy is to be involved, I am hoping someone can shed me more light and resolve this problem without asking my colleagues.
Thank you very much.
January 24, 2012 at 11:13 am
I have seen this happen when you have a domain account logged onto SQL and you change the domain account password. If you then try log on from another computer it will let you log onto the domain, but you get this error when youtry log onto SQL.
Have you changed your password? if so check that your account isn't logged on via another computer.
Cheers
Leo
Leo
Nothing in life is ever so complicated that with a little work it can't be made more complicated.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply