NT Only Security With NT Groups

NT Only Security With NT Groups

Post by Gopal Ash » Wed, 26 Jul 2000 04:00:00

Hi Jeff,

When you setup NT groups for SQL logins, one thing that you have to make
sure is that the local group resides on the machine in which SQL Server is
I have seen many cases where people create the group on the PDC and then
try to grant login to that group.

For e.g.
If your machine name is SQL and the domain is SQLDOM and you create a Local
Group in the domain called SQLGRP and grant login to that group it won't

Create a Local Group (SQLGRP)in the machine itself, add domain users or
global groups to that local group, then grant login to that local group.
So you will be granting access to SQL\SQLGRP rather than SQLDOM\SQLGRP.

I'm not sure if you arehaving the same problem, but this is the most common
mistake people make when granting login to NT groups.

Hope this helped



1. SQL 7 Group Security and Predefined NT Groups

We are attempting to test SQL Server 7.0 security and it seems that you
can't add an NT predefined group (such as Domain Users) to SQL Server's
roles and then get the permissions in the database to work.  This does
appear to work, however, with new groups we create in NT.

Can anyone verify this or point us to documentation that states this?

Thanks, John

2. Database in Redhat Linux

3. SQL Server & NT Security Groups

4. MS Search Service (sql 7) and Local variables

5. security: NT local groups

6. Join Predicate Question

7. NT User Groups and security related functions

8. lookup runtime error

9. SQL 6.5 security manager fail to enumerate global group members after NT upgrade to SP5

10. NT local group not showing up in Security Manager

11. setting permissions for NT Groups with Mixed security...

12. NT/SQL Security Groups... Need suggestions

13. Sever Won't Refresh NT Group Security