July 18, 2010 at 7:20 am
i had add a group to windows group and users "Apress_Product_Controllers" and add to this the Adminstator and Omar(current login User) users
and then Go to SQL Menagement Studio-> security-> logins then click add new login and name it "Apress_Product_Controllers" as windows Authentaction and then add a specific data base to it as database membership as public then restart the ssms then type in login scerrn as a server name "Apress_Product_Controllers" and i get this error
"
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)"
Error NO 53
and i dont know how to connect to this login i have just created
July 19, 2010 at 9:34 am
I'm trying to understand what you've written as it looks like you've got the server name and the windows group mixed up.
If I have a server name of MyServer, then in SQL Server Management Studio, that's what I put for the server name. If I'm using Windows authentication, I won't have a choice of what user to log on with. It's going to use the Windows user which started Management Studio. If you're filling in the login and password boxes, then it is attempting SQL Server authentication, not Windows, and that won't work.
You'll need to make sure the user you're logged on as to Windows is a member of the Apress_Product_Controllers group. And then start SQL Server Management Studio and try to connect.
Now the error you're getting looks like you can't see the SQL Server. Can you connect to it via some other means across the network? Say with a different account? If you're logging on to the server and then bringing up SQL Server Management Studio to connect, that might mean the SQL Server isn't configured to to talk on the network. Is that what you're doing? The fact you've dropped down to Named Pipes and failed to connect using that is usually an indicator that either the SQL Server is not started or it's not able to talk on the network.
K. Brian Kelley
@kbriankelley
July 19, 2010 at 9:35 am
I am not sure what you are trying to do. You have database A. You created a Windows Group Apress_Product_Controllers and added the two login Omar and administrator to that group. And then you added this group to access SQL Server with the correct rights. Am I correct so far?
So why are you using the Apress_Product_Controllers as your server/Instance name? Or am I wrong here? Could you clarify that point? Then we could help you
EDIT : Brian, Sorry. Did not see your post.
-Roy
July 19, 2010 at 1:34 pm
i have make alogin on sql server but now i downt know how to use it to secure the other databases when i contct to sql via the userAcount wich is member of the group i have creat i founfd that ia have acess to the other database wich i havent give permission to but i may know need to use the login i create on the right way could you please help me on that?
July 19, 2010 at 2:06 pm
You need to check all the group membership for that login. SQL Server will look at all Windows groups that have been given access and combine the permissions. So, for instance, if user John is a member of:
- Banking Project Developers
- HR Project Developers
and Banking Project Developers has accessing to the Banking database and HR Project Developers has access to the HR database, then when John logs in, he will have access to BOTH the Banking and HR databases.
Also, chances are your local Administrators group is a member of the sysadmin server role (look for a login called BUILTIN\Administrators and check its server roles). If it does, anybody who can map into that group, whether directly or through a nested group (like you've done), has access to all databases.
K. Brian Kelley
@kbriankelley
July 19, 2010 at 6:15 pm
so the resone for still seeing the other database that my current user however its in the windows group for this login and it also have a login for this user itself so i still have permisssion to other database which is not have permision in the new login?
July 21, 2010 at 9:32 am
If the user is a member of a Windows group with access, yes, that'd explain why they'd see the DBs when someone who isn't a member of the group wouldn't. So if you have someone with membership in a group that is a member of the sysadmin role in SQL Server, they will see everything.
K. Brian Kelley
@kbriankelley
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply