Question : odbc connection failed.  error sql state 28000  sql server error 18452

Can't connect a new client box (with XP pro SP3) to our existing sql server instance in our office. A dozen other computers connect just fine. We are a Workgroup setup, no domain. SQL Server is installed on a stand alone server up (Windows 2003)  with Windows authentication.

The user name and password (spelling and case) have been doubled checked in Local Users set up on the server. (password checked not to expire, just like the rest of our client set-ups)

Also, in our SQL database  on the server, in the security folder, the user name path shows correctly.

The ODBC DNS configuration on the client box is set with Windows NT authentication. Network libraries are TCP/IP with port dynamically determined. (Protocols for SQLEXPRESS have TCP/IP and named pipes enabled.)

I can't find what I'm overlooking that is keeping the sql server from seeing this client machine.

Should I try renaming the user on the client machine (no data/settings to lose on this new box) ? I thought maybe a maximum amount of clients has been reached  for a Workgroup arrangement (SQL is set to zero - for no limit on connections)?


Unfortunately I am not a database person of any sorts, so kindly bear with me as I work to grasp your responses.

ES

Answer : odbc connection failed.  error sql state 28000  sql server error 18452

Hi,

mmm this might like a long shot but please bear with me

You said
 "Dozen other computers connect just fine"

So this particular machine using this particular username/password is not working

can you try creating a new user profile that you know is for sure working on other machines... if this works delete the failed profile and create it again this should rebuild the ODBC files, I faced this once and turned out to be a windows profile issue.

This should work if am not mislead but your case scenario