security not applying on some client machines

  • Thread starter Thread starter ChrisA
  • Start date Start date
C

ChrisA

I have an Access 2000 database which is split. The backend is on a Windows
2000 server the front end on 2000 pro or XP pro clients. I am trying to set
up security and have also set up a terminal server on the 2000 server for
remote users.

On using the security wizard I have set up various users with required
permissions using a the front end of the database on the Terminal Server.
This works and comes up with the logon prompt and users for the terminal
users.

However when I copy the front end to one of the 2000 clients pointing to the
database file on the server the security logon does not work and the users
are not listed in that local security wizard of Access.

Obviously I'm missing something here when it comes to applying security for
both network and termianl server users. Hope someone can give me some
direction for setting up users and permissions etc that will work on a
number of clients,

Thanks
Chris
 
The Access 2000 security wizard should not be trusted. Are you following
the steps in the security FAQ?
http://support.microsoft.com/?id=207793

The fact that TS is involved should not come into play. You should put the
secure workgroup file in the same folder as the backend. Both regular LAN
clients and the TS sessions can use that workgroup file.

Your LAN clients are not using the workgroup file you set up. They are
instead using their default system.mdw workgroup. If you secured the
database properly, they shouldn't be able to even open the database.

Review the FAQ and follow the steps exactly - just don't use the security
wizard.
 
Thanks for the insight,
Chris

Joan Wild said:
The Access 2000 security wizard should not be trusted. Are you following
the steps in the security FAQ?
http://support.microsoft.com/?id=207793

The fact that TS is involved should not come into play. You should put the
secure workgroup file in the same folder as the backend. Both regular LAN
clients and the TS sessions can use that workgroup file.

Your LAN clients are not using the workgroup file you set up. They are
instead using their default system.mdw workgroup. If you secured the
database properly, they shouldn't be able to even open the database.

Review the FAQ and follow the steps exactly - just don't use the security
wizard.
Click to expand...
 
Back
Top