Re: security not applying on some client machines

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Joan Wild (jwild_at_nospamtyenet.com)
Date: 02/26/04 

Date: Thu, 26 Feb 2004 15:55:55 -0500

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. 

-- 
Joan Wild
Microsoft Access MVP
"ChrisA" <chris@nospam.atlas-anchor.com> wrote in message
news:DBs%b.82995$Hy3.38624@edtnps89...
> 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: 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)
  • RE: Script for find dominos users
    ... The key lies in the fact that Domino web servers will ... "404" nonexistent URI if the database does not. ... Choose not to allow email through the web (Application Security, ... server's server document. ...
    (Bugtraq)
  • Re: Newbie Salt and Pass Phrase Question.
    ... is it a server side application? ... The database contains private ... The second biggest problem confronting me is that security was ... My client, a tennis coach, tells me other coaches at the same ...
    (sci.crypt)
  • Re: Is this possible??
    ... The OwnerAccess option is used with user level security - which is only ... the application from the beginning using client/server concepts such as ... You would keep the back end database on the server where only ...
    (microsoft.public.access.tablesdbdesign)