similar to: Can't start new version of Samba

Dear "someone who can help", I am having a problem with SAMBA and SWAT (although I'm not sure SWAT is part of the problem...) I get two instances of "smbd" when ever it is started on this system. From SWAT I can only stop it ONE time. After that, each time I attempt to stop the SMBD daemon from SWAT it simply starts TWO more instances of the daemon (or something

Hi Rowland, Same, as said; winbind isn't started :-) [root at dmzrodc ~]# ps ax | egrep "ntp|bind|named|samba|?mbd" 650 ? Ss 0:00 /usr/sbin/ntpd -u ntp:ntp -g 1205 ? Ss 0:00 /usr/sbin/samba -D 1225 ? S 0:00 /usr/sbin/samba -D 1226 ? S 0:00 /usr/sbin/samba -D 1227 ? S 0:00 /usr/sbin/samba -D 1228 ? S 0:00 /usr/sbin/samba -D 1229 ? S 0:00 /usr/sbin/samba -D 1230 ? S 0:00

Hi Louis, Hi Rowland, I will respond to both in this mail. Yes winbind is installed : [root at dmzrodc ~]# which winbindd /usr/sbin/winbindd [root at dmzrodc ~]# rpm -qa |grep winbind sernet-samba-winbind-4.8.2-10.el7.x86_64 I know about *mbd processes. so strange.. This is why I'm posting here :-) I joined the RODC following the procedure available on the wiki page

 If its really urgent then u would really suggest, invest in samba a bit and pay them to get this working. Thats what sernet can do for you. Get commercial support.   Im pretty much out of options, execpt upgrade to 4.8 and try it again.     Greetz,   Louis     Van: Gaetan SLONGO [mailto:gslongo at it-optics.com] Verzonden: woensdag 13 juni 2018 10:40 Aan: Rowland Penny; L.P.H. van Belle

On Wed, 13 Jun 2018 09:46:03 +0200 (CEST) Gaetan SLONGO <gslongo at it-optics.com> wrote: > Hi, > > Here is the current process list. We can see missing winbind and *mbd > processes : > > > > [root at dmzrodc ~]# netstat -plaunt | egrep "ntp|bind|named|samba|?mbd" I wouldn't worry about 'winbind' not being in the output of the above

On 16/11/2019 18:47, William Lugg via samba wrote: > OK, here's the result of ps ax: > > ?1324 ???????? Ss???? 0:00 /usr/sbin/nmbd --foreground --no-process-group > ?1348 ???????? Ss???? 0:00 /usr/sbin/smbd --foreground --no-process-group > ?1351 ???????? S????? 0:00 /usr/sbin/smbd --foreground --no-process-group > ?1352 ???????? S????? 0:00 /usr/sbin/smbd --foreground

OK, here's the result of ps ax: ?1324 ???????? Ss???? 0:00 /usr/sbin/nmbd --foreground --no-process-group ?1348 ???????? Ss???? 0:00 /usr/sbin/smbd --foreground --no-process-group ?1351 ???????? S????? 0:00 /usr/sbin/smbd --foreground --no-process-group ?1352 ???????? S????? 0:00 /usr/sbin/smbd --foreground --no-process-group ?1353 ???????? S????? 0:00 /usr/sbin/smbd --foreground

Hi, Not sure sernet can help. It really looks like a samba issue to me..? Just found this in logs when starting the RODC : [2018/06/13 10:59:11.546077, 3, pid=12673, effective(0, 0), real(0, 0)] ../lib/util/util_runcmd.c:291(samba_runcmd_io_handler) samba_runcmd_io_handler: Child /usr/sbin/winbindd exited 1 [2018/06/13 10:59:11.546131, 0, pid=12673, effective(0, 0), real(0, 0)]

On Wed, 13 Jun 2018 10:05:23 +0200 (CEST) Gaetan SLONGO <gslongo at it-optics.com> wrote: > Hi Rowland, > > > Same, as said; winbind isn't started :-) > > > > [root at dmzrodc ~]# ps ax | egrep "ntp|bind|named|samba|?mbd" > 650 ? Ss 0:00 /usr/sbin/ntpd -u ntp:ntp -g > 1205 ? Ss 0:00 /usr/sbin/samba -D > 1225 ? S 0:00 /usr/sbin/samba

I get the same problem and have struggled on this for 4 days. My Linux box has RH8.0 on it and is networked with a Windows 98 PC What I have done: (1) Follow the instructions on "The Official Red Hat Linux Customization Guide" and config smb.conf (2) Run the test in DIAGNOSIS.txt, failed in step 5. (3) Step 7 is OK, which means local smb client can connect to smbd service and

On 16/11/2019 16:07, William Lugg via samba wrote: > Yes, I created the unix user and a Samba user as instructed in the Wiki. > > According to the package manager, my Samba version is 4.7.6. Would you > say upgrading is still in order? This is better than what I thought you would be running, but it is still EOL as far as Samba is concerned, but it should work ;-) > > The test I

