similar to: Samba, 20.000 users and concurrent logons: part 2

Hi! My Samba setup broke after upgrading Samba from 3.0.5-1 to 3.0.6-3 using Debian apt-get upgrade. It seems to me, that the problems lies within winbind. Any help would be appreciated! -- Pirkka > The Samba 'panic action' script, /usr/share/samba/panic-action, > was called for pid 8012 (/usr/sbin/smbd). > > Below is a backtrace for this process generated with gdb, which

At 15:58 00-04-17, you wrote: >Date: Mon, 17 Apr 2000 14:45:07 +0200 >From: werner maes <werner.maes@cc.kuleuven.ac.be> >To: samba@samba.org >Subject: SMBD-error: important?? >Message-ID: <38FB0753.B00F2E49@cc.kuleuven.ac.be> >MIME-Version: 1.0 >Content-Type: text/plain; charset=us-ascii >Content-Transfer-Encoding: 7bit > >Hello, > >When I

Hello, I have defined 20.000 users on a Samba-server. The samba-server takes care of domain logons. When several users try to authenticate at THE SAME time the server can't follow: only the first users can succesfully logon. When they don't logon simultaneously there's no problem. For example: 20 users log on at exactly the same time. This situation occurs in our pc-rooms when

Hello from a neophyte! Is there a diagnostic programme which can be run to determine if there are any faults in Samba 2.2.3a? I cannot connect from Win XP to my rev/b iMac (suddenly, maybe 'upgrade' to 10.3.4 had some effect) and the smb crashlog (shown below) has a pile of stuff which is incomprehensible to me. Secondly, how does one upgrade to another version of Samba and is this

Hi - I am trying to compile and install 2.2.8 to /opt/samba, but I keep getting the following errors after I 'make install' and try to start smbd using '/opt/samba/sbin/smbd -d 2 -D -s /opt/samba/lib/smb.conf': Unable to open new log file /usr/local/samba/var/log.smbd: No such file or directory [2003/03/25 10:21:56, 0] lib/debug.c:reopen_logs(348) Unable to open new log file

Hi, Having reset-up a print server from installation disks today, I did something stupid and blindly copied the contents of /etc/samba from the previous installation into the new installation. Now smbd refuses to start (nmbd starts OK). I am currently using a blank smb.conf file and the smb.conf file from the old installation. testparm doesn't report any errors in the smb.conf from the old

On Mon, 2023-08-28 at 23:46 +0200, Peter Koch via samba wrote: > Hi Andrew and Roland, > > I spent some hours today to debug the problem by > adding lots of printf-statements into the samba4 > source. > > Here are my findings: > - upgrade.py calls passdb.get_global_sam_sid() > - get_global_sam_sid() calls pdb_generate_sam_sid() > - pdb_generate_sam_sid() calls

Hi, I have installed the public domain version of samba version 2.2.8a on aix 5.2 and I receive the following error message while attempting to start the samba server. I am wondering if anyone could help me. Thanks in advance. [2003/11/19 11:52:21, 0] smbd/server.c:main(791) smbd version 2.2.8a started. Copyright Andrew Tridgell and the Samba Team 1992-2002 [2003/11/19 11:52:21, 0]

Hi all.. Happy holidays! I am having trouble all of the sudden with samba. I was running an older version and I suddenly couldn't connect the mapped drives this morning (yesterday it worked fine) so I downloaded the lastest samba and compiled and installed it. Now when I try to connect to a public share windows keeps asking me for a password. Also, if I use "smbclient -L

Hello I cannot get my Windows98 machines to connect to my Samba server(2.2.4) shares. It appears that my Win machines are not transmitting the password. The Samba server looks OK. On the server machine, "smbclient -L <server> -U user1" prompts me for a passwd, then, after authentication, displays the shares. When I attempt to map a share from my Win machines, the samba log file

Hi I hope I've posted this to the correct place. I've installed Samba 2.2.4 on a Caldera Open Unix 8 server, and created a basic smbd.conf file. When I launch smbd as a daemon, I'm getting the following in the log file: passdb/secrets.c: (43) failed to open /usr/lib/samba/private/secrets.tdb passdb/machine_sid.c: (163) pdb_generate_sam_sid: Failed to store generated machine SID

Hello, I have a problem with my PDC server. It runs samba + openLDAP. It used to work fine. The machine was stopped today because of a power supply failure, and since it was restarted i have problems connecting to the domain. - The ldap data was restored from a ldif file, the ldap seems to work fine. when i type ldapsearch -x I see the contents of the ldap data. - When I try : smbclient -L

Hello I cannot get my Windows98 machines to connect to my Samba server(2.2.4) shares. It appears that my Win machines are not transmitting the password. The Samba server looks OK. On the server machine, "smbclient -L <server> -U user1" prompts me for a passwd, then, after authentication, displays the shares. When I attempt to map a share from my Win machines, the samba log file

List members, I have an issue that I hope one of you can help me with ... I have set up a AD ( 2003 ) as PDC and a RHE3 AS server running Samba V3.0.6-2.3E following the instructions in the HOW-TO- By example. Here is what I have at the moment .. I had no problems adding the RH server to the Domain and I have Winbind set up in the nsswitch.conf file for passwd, group and hosts I

Dear I have connected samba 3.6.8 to my Active Directory in the lsass.exe run to 100% When stopping winbind the lsass.exe CPU is down to 0% When set winbindd to debug mode, it seems it try to scan the root user every time. I would to know how to ban nsswitch to query winbindd for system internal users such has root, apache..... Here it is my nsswitch.conf : # # Example configuration of GNU

First of all hello to everybody on this list. Question 1: I?m having a little (?) problem with winbind. To be short here is the situation: Runnign w2k AD on native mode. Linux box is Red Hat 7.2 with 2.4 kernel. Authentication from my W2K Active Directory server fails. I get following outputs with commands--> wbinfo -t --> secret is bad 0x000001 wbinfo -u --> Error looking up domain

I am using rsync 2.5.5 running as a daemon on the destination system, which is SuSE Linux 8.0. The source system is SuSE 7.3, also with rsync 2.5.5. With the default 'use chroot = true' and not using --numeric-ids, I get the wrong user names on the destination files. I have tracked this down to getpwnam() failing to return the user name from the passwd file. It does not fail when

All, I'm trying to configure a Samba 3 AD member server including winbind. I'm on RHEL 6.6, so I'm using Samba version 3.6.23. Here's my configuration: [global] log level = 3 winbind:10 workgroup = ABC server string = LV37 netbios name = LV37 idmap config *:backend = tdb idmap config *:range = 2000-9999 idmap config

Does mdecker exist in AD ? => Yes root at solaris1:~# getent passwd "MYDOM.ADS\\mdecker" mdecker:*:13767:613::/home/mdecker:/bin/bash winbind log: getpwnam MYDOM.ADS\mdecker wb_request_done[24254:GETPWNAM]: NT_STATUS_OK Does 'getent passwd mdecker' work ? => No getent passwd mdecker getpwnam mdecker winbindd_getpwnam: My domain -- rejecting getpwnam() for

Hello! I use a PAM-module (pam_ncp_auth from ncpfs) for authentication against a netware server. pam_ncp_auth can create local UNIX user accounts from information in NDS, and it works perfect with login, gdm and telnet. But not with openssh (2.5 and 2.9). It works perfect if the user already is in /etc/passwd, but the first time he logs on he doesn't exist there. In that case openssh call