asked on

Login failed for user ''. Not associated with a trusted SQL Server connection

Hello,
I have SQL Server 2005 and Windows Server 2003. Recently I formatted and reinstalled all programs of an user computer of the WorkGroup that could access the sql server but now when I try to access to the SQL Server from the formatted computer with the same user and password I get:Login failed for user ''. Not associated with a trusted SQL Server connection.
I have the Windows Authentication in the SQL Server enabled.

Can anybody help me ?

Thanks in advance.

Raja Jegan R

Change your Server Authentication from Windows Authentication to Mixed Mode Authentication. To do that

1. Right Click Server in SSMS and Choose Properties.
2. Click Security and Choose Mixed Mode Authentication. ( SQL Server and Windows Authentication Mode)

That's it.

ASKER CERTIFIED SOLUTION

DBAduck - Ben Miller

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

McGregor09

ASKER

Hi,

Thanks for the response. From the reinstalled computer I can access all shared folders and printers in the computer running the SQL server. I guess that is what you meant.

Then, if I don't have a credential-passing problem, what can I continue to look for?

DBAduck - Ben Miller

First you can turn off the Windows Firewall and then try. Then turn it back on. Tell me what your results are and we can go from there.

McGregor09

ASKER

Hello,

Yes, I have also disabled Windows Firewall, but the same errors keep on happening...

DBAduck - Ben Miller

The other reason that you can see this, is that it is trying to use Named Pipes and it is not enabled on the server.

What are the protocols enabled on the Server side in SQL Configuration manager?

Raja Jegan R

Have you tried my comment no 23754905 by changing Authentication mode.

McGregor09

ASKER

In the SQL server the following protocols are enabled:

TCP protocol
Shared Memory protocol

but name pipes are disabled.

rrjegan17: I haven't changed the authentication mode on the server because it has to work as it is, with the Windows authentication. This problem only takes place after formatting one single client computer, and only happens in that computer.

Raja Jegan R

For Windows Authentication to work properly, Enable the Named Pipes. Kindly check it out once.

McGregor09

ASKER

At the end the problem was a wrong creation of the user in the client computer. The shown username was "Antonio Garcia" in Control Panel --> Users, but in the Users list ( Administrative Tools --> Users) , the username was "Juan". I changed the name of the user but not fixed the error. Creating the user again with the correct name on the customer computer was enough to fix the error.

Thank all for the support and ideas