Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After installing and setting up new machines in a domain, we decided to rename one of them which had a SQL Server instance installed. So I changed the hostname, everything went fine regarding the domain but now, the server is logging a approximatively 2 SQL Server errors every 5 minutes and I cannot connect to the instance localy or from anywhere within the domain.

Here is the error from the event log:

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: x.x.x.x]

Concerning the instance, everything is started and restarted without any extra error.

share|improve this question

I would say all your logins were of the form of 'computername\username' and because the computername is now different the logins don't not work anymore. If you don't have SQL-Authentication of the 'sa' password, you need to start SQL-Server in single-user mode in which any local administrator has access and you can fix your broken logins.

share|improve this answer

Have you taken a look at this article?

It might have some ideas for you.

share|improve this answer
Welcome to Server Fault - we generally expect answers here to contain more content. Please consider expanding your answer so it's still useful after Microsoft breaks your link. Thanks! – voretaq7 Oct 22 '12 at 16:56

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.