similar to: user password expiration patch (Samba 2.2.4/2.2.5 PDC with LDAP)

Hi, As I said yesterday, I worked on a solution for tdb format in order to manage easily new fields for this format. So I add small changes to init_sam_from_buffer and init_buffer_from_sam in this purpose. The data TDB_FORMAT_STRING became an array which contains the list of the different fields format which exist. When the tdb file is read, for each records, Samba will try the most recent

Hello, I hope this is the correct place for this mail... I have found that samba-2.2.3a (--with-ldapsam) gives the correct logon home for win2k, but not for win98. Obviously the two systems request the information in a different way. For win98 machines, in lanman.c, the information is taken only from smb.conf, and not from ldap (or other backends). I have attached a small patch that yields

Okay - I've got samba working as a PDC with and ldap backend. I want to have some users not be in ldap (like the built in stuff like cyrus, mail, lp etc) I can get that to work with the pam_ldap and pam_unix but pam_smbpass doesn't seem to return user_unknown as i expect for users who are not in the ldap database does this make sense? --- pam_smb_passwd.c 12 Feb 2002 15:56:19

This is using samba-3.0.2a, as downloaded from us2.samba.org today (19th of April), on Debian Linux. I have setup and gotten mostly-working the MySQL PDB for Samba. It queries the database correctly, pulls in the data, etc. However, when I connect as a user, I get: [2004/04/19 15:56:23, 3] libsmb/ntlm_check.c:ntlm_password_check(182) ntlm_password_check: NO NT password stored for user

Dear List, we have several server installations in local schools serving files with samba. The users are stored within an ldap database. We then tried to set the smabaPwdCanChange time somewhere in the future, but had to see, that samba didn't honored the given value. I then got the source, looked at the logs with an high log level and searched my way though it to two important functions,

On 31.05.19 18:47, Jeremy Allison wrote: > On Fri, May 31, 2019 at 06:32:56PM +0200, Andreas Reichel via samba wrote: >> Dear samba team, >> >> I have a lot of hobby projects including old PCs. I wanted to hook up a Win3.11 machine to my current >> Arch-Linux Workstation running samba 4.9.4. >> >> I have used the following configuration: >> >>

On Fri, May 31, 2019 at 06:32:56PM +0200, Andreas Reichel via samba wrote: > Dear samba team, > > I have a lot of hobby projects including old PCs. I wanted to hook up a Win3.11 machine to my current > Arch-Linux Workstation running samba 4.9.4. > > I have used the following configuration: > > [global] > workgroup = HOMEBASE > netbios name = Orcane > wins

On Fri, May 31, 2019 at 07:09:44PM +0200, Andreas Reichel wrote: > > > > > > > When adding me as the user with 'smbpasswd -a andreas', and entering a password, > > > no LANMAN hash is generated. The generated smbpasswd entry always contains 32 X as the first hash. > > > > > > When I do the same with Samba 4.3.11-Ubuntu, the hash IS

On Fri, 2019-05-31 at 22:33 +0200, Andreas Reichel via samba wrote: > On 31.05.19 22:07, Andrew Bartlett wrote: > > On Fri, 2019-05-31 at 11:40 -0700, Jeremy Allison via samba wrote: > > > On Fri, May 31, 2019 at 07:09:44PM +0200, Andreas Reichel wrote: > > > > > > When adding me as the user with 'smbpasswd -a andreas', and entering a password, > >

Hi, If anyone is interested, the included patch to rsync-2.6.2 allows you to specify the port number for an rsync server as a global option in rsyncd.conf with 'port = <N>' (where <N> is your favorite port number). Note that this parameter only takes effect when the server is started, not when clients connect. Also, specifying the port in rsyncd.conf takes precedence

Hi folks, Just yesterday, my Samba installation on OpenSlug suddenly stopped working, out of the blue. Now, users on my WinXP SP2 systems cannot under any circumstances log in to the domain. Local Windows users however can map shares with no problem. When a domain user attempts to log on to a domain member PC (joining the domain works fine, by the way), they are denied with the generic Windows

Hi everyone, I'd like to propose a patch for review. It enhances rsync when patched and compiled with slp support. It adds a new global boolean option, 'disable slp', which can be used to disable SLP advertisements at runtime. The idea behind this patch is to allow distributors to build rsync with SLP support compiled in, but to allow the users to turn it off without recompiling

winbind primary group = 213478 winbind force primary = no // this is the default, but I just wanted to be explicit Stephen A Jazdzewski Steve@Jazd.com <<samba-2.2.4-forceprimarygrouprid.patch>> ------_=_NextPart_000_01C1FC4A.A7164AC0 Content-Type: application/octet-stream; name="samba-2.2.4-forceprimarygrouprid.patch" Content-Transfer-Encoding: quoted-printable

On Fri, 2019-05-31 at 11:40 -0700, Jeremy Allison via samba wrote: > On Fri, May 31, 2019 at 07:09:44PM +0200, Andreas Reichel wrote: > > > > When adding me as the user with 'smbpasswd -a andreas', and entering a password, > > > > no LANMAN hash is generated. The generated smbpasswd entry always contains 32 X as the first hash. > > > > > > >

I have a Macintosh Xserve running OS 10.4.8 and it's running Samba 3.0.10. Everytime a Windows XP workstation logs off the Macintosh Xserve server, the following shows up in the log.smbd (located at var/log/samba): [2007/01/11 14:24:17, 0] pdb_ods.c:make_a_mod(2045) make_a_mod: INVALID VALUE!!! [2007/01/11 14:24:17, 0] pdb_ods.c:make_a_mod(2045) make_a_mod: INVALID VALUE!!! [2007/01/11

I have recompiled pdbedit 3.0.2 with -g flag to be able to list sources from gdb when debugging pdbedit and discovered some more info but don't know how to interpret it: (gdb) frame 1 #1 0x0806c899 in init_sam_from_buffer (sampass=0x81b8c28, buf=0x81b8d78 "", buflen=208) at passdb/passdb.c:1462 1462 SAFE_FREE(domain); (gdb) print domain $8 = 0x10000 <Address

On 17/02/17 07:58, Andrew Bartlett via samba wrote: > On Fri, 2017-02-17 at 07:48 +1100, Tom Robinson via samba wrote: >> Anyone? > Can you please post a gdb backtrace --full? > > Hi, I replied last week with a full backtrace but I didn't see my post come through. The email was only 266KB. Is the list server or SPAM filter blocking my previous message? In attempt to

Hi, Not sure if I should post in samba-technical or just samba list. Please advise. Back in February I was trying to do a samba-tool classicupgrade but kept getting SIGSEGV: https://lists.samba.org/archive/samba/2017-February/206409.html I didn't progress much after that. This week I've compiled samba-4.6.5 and installed that. Following the HOW-TO for classic upgrade

On 31.05.19 22:07, Andrew Bartlett wrote: > On Fri, 2019-05-31 at 11:40 -0700, Jeremy Allison via samba wrote: >> On Fri, May 31, 2019 at 07:09:44PM +0200, Andreas Reichel wrote: >>>>> When adding me as the user with 'smbpasswd -a andreas', and entering a password, >>>>> no LANMAN hash is generated. The generated smbpasswd entry always contains 32 X

In the bufferbloat age, anything that can make for a kinder, gentler bulk transfer protocol seems desirable. This add support for user and server selectable congestion control algorithms. As examples: --congestion-alg=lp # For the tcp-lp algorithm on the command line Or in a subsection: [mystuff] congestion alg = westwood # for a wireless connection And diffserv support: --diffserv=8 for