Table permissions: No matter what I set all users have full access?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Mark - 28 Mar 2006 13:39 GMT

Hi

Following my earlier question ((CROSS POSTED) Very strange: Connection under
process info not whats in front-end)

I have set the permissions for a particular table so that none of the listed
users can do anything (select, insert etc.) yet when I connect from another
machine via the ADP using Windows authentication (from a login thats not
even listed in the servers users I might add) I still have full permissions
on the table. I get the impression I am missing something here...

Any pointers much appreciated

Mark

Reply to this Message

Mark - 28 Mar 2006 16:00 GMT

Update: I have created a new Windows user (against the same domain) the
logged on to another PC as that user and can still access the database with
full permissions. The new user does not have a login on the server and is
only a member of the Guests group in the domain.

I even created a login for the user and denied SELECT permissions on various
tables and that made no difference either.

Nothing I do seems to affect what users can do to the data and the process
info under current activity always shows the server admin user, not the user
who is logged into the machine thats doing the editing. This is the same for
all databases on my test server.

Whoever I log onto the client machine as I always show up on the server as
the same admin user and even denying that user (i.e. the admin user)
permissions on specific tables makes no difference.

This is driving me crazy... Any help much appreciated

Mark

> Hi
>
[quoted text clipped - 11 lines]
>
> Mark

Reply to this Message

Ecomorph - 30 Mar 2006 10:41 GMT

Just a thought...

What about the DSN ODBC connection file? Could there be a Connection
file that was set up with Saved user name and pw.

Reply to this Message

Mark - 30 Mar 2006 21:53 GMT

I did actually check that it was not the case...

(snip from my other post)

"I believe that possibly (and I'm hoping someone can confirm this) that the
problem was due to the fact the server and client are on a test network that
does not use a domain controller."

Cheers

Mark

> Just a thought...
>
> What about the DSN ODBC connection file? Could there be a Connection
> file that was set up with Saved user name and pw.

Reply to this Message

Sylvain Lafontaine - 30 Mar 2006 18:09 GMT

Well, if the Login used was not even listed in the server's list of users,
then that account shouldn't even have the ability to connect to the
SQL-Server. Obviously, you are making something wrong.

Maybe a look with the SQL-Server Profiler will tell you more about this.

Signature

Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF

> Hi
>
[quoted text clipped - 11 lines]
>
> Mark

Reply to this Message

Mark - 30 Mar 2006 21:52 GMT

Thanks Sylvain

I believe that possibly (and I'm hoping someone can confirm this) that the
problem was due to the fact the server and client are on a test network that
does not use a domain controller.

Thanks again

Mark

> Well, if the Login used was not even listed in the server's list of users,
> then that account shouldn't even have the ability to connect to the
[quoted text clipped - 17 lines]
>>
>> Mark

Reply to this Message