I have two computers running SQL Server 2008 Express: c01 and c02, I setup both for remote connection using windows authentication. Worked fine for c02 but not for c01.

This is the error message I'm getting:

Cannot connect to ACAMP001\SQLEXPRESS.


Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. (Microsoft SQL Server, Error: 18452)

For help, click: http://go.microsoft.com/fwlink?>ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18452&LinkId=20476

I don't know if I'm missing something, here is what I did:

  1. Enabled TCP/IP protocol for client from Sql Server Configuration Manager.
  2. Modified Windows firewall exceptions for respective ports.
  3. Started the Sql Browser service as a local service
  4. Added Windows user to this group: "SQLServerMSSQLUser$c01$SQLEXPRESS"
  5. From Management Studio, I added "SQLServerMSSQLUser$c01$SQLEXPRESS" to SQLEXPRESS instance's logins under security folder, and I granted sysadmin permissions to it.
  6. Restarted c01\SQLEXPRESS
  7. Restarted Sql Browser service.
  8. There is no domain here. It's only a workgroup.

Please any help is appreciated, Thank you.

3 Answers 3


Whatever username you are using on the "remote" machine must be set up on the "server" machine.

So, if you are logged-in to "remote" as "John," there must be a "John" user on the machine that is hosting SQL Server 2008 Express, and unless you are going to provide different credentials, it should have the same password, too.


I think you should be able to use the runas command to set up your connection in SSMS. Create a shortcut on your desktop (or wherever), and set this as the target location:

runas /user:DOMAIN\account /netonly C:\path\to\ssms.exe

If this is a workgroup, then DOMAIN may be the name of the computer SQL Server is installed on. Obviously, the account you're setting here will have to exist on the computer hosting SQL Server.

This setup also works for domain users trying to connect to a SQL Server instance in another domain.

  • (Just noticed that this was an old question. Oh well!)
    – bhamby
    Commented Apr 16, 2012 at 16:18

Try 'mixed authentication mode' and see if that helps. I've seen this error with the opposite configuration (i.e. trying to login with a SQL user on a system set up only with Windows Authentication).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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