Connection Error 18452 - Login failed for user '(null)'

Hello everybody,
one of our users gets an error message when trying to connect to our SQL
Server database:
Connection failed:
SQLState: '28000'
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
The problem occured suddenly during work. The user can connect to the server
using another computer and other users can connect using his computer.
Knowledge base didn't help so I'm asking you.
Configuration
Client: Windows XP professional (2002/SP1)
ODBC driver: SQL Server (2000.81.9042.00)
Client configuration: TCP/IP
Server: Windows 2000 Server
SQL Server 7.0
Seems the network setup for the user is somehow corrupted, since the message
states the user to be '(null)'.
Any suggestions?
Thanks in advance,
Markus Wolff
I have the same problem and this is a problem associated with trusted SQL
Server connections, there is a document out there that says that if you use
named pipes everything is great but using TCP/IP, then you need to configure
Active directory and possibly using kerberos (instead of NTLM). I was hoping
to get more info on how to set out systems at work so that trusted
connections can work.
"Markus Wolff" wrote:

> Hello everybody,
> one of our users gets an error message when trying to connect to our SQL
> Server database:
> Connection failed:
> SQLState: '28000'
> SQL Server Error 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection.
> The problem occured suddenly during work. The user can connect to the server
> using another computer and other users can connect using his computer.
> Knowledge base didn't help so I'm asking you.
> Configuration
> Client: Windows XP professional (2002/SP1)
> ODBC driver: SQL Server (2000.81.9042.00)
> Client configuration: TCP/IP
> Server: Windows 2000 Server
> SQL Server 7.0
> Seems the network setup for the user is somehow corrupted, since the message
> states the user to be '(null)'.
> Any suggestions?
> Thanks in advance,
> Markus Wolff
>
>