security not going across the network

[dennis]

I have just setup security (groups and users) on a
database that is running across a network. When using my
PC, the one the database security was setup on, it works
fine (asks for username and password). When accessing the
database from another computer, it doesn't ask for a
username and password, it just opens as it normally did.
The database is situated on a designated file server. Do
I have to go to every individual PC and setup the security
on them?

 

[Rick Brandt]

I have just setup security (groups and users) on a
database that is running across a network. When using my
PC, the one the database security was setup on, it works
fine (asks for username and password). When accessing the
database from another computer, it doesn't ask for a
username and password, it just opens as it normally did.
The database is situated on a designated file server. Do
I have to go to every individual PC and setup the security
on them?

No, it means you have not set up security properly. When secured properly,
anyone who needs to use the file would have to use the MDW file you created
when you applied security. Anyone attempting to open the file with a
different MDW file should be denied access.

The other users are likely still opening the file with their default
System.MDW file. Regardless of which MDW file they are using, if they are
not being prompted for a UserName and Password, then they are being
silently logged in as user "Admin" as a member of the default group
"Users". Your security settings should have removed all permissions from
both of these. The fact that they can open the file indicates that you did
not.

Also check the ownership of the database and all objects. Owners have
rights above and beyond the permissions explicitly granted to them. A
common mistake when securing a file is to leave "Admin" as the owner of the
database. As such he will be able to open the file even though you have
removed all permissions.