Error 18452 / Login failed The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452)

Question

 

I have a server  dbsrv1  which also has the dns - name dbsrv (with a different ip adress). (SQL SRV 2008 (10.0.2351))

(the purpopse of the second name is that every application should access the server through dbsrv ... and if i later update or switch the server .. i only have to move the dbsrv name + ip address)

If i try to access the db through dbsrv1 everything works fine. (windows authentification) if i try to access the server through the name "dbsrv" i get the error message:

Error 18452 / Login failed The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452)

or in German

Anmeldefehler. Die Anmeldung stammt aus einer nicht vertrauenswürdigen Domäne und kann mit der Windows-Authentifizierung nicht verwendet werden. (Microsoft SQL Server, Fehler: 18452)

In the Eventlog there is the message:

Fehler beim SSPI-Handshake (Fehlercode 0x8009030c) beim Herstellen einer Verbindung mit integrierter Sicherheit. Die Verbindung wurde geschlossen. [CLIENT: x.x.x.x]

The server is configured as windows + sql mode.

This connection is opened with the SQL server management studio.

 

Whats the reason for this ? how is it handled in cluster environments (there must be a similar problem)

 

Answer 1

I have not had that error myself.  But it looks like Michel Barneveld had a similar (but not identical) problem with a DNS alias and he blogged the solutions at:
http://blog.michelbarneveld.nl/michel/archive/2009/11/11/login-failed-microsoft-sql-server-error-18452.aspx

The SQL Protocols team has a blog and here is one entry.  I understand that the lack of mixed mode is not your problem, but this may also offer some other clues. 
http://blogs.msdn.com/sql_protocols/archive/2005/09/28/474698.aspx

In the conversation that follows, Ming also suggests that alias users "check whether you configured the same port that server was listening on in the TCP Alias properties" and "double check whether you spcify the correct sql port number in your alias".   Another user simply deleted his alias, which is not what you want to do. 

RLF