Hi Glen :
I use a method which "force" the policies reading from Windows
workstations,
this is a very secure and effective way :
----------Begin cut ---------------
REGEDIT4
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\Update]
"NetworkPath"="\\\\LOGONSERVER\\netlogon\\config.pol"
"UpdateMode"=dword:00000002
"Verbose"=dword:00000001
----------end cut -------------------
Only cut the text, change "LOGONSERVER" and "config.pol" to
adjust your
needs, save it on a plaint text archive ending with .reg, double click
over it and viola!!, your Windows 9x workstation will use policies
..........
Regards,
Hugo Segura
e-mail : hsegura@acm.org
Glen Gibb wrote:
> Hello all,
>
> I wrote yesterday about problems with Windows policies and Samba 2.0.4b
> yesterday. Since then, I've had someone ask for a more detailed
> explanation, so here it is.
>
> Samba currently provides domain logons for a number Windows 95 and 98
> clients (as well as the standard file serving). The domain logon currently
> succeeds, a user's username and password is accepted and the client
> computer proceeds to execute the login script (a .BAT file). However, the
> client computer does not use the policy file which is located in the
> netlogon share.
>
> I will point out the the login script and the policy file are located on
> the same share, both with the same set of permissions (writeable by one
> priveleged user only, group and world readable).
>
> Hopefully this will clear up any confusion that my original message may
> have caused.
>
> Glen Gibb
> Ridley College