similar to: samba panic

On Sun, 17 Mar 2024 11:36:51 +0100 Steffen Dettmer <steffen.dettmer+samba at gmail.com> wrote: > On Sat, Mar 16, 2024 at 9:45?PM Rowland Penny via samba wrote: > > On Sat, 16 Mar 2024 21:33:59 +0100 Steffen Dettmer via samba wrote: > > > getent passwd 'DMYDOM\a-sdettmer' > > > [nothing] > > Have you installed libpam-winbind & libnss-winbind

On Sat, Mar 16, 2024 at 9:45?PM Rowland Penny via samba wrote: > On Sat, 16 Mar 2024 21:33:59 +0100 Steffen Dettmer via samba wrote: > > getent passwd 'DMYDOM\a-sdettmer' > > [nothing] > Have you installed libpam-winbind & libnss-winbind ? Thank you for your quick response again! Yes, I have libpam-winbind and libnss-winbind. I just today noticed (due to a

Wow, thank you so much for your instant reply! I added it and executed "smbcontrol all reload-config", but the message keeps appearing. Should I kill and disable nmbd? I see such a process running. Steffen root at nas1:/var/log/samba# systemctl status nmbd.service ? nmbd.service - Samba NMB Daemon Loaded: loaded (/lib/systemd/system/nmbd.service; enabled; preset: enabled)

Hi, I had issues using"vfs objects = acl_xattr" (possibly too old version [Version 4.13.13-Debian] for the needed "acl_xattr:security_acl_name = user.samba" option needed if running in a non-priv container). So I tried "vfs objects = acl_tdb" and found it working. In https://wiki.samba.org/index.php/File_System_Support I found: File systems without xattr support

On Sat, 16 Mar 2024 15:19:54 +0100 Steffen Dettmer via samba <samba at lists.samba.org> wrote: > Hi, > > I setup a new samba file server (in a priviledged Proxmox container > using the Debian 12 template) and apparently it works fine. > > In log I see every 10 seconds: > > write_browse_list: Fatal error - cannot find my workgroup DMYDOM > > Google found

Hi, I read several articles on the internet, but I fail to understand how ACL storage technically works. Of course in almost any case, ACL should not only be stored but also evaluated, and for this this Samba server needs to be a member of the AD domain. I think I understand this, but I have a different use case. I hope someone can help and possibly has a link or such. I have a samba instance

Hi, we are using Samba 3 ( CVS checkout from 09/01 ) on a SuSE 8.2 box with all patches applied. The passdb backend is LDAP / eDirectory 8.7 on another machine. The Samba box is supposed to work as a stand alone domain controller, so I am testing to join a client machine to it's domain. This is my "add machine script": /usr/bin/cpu useradd %u -d /dev/null -f

On Sat, 16 Mar 2024 21:33:59 +0100 Steffen Dettmer via samba <samba at lists.samba.org> wrote: > Hi, > > after I setup one working Samba today, I tried to do exactly the same > in another domain. > I created a privileged debian12 container and installed samba. > I have a MS Win driven AD (3 DCs). First I had not all in upper case > in krb.conf. I learnt uppercase is

Hi all, yesterday i switched from Samba 3.0.5 to 3.0.6 RC2 because we want to upgrade our Windows XP clients to SP2 which seems to cause printing problems with all older versions of Samba. Unfortunately this reintroduced a problem regarding DOS ( please see http://lists.samba.org/archive/samba/2004-July/089609.html ) which i already had experienced when i switched from Samba 3.0.4 to

Hi, I setup a new samba file server (in a priviledged Proxmox container using the Debian 12 template) and apparently it works fine. In log I see every 10 seconds: write_browse_list: Fatal error - cannot find my workgroup DMYDOM Google found one hint telling it should set "network = ip", but man page does not explain such an option. Another hint suggests it could be related to an

Hi, after I setup one working Samba today, I tried to do exactly the same in another domain. I created a privileged debian12 container and installed samba. I have a MS Win driven AD (3 DCs). First I had not all in upper case in krb.conf. I learnt uppercase is needed and fixed it. To go sure I left domain, killed the container and started again from scratch (hope nothing is stored anywhere). I

guys need help my samba was working fine for about 1 month then it stoped working and now i get this error log [2004/07/29 13:36:53, 5] lib/charcnv.c:charset_name(74) Substituting charset 'ISO-8859-1' for LOCALE [2004/07/29 13:36:53, 5] lib/charcnv.c:charset_name(74) Substituting charset 'ISO-8859-1' for LOCALE [2004/07/29 13:36:53, 5] lib/charcnv.c:charset_name(74)

Hi. I have some trouble with my samba domain controller. Every time I try to logout my windows workstation, I get an error that the share is no longer availible. I estimate that this happens around the time when windows tries to copy my user profile back to the server. (because when I change profile type to local the error no longer occurs) on the samba side the following error is logged.

Hello, I'm trying to add a user to big list of Samba groups, 74 groups to be precise. The problem is that when the user reaches around 65 to 70 groups, it starts giving errors in User Manager for Domains, and causes a panic in Samba. Is there a limit for how many groups a user may belong? I'm using Samba-3.0.10 with openldap. This is what I get in the logs. [2005/02/07 13:22:42, 0]

On Sat, 16 Mar 2024 16:53:04 +0100 Steffen Dettmer <steffen.dettmer+samba at gmail.com> wrote: > Wow, thank you so much for your instant reply! > > I added it and executed "smbcontrol all reload-config", but the > message keeps appearing. > Should I kill and disable nmbd? I see such a process running. > > Steffen > > root at nas1:/var/log/samba#

I have moved a Samba installation from an old samba 2.2.8a (on a 2.4.21 kernel) to a new server running Samba 3.0.10 on a SuSE 9.2 (kernel 2.6.8) and I now have a problem using the (same) shares from client W2K machines. When I open "My Computer" window on a client, the drives are marked by a red cross, as if they were disconnected, and the disksize is zero. I can decend into the

Wlcome in the club :-) I wrote a topic "Limit of group membership for a user?" with the same problem, and I don't have any answer by the samba team. I have the most recent Samba 3.0.21b, OpenLDAP 2.2.28 and Glibc 2.3.6 version on a Gentoo (kernel 2.6.15) and I have the same problem. I check the NGROUP_MAX (65535) and the NSS_BUFLEN_GROUP (2048) value of the glibc. For the AMD64

Hi All, I had been doing some testing with the Debian 3.0.4-x versions of samba. On two sepearte systems, running different configs, I've found that smbd panics unless the [printers] section is removed from smb.conf. Errors generated as follows... (System #1) Server role: ROLE_DOMAIN_MEMBER Smb.conf... [Global] security = DOMAIN printcap name = cups printing = cups [printers]

Hi folks, I have updated samba to 3.0.20, on SLES9. I had a configuration earlier, where SLES9 was a domain member 2003 Server (samba 3.0.14a), everything used to work well earlier. After updating.. I rejoined it to AD there was no errors. However, Clients from windows were unable to access the shares. #>getent passwd [2005/08/22 15:41:41, 0] lib/fault.c:fault_report(36)

Hi All, I hope someone can help me with this problem. I recently moved my Windows Print server to Linux (Red Hat 9.0, Samba 3.0.2) due to stability problems, however since i had a constant smbd panics I reverted back to my Windows 2000 server much to the disappointment of my manager and director. Having posted to this list someone suggested an upgrade to 3.0.3pre2 which solved their issues, I