0

I have a staging SQL Server that is not joined to the domain. When I access the server, I log into remote desktop as a local user on that machine.

However, I can connect to the SQL Server instance in SSMS from my machine using Windows Authentication. However, I can't find how this is working. I don't see my domain username included in the list of logins.

Is there a way to tell how my domain account has permissions to log in? This server in general is a mess and I need to start cleaning it up and setting up other users to use Windows Authentication instead of SQL Server Authentication.

1
  • What version of windows is the sql server running on? Dec 4, 2009 at 19:48

2 Answers 2

2

Ok, this is easy.

I believe that if the non-domain SQL Staging machine has a local account name that matches your domain name and it's password (minus the domain name credential), then the access will appear to be seamless without the staging server needing to be part of the domain.

1
  • Although this method is rather troublesome, and certainly adds some complication to the security. :(
    – ewall
    Dec 4, 2009 at 22:13
0

Was the server at one time connected to the domain, maybe the SQL server has an old LOGIN that is linked to the domain user.

  1. In SSMS connected to the SQL Server look under Sercurity => Logins, and Security => Credentials for users that are the same as your domain user.
  2. Check Local Users on the Windows machine to see if your username exists.

If you cannot find any obvious user connection, try disabling users one at a time until you are no longer able to connect to the SQL server using Windows Authentication.

I have seen behavior with renamed user accounts where they maintain their old relationships because the SID never changed, just the username.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .