search for: peus

Hi all, I would like to limit access to our samba shared printers to certain user groups by commandline without using Windows. Is this possible? Thanks! Christoph

Hi, we are using samba 3.0.24 as a printspooler for 80 network printers with a 500kB ntprinters.tdb for some years now. When we recently restarted samba we noticed that the ntprinters.tdb automatically shrinked to 24kB and printing was no longer possible. tdbdump of the original tdb-file is impossible too: "Failed to open ntprinters.tdb" The strange thing about this: we can solve

Hello experts, I've migrated our NT4 domain to sambe 3.0.20b/ldap backend with "net rpc vampire", and nearly everything works as expected. But one big problem remains: it's not possible to login to the domains member maschines now, because "the domain is not available at the moment" (translated from german). After the maschine rejoined the samba domain, login

Hi all, we have been using a samba setup with samba being an AD member, idmap backend = ad and winbind nss info = rfc2307 for several month without problems yet. But it turns out now that we cannot move useraccounts in AD from the original location "CN=Users,dc=uni-wh,dc=de" to a newly created OU "OU=uwhusers,dc=uni-wh,dc=de" because winbind doesn't get correct values

Hello everybody, we have a lot of printers shared by samba, which are still offering the old "version 2" W32X86 style print drivers, though most of our clients have been upgraded to w2k and above meanwhile. Therefore I would like to delete these old drivers, but I don't know how to achieve this without deleting the drivers for all architectures (with rpcclient -c

Hello experts, we have encountered this problem several times with different samba versions (3.0.20b now) and need a solution now which works without restarting the samba server: sometimes when a client crashes for whatever reason while it has a file on the samba server opened, this file cannot be opened for writing after the client has rebootet. The locking entry is then associated with a

Hi everybody, I've joined a fileserver running samba 3.0.24 to an AD domain using winbind and noticed that samba maps the "users" group SID (5-1-5-32-545) to gid 1001 automatically. This seems to conflict with one of ~2000 mappings I had to "inject" in winbinds winbindd_idmap.tdb by use of net idmap dump/restore, because the fileserver had millions of files with

Hi everybody, when driver files in samba's print$ share change, the clients don't recognize it automatically and continue to use the old driver files. This can be a nightmare when you have to change a driver which has been downloaded already by 50 clients, because you have to delete the old driver on every single client manually (if you do not have an advanced networkwide

Hi, I have a strange problem with user quotas enabled on a xfs filesystem and samba 3.0.21c: When a standard block device (e.g. /dev/sdc1) is used for the fs, quota works like expected: /dev/sdc1 on /mnt/tmp type xfs (rw,usrquota) output from level quota:10 debug: [2006/04/19 14:38:48, 10] lib/sysquotas.c:sys_get_quota(394) sys_get_quota() uid(4004, 4004) [2006/04/19 14:38:48, 10]

Hi, when migrating a big linux/samba fileserver with several hundred local users/uids and more than a million files to a winbind/Windows AD setup, it's not desirable to have new uids assigned for all the users from a uid range by winbindd, because the file ownerships are messed up then. Is it possible to keep the original local uids for already existing users with winbind even after