SQL New Login can't see domain users

  • Hi

    I'm trying to set up Windows-based SQL logins on an existing SQL 2008 installation. The installation was created by cloning a previous virtual machine, and where and how that was set up, only God knows...

    The New Login screen can't seem to see the list of domain users. I browse to the domain, it can see that; it can see a Users node under that. But the node is empty. If I change the "Location" to the Users node under the domain, and type in the name of a (known, existing) domain user in the "Enter the object name", and then press "Check name", it gives an error.

    The same thing happens when I go to Services and try to change the SQL Server service startup account to a domain account (not that I actually want to do this, just to test whether anything on the machine can browse domain users).

    I don't know much about networks, and the person who does is being... let's say, not helpful. Anyone have any idea why this is happening?

  • seb 30496 (5/18/2012)


    Hi

    I'm trying to set up Windows-based SQL logins on an existing SQL 2008 installation. The installation was created by cloning a previous virtual machine, and where and how that was set up, only God knows...

    The New Login screen can't seem to see the list of domain users. I browse to the domain, it can see that; it can see a Users node under that. But the node is empty. If I change the "Location" to the Users node under the domain, and type in the name of a (known, existing) domain user in the "Enter the object name", and then press "Check name", it gives an error.

    The same thing happens when I go to Services and try to change the SQL Server service startup account to a domain account (not that I actually want to do this, just to test whether anything on the machine can browse domain users).

    I don't know much about networks, and the person who does is being... let's say, not helpful. Anyone have any idea why this is happening?

    have you tried creating the login using query instead os SSMS? You can try it like this:

    CREATE LOGIN [DomainName\UserName] FROM WINDOWS

    In the above query change the DomainName to your domain name & UserName to your domain user name. If you get any error, post them here.


    Sujeet Singh

  • Sounds like the machine SQL is installed on is having problems authenticating against the domain, don't think it's an issue with SQL itself.

    Whether that's the machine itself being dodgy, or the computer account in AD isn't correctly configured, I can't tell (although I'd guess the latter).

    You may need to go back to the network guy (Sorry...)

    Gaz

  • Thanks for your replies.

    It's a weird problem. Come to think of it it's occurred before.

    If I set the Location to the domain, then - as mentioned before - I can't see anything under Users.

    But if I type in a fully qualified domain user name (in form DOMAIN\USERNAME), and press Check Names - it works.

    Why, exactly, this SQL screen (and, equally, the similar domain user browser in Services) can't browse domain users, I really don't know. As you said, it's probably something wrong with the computer setup in AD. (I'm guessing you meant Active Directory). I got on to the domain server and had a look in AD, but couldn't find anything that makes immediate sense.

  • Ok, I see now. The Users node on my dialog screen is the same - empty.

    You're only selecting a location there, not the user, so you shouldn't see a list.

    I was focussing on the error - what precisely was it?

    Thanks

  • How was the SQL Server instance configured at build time? If it's using a dedicated account i.e. YOURDOMAIN\MSSQLSERVER rather than NT SERVICE\MSSQLSERVER then ensure the account is a member of Domain Users to have permissions to browse AD, and (possibly) that they are a member of Account Operators too.

    ---

    Note to developers:
    CAST(SUBSTRING(CAST(FLOOR(NULLIF(ISNULL(COALESCE(1,NULL),NULL),NULL)) AS CHAR(1)),1,1) AS INT) == 1
    So why complicate your code AND MAKE MY JOB HARDER??!:crazy:

    Want to get the best help? Click here https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help (Jeff Moden)
    My blog: http://uksqldba.blogspot.com
    Visit http://www.DerekColley.co.uk to find out more about me.

  • Thanks for your replies.

    Gazareth; there wasn't an error message - just that it wasn't possibly to browse AD domain users. I'm sure I used to be able to at some point (when I was working another job years go) - rather than trying to remember exactly what spelling a domain user name has, and then having to press Check Names to see if I got it right.

    Derek, yes, that's probably one of the issues: SQL service runs under [localmachine]\Administrator, rather than under a domain account. Still a mystery why the SSMS dialog can Check Names, but can't browse the AD list of users and show them.

    At the moment I'm too tired of cross-purposes to try to get the network admin to set up a domain user with minimal rights, for the SQL service to run under, just so that it can browse AD users.

    thanks again!

  • Not sure if it can or not, but if so hope you sort it!

    I rarely type the exact name, even a couple of letters will give you a list to choose from after you hit Check Names 🙂

  • Divine Flame (5/18/2012)


    seb 30496 (5/18/2012)


    Hi

    I'm trying to set up Windows-based SQL logins on an existing SQL 2008 installation. The installation was created by cloning a previous virtual machine, and where and how that was set up, only God knows...

    The New Login screen can't seem to see the list of domain users. I browse to the domain, it can see that; it can see a Users node under that. But the node is empty. If I change the "Location" to the Users node under the domain, and type in the name of a (known, existing) domain user in the "Enter the object name", and then press "Check name", it gives an error.

    The same thing happens when I go to Services and try to change the SQL Server service startup account to a domain account (not that I actually want to do this, just to test whether anything on the machine can browse domain users).

    I don't know much about networks, and the person who does is being... let's say, not helpful. Anyone have any idea why this is happening?

    have you tried creating the login using query instead os SSMS? You can try it like this:

    CREATE LOGIN [DomainName\UserName] FROM WINDOWS

    In the above query change the DomainName to your domain name & UserName to your domain user name. If you get any error, post them here.

    I am having the same issues, when using script, adding users is a blast, when trying to search using

    Add login getting this

    However when directly on the server through RDP, it works like a charm:)

    Anybody else experienced this?

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply