similar to: logon home with ldap under win98

Hello, A few months ago the distribution I use (Debian Testing) moved from Samba 3 to Samba 4 - I started seeing a lot of problems. Since then there are two bugs I find occurring on a regular basis: 1. Consistent dumping core on a regular basis (very rarely, if ever occurred with Samba 3) a. $ ls -ltr *core*smbd* |wc -l b. 1297 c. $ du -ach *core*smbd*|tail -n 1

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

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

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

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,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tom, Try this patch. I lost your original message but this should fix the problem with 'logon path = \\%L\profile\%U\%a' confusing WinXP with Win2K. cheers, jerry ---------------------------------------------------------------------- Hewlett-Packard ------------------------- http://www.hp.com SAMBA Team

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 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

I plan to use samba to substitute two NT4 server (PDC/BDC) howewer I am not sure if it would fit: I have not been able to find either in the samba 3.0 and samba-tng documentation the following informations: 1. Can I have three different serever on which putting the home directories of the users (of course this would be set in their profiles) ? logon_home parameter seem to forbide this ... 2.

We have a linux pc (slackware 4.0, samba 2.0.5) acting as a gateway between two subnet of our office. On my side of the net I have a mixed win95/NT/Samba network, and on the other side we have some sco unix servers, running an old lan-manager, os/2 like. Gateway linux is a master browser, that enable us to see the other subnet, but... I can't see the record for the sco-server in

We have small panic here as we've just put samba 3.0.8 up to fix the DoS attack but all printing from Windows 98 has now broken. Printing from Windows XP is still working fine. We're running on Fedora 2 using LPRng. Everything was working fine under 3.0.7 and no changes to the OS or the config files was made. Samba was upgraded to 3.0.8 using the configure line from the 3.0.7

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. > > > > > > >

My systems: rh61, 2.2.14 + smbfs-nls.patch. === 1) Samba seems to override unix permissions in a particular case. I get the very same behavior of: http://us1.samba.org/listproc/samba-technical/February2000/0476.html === 2) browsing behavior: anonymous login There is a different behavior doing smbclient -L -U% if the server is samba or nt/w2k nt wants a correct user/pass pair if guest account

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 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

Hi there, is there any possibility of disabling Samba's version number output (e.g. with smbclient) without having to manually edit it in the source code? I don't want anyone to see my Samba's version number... Thanks Florian