similar to: usrmgr.exe and problems

It's exactly the same. Except that I use tdbsam instead of ldap and the error message therefore also is different in the log file. But the example and result is the same. Do you have any idea of workaround or fix? Cheers, Joel -----Ursprungligt meddelande----- Fr?n: Doug Campbell [mailto:doug@bpta.net] Skickat: den 11 maj 2005 10:49 Till: Joel Larsson, PF, Posten; samba@lists.samba.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I had a problem with smbpasswd -m The man pages says: -m This option tells smbpasswd that the account being changed is a MACHINE account. Currently this is used when Samba is being used as an NT Primary Domain Controller. This option is only available when

I have added roles and roles_users table and updated the model so that my users can have multiple roles. ("Admin" role does always have id = 1). I have added these methods to my application controller. <code> helper_method :is_admin? helper_method :is_user? def is_admin? if @session[''user''] @session[''user''].roles.find(1)

the following problem occurs when using samba 2.2.4 or 2.2.5 with ldap support as PDC: any time when a user logs on he is asked to change his/her password. whether he change it or not he will be asked again next time he logs on. this is annoying. the reason is, that the LDAP attribute 'pwdMustChange' is not updated at all. the easiest way to solve this to set the attribute to the

Greetings everyone, I have a question about the smbpasswd encrypted database and /etc/passwd -- why does the passdb backend require an entry in /etc/passwd? Is it possible to create samba encrypted users without a /etc/passwd entry? I have a samba PDC setup that is mainly just a login server, then a separate server for $HOME's. I have all of my PAM configs setup to remotely authenticate

This is some very odd behavior with Samba, I think we have a bug... My set up is: Samba is running as a PDC / Domain Logins. OpenSLP 1.2.1 OpenLDAP 2.4.7 Samba 3.0.28 nss_ldap CUPS 1.3.5 Using the smbldap-useradd scripts that come with Samba! I don't download them from PADL.com Not using PAM modules. getent passwd & getent group work fine. I can no longer join workstations

See attached samba-3.0.23/examples/pdb/test.c which actually compiles. -------------- next part -------------- /* * Test password backend for samba * Copyright (C) Jelmer Vernooij 2002 * * This program is free software; you can redistribute it and/or modify it under * the terms of the GNU General Public License as published by the Free * Software Foundation; either version 2 of the

On 06/03/16 14:12, Volker Lendecke wrote: > On Fri, Mar 04, 2016 at 04:16:44PM +0000, Rowland penny wrote: >> On 04/03/16 09:58, Volker Lendecke wrote: >>> On Fri, Mar 04, 2016 at 10:53:17AM +0100, Volker Lendecke wrote: >>>> On Wed, Mar 02, 2016 at 09:23:34AM +0000, Rowland penny wrote: >>>>> OK, here is the output: >>>> Can you try the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 31 Jan 2003, Robert M. Martel wrote: > I've followed the steps as listed in the manual. Log onto a > windows 2000 client as a user listed as a printer admin. Load the > printer driver and make the changes to reflect installed options on the > printer. Just as listed in section 6.2.2 of the "how-to" manual >

Our computers in our office ceased being able to print to a shared cups printer today. Could not find the cause. Seems the smbd processes are dying. Below is the stack trace produced by gdb bt full. The Samba 'panic action' script, /usr/share/samba/panic-action, was called for pid 5839 (/usr/opt/samba-3.0.2rc2/sbin/smbd). 0x40150a59 in wait4 () from /lib/libc.so.6 #0 0x40150a59 in

Hi, I've a problem, with a cpu load (>66% while running a separate virusscanner with another 30%) of one of my smbd processes. It only happens occasionally (approx. 2 times in the last 4 weeks). The backtrace is attached. It seems to me, that smbd is looking for colorlaser5quota. This printer isn't attached anymore to the server and neither cups nor samba configuration files include a

On Fri, Mar 04, 2016 at 04:16:44PM +0000, Rowland penny wrote: > On 04/03/16 09:58, Volker Lendecke wrote: > >On Fri, Mar 04, 2016 at 10:53:17AM +0100, Volker Lendecke wrote: > >>On Wed, Mar 02, 2016 at 09:23:34AM +0000, Rowland penny wrote: > >>>OK, here is the output: > >>Can you try the attached (UNTESTED!) patch? > >> > >>Thanks, >

share in the samba box, from the PDC server itself. The log.winbindd and log.nmbd are empty. [2001/08/08 13:11:28, 3] smbd/reply.c:reply_sesssetup_and_X(865) Domain=[EERDBR001] NativeOS=[Windows NT 1381] NativeLanMan=[] [2001/08/08 13:11:28, 3] smbd/reply.c:reply_sesssetup_and_X(876) sesssetupX:name=[administrator] [2001/08/08 13:11:28, 3] libsmb/namequery.c:resolve_lmhosts(733)

and that access to the client should be denied. > James > > ----- Original Message ----- > From: "Alexander Lobodzinski" <lobo@mental.com> > To: <samba@lists.samba.org> > Sent: Monday, August 20, 2001 10:17 AM > Subject: Can I have only certain users log in to a Samba DC client? > > > > A machine should be member of a domain controlled by

<-----------------------------------------------------------------------> Changes to user passwords are captured by a special DLL, which traps and then stores the password changes in encrypted form in a private area. On each synchronization schedule, the synchronization service first examines the SAM file for changes, and then checks this private area for passwords to be synchronized. Once