security not applying on some client machines

From: ChrisA (chris_at_nospam.atlas-anchor.com)
Date: 02/26/04 

Date: Thu, 26 Feb 2004 20:24:03 GMT

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

Relevant Pages

  • Re: [Full-Disclosure] SSH vs. TLS
    ... > frowned upon by network ops and security. ... > - There must be a secure means by which all server keys are distributed to ... > appropriate ssh clients. ... > servers from using expired keys. ...
    (Full-Disclosure)
  • Re: Real time notification
    ... Thanks Sahil for detailed reply. ... > reaction was that I will use a database. ... > a) Logical - The central server informs the clients of a change. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: number of critical errors occurred on SBS 2003
    ... SharePoint 3 has been around for a while for SBS, and if it were installing with the database security defaulting to an incorrect setting, that would be well known by now. ... I would check all the installation docs and the release notes, but I would assume the security is correct unless you find written documentation to the contrary. ... mode of the SQL Server in regards to event ID: ...
    (microsoft.public.windows.server.sbs)
  • Re: SceCli Error 1202 filling up the Event Log!
    ... > after restarting the Win2003 server, the secedit.sdb database does not get ... >>> security database and have it recreated. ... >>> configuration\windows settings\security settings, you should inventory ...
    (microsoft.public.win2000.advanced_server)
  • Database Access Issue
    ... I reciently attempted to migrate a database application and a number ... of file shares from an NT4 server to a Windows 2000 server. ... XP, Mac OSX, and Mac OS 9.x. ... Following the migration all clients were able to access the file ...
    (microsoft.public.win2000.macintosh)