search for: temmokan

Displaying 5 results from an estimated 5 matches for "temmokan".

2011 Jan 13
2
Problem: how to make users use unique passwords
Hello, To harden security, I've modified the smbldap-passwd script so that it update sambaPwdMustChange, sambaKickoffTime and shadowExpire fields; also, a simple script notifying users with expiration date approaching has been set up. I have also added a call to cracklib to check password strength prior to applying it. It all works well, but the task it to force users to use unique password
2010 Dec 07
2
PDC (CentOS 5.5, Samba 3.5.6): no domain group names sent to Windows 2003 members
Hello, After setting up Samba 3.5.6 on CentOS 5.5 (built from sources) I have noticed a strange problem. Windows 2003 servers participating in this Samba domain do not receive domain groups list when I, say, try to assign security credentials for a file/folder. When I choose domain as source, search reveals only technical group names and individual domain users names. No domain group names
2011 Dec 16
0
System Shock 2: problem viewing intros
Hello, I managed, finally, to make System Shock 2 work smoothly on a Fedora 16 64-bit, wine version 1.3.33, on a computer using Intel Graphics (game installed, SSTool applied, VSync disabled, 16-bit mesa/libGL2 installed, LIBGL_DRIVERS_PATH set to /usr/lib/dri before the game is started via 'taskset -c 1') The problem was running intros. Until I run winetricks quartz devenum
2010 Nov 08
1
Samba 3.5.6: can't follow symlinks on shares
Hello, Samba version: 3.5.6, OS CentOS 5.5 64-bit. The problem: I have a share with symlinks leading outside the share. After mounting the shared resource (cifs), I can't proceed through symlinks (permission denied). Setting options follow symlinks = yes wide links = yes for the share doesn't change Samba behaviour. Could someone enlighten me on how to handle this? Thanks.
2010 Nov 11
0
Samba on domain member refuses to work after certain time has passed
Hello, The configuration files for PDC and the server in question are below. Both have Samba 3.5.6 installed, firewalls pass all smb/nmb traffic, CentOS 5.5.x86_64 runs on both. The situation: after the server (DEVSERV in the example below) starts its Samba, it works fine for approx 1-1.5 days. After that it abruptly stops servicing any shared resources. The only cure is to stop Samba,