I decided to use S99samba in /etc/rc2.d, during the boot up i see the message "samba started" or something like that but when i log in and do "ps -ef|grep mbd" i do not see neither smbd nor nmbd running. PC side gives me the error "computer not found" message. I move the S99samba to /etc/rc3.d and see no messages during the boot up. "ps ..." output is same

James, I have sent this to you directly and cc:ed the list for reasons that should become apparent below. THE SITUATION OS: mdk 7.2, 2.2.19 kernel - basically bone stock Latest addtions: samba 3.0.7-1 compiled from source (working fine); cups-1.1.18-1 from mdk rpm Reasons for additions: XP SP2 fun and games THE MYSTERY As any normal person does, I use

On Thu, 31 May 2018 15:37:20 +0200 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > Hai, > > Yes, but with or without internal dns server, the command is missing > ports. > > netstat -plaunt | egrep "ntp|bind|named|samba|?mbd" > > And do note here that i used the "bind" for bind and winBIND > detection. >

Hi 2 all ! I want to implement a new option into version 2.11 of syslinux: The feature should do the following: Ask the user if he really wants to boot from dvd. If no keyboard key is pressed in an amount of time it should boot from the next device configured in BIOS (INT 18h). I looked up the isolinux.asm and tried 2 entry points for my code: 1. entry point: label

Hello With smb.conf below, samba 3.0.1pre3 is capable of connecting to itself by smbclient -L oberon <empty_password>. Also domain logons work. With 3.0.1rc1 it just writes bash-2.05b# smbclient -L oberon Password:<empty> tree connect failed: Call returned zero bytes (EOF) bash-2.05b# smbclient --version Version 3.0.1rc1 bash-2.05b# smbd --version Version 3.0.1rc1 bash-2.05b# which

Hi, As it has been brought to my attention (by several parties), my current MB does not support VT-d. Since I don''t feel like purchasing a brand new system, I have searched for replacement MB-s that would fit into my existing uATX case, support my C2D CPU, and support at least 4x2GB ram. I have narrowed it down to the following four models: SUPERMICRO MBD-C2SBM-Q-O (Q35 chipset)

Hi, Since today I can't start virt-manager anymore :-( Failed to connect to socket /tmp/dbus-yhDz4m8loi By the way the same message as I get from qdbus. There are no files called /tmp/dbus* on my system but some dbus applications are running: linux-dev:~# ps ax | grep dbus 1774 ? Ss 0:00 /usr/bin/dbus-daemon --system 2436 ? S 0:00 dbus-launch --autolaunch

Hi again, I'm hoping this will make it to the list. I'm still puzzled by the behavior of the smb daemon. Jerry Carter's book and talk at the recent Linux World Expo state that after starting nmbd and smbd with e.g. "smbd -D ; nmbd -D" that a "ps -ef | grep mbd" should return the PIDs of both smbd and nmbd. I have downloaded and installed both a rpm

I run samba ( ver 3.0.26a ) on a linux box ( Fedora 4 ) so that users from a Windows 2003 domain can access those files on the linux box. I compiled the samba and configured it with the command : configure --with-ads The /usr/local/samba/lib/smb.conf is : -------------------------------------- [global] domain master = no local master = no preferred master = no