similar to: Upgraded > Samba no longer listening on 192.168.0.x

On Sun, 18 Jun 2017 02:55:22 -0700 (PDT) Winfried via samba <samba at lists.samba.org> wrote: > Forgot to give the smb.conf: > OK, it looks like you are trying to set up a standalone server with guest access, I suggest you read this wiki page: https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Standalone_Server You do not need most of the parameters you have added to smb.conf,

Here goes: root at debian:~# cat /etc/init.d/samba #!/bin/sh ### BEGIN INIT INFO # Provides: samba # Required-Start: # Required-Stop: # Default-Start: # Default-Stop: # Short-Description: ensure Samba daemons are started (nmbd and smbd) ### END INIT INFO set -e # start nmbd, smbd and samba-ad-dc unconditionally # the init scripts themselves check if they are needed or not case $1 in

that init script is ok. Try adding the following in your smb.conf Add : interfaces = 192.168.249.230 127.0.0.1 Or interfaces = eth0 lo ( change eth0 to your interface name) Check: systemctl status samba systemctl status samba-ad-dc If samba-ad-dc is enable, disable that one, and enable samba. systemctl disable samba-ad-dc systemctl enable samba Greetz, Louis >

Hello, Probably problem is numer 3... see below.... All of them are running after restart of computer: # /etc/init.d/samba-ad-dc status ● samba-ad-dc.service - LSB: start Samba daemons for the AD DC Loaded: loaded (/etc/init.d/samba-ad-dc) Active: active (running) since Son 2015-10-04 23:14:36 CEST; 18h ago # /etc/init.d/samba status ● samba-ad-dc.service - LSB: start Samba daemons for

On 02/04/16 20:59, Sonic wrote: > On Sat, Apr 2, 2016 at 2:34 PM, Rowland penny <rpenny at samba.org> wrote: >> On debian there is a script called samba in /etc/init.d , it starts smbd & >> nmbd *or* samba, if it doesn't find 'server role = active directory domain >> controller' in smb.conf , it doesn't try to start the samba deamon. > Odd that

Hi again, I refer to https://wiki.samba.org/index.php/Setup_a_Samba_Active_Directory_Domain_Controller#Testing_your_Samba_Domain_Controller Thank you for this great wiki! I run all the tests and everything looks perfect! I encounter just a little difference here. Actually I thought that there should be no Master and Workgroup for a AD DC. (as given in the wiki and in Stefan Kania's book

Am 19.06.2017 um 11:42 schrieb Winfried via samba: > ### BEGIN INIT INFO > # Provides: samba > # Required-Start: > # Required-Stop: > # Default-Start: > # Default-Stop: > # Short-Description: ensure Samba daemons are started (nmbd and smbd) > ### END INIT INFO well, there is no ordering with network services most likely your samba starts before the network is

So it looks like the init script in the Samba package in the Debian repository needs to be edited for a non-DC home server. -- View this message in context: http://samba.2283325.n4.nabble.com/4-2-14-Debian-Smbd-not-listening-on-192-168-0-x-on-cold-start-tp4720131p4720160.html Sent from the Samba - General mailing list archive at Nabble.com.

Hello, I noticed a problem when cold-starting a Debian host: smbd doesn't listen on 192.168.0.x. I need to restart it through the Initd script: Cold start: ======== root at debian:~# netstat -tunlp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:445 0.0.0.0:*

Hai, There is nothing wrong with the debian script. If it does not work, ( like this one ), failing to start at boot time. The make the change i suggested, one of these 2 wil fix it. There are few know things, these involve these settings. interfaces = 192.168.0.1 127.0.0.1 Or interfaces = eth0 lo and bind interfaces only = yes 1) smb.conf: use "bind interfaces

Thank you. After adding "interfaces = eth0 lo" to smb.conf, I ran the following commands: ================ root at debian:~# systemctl status samba ● samba.service Loaded: masked (/dev/null) Active: inactive (dead) ================ root at debian:~# systemctl status samba-ad-dc ● samba-ad-dc.service - LSB: start Samba daemons for the AD DC Loaded: loaded

Ubuntu 14.04. 2 node ctdb in an 4.1.11 AD domain with 4.1.11 member servers on each node. winbindd is present but nss and pam are controlled by sssd. All OK, except that the event script which starts samba is not working. smb.conf [global] workgroup = ALTEA realm = ALTEA.SITE security = ADS kerberos method = secrets and keytab netbios name = SMBCLUSTER clustering = Yes ctdbd socket =

Thanks for the infos. I'm running 4.2.14. I always use apt-get to install/upgrade packages, so the init script comes standard from the official repository: =============== root at debian:~# cat /etc/init.d/samba #!/bin/sh ### BEGIN INIT INFO # Provides: samba # Required-Start: # Required-Stop: # Default-Start: # Default-Stop: # Short-Description: ensure Samba daemons are started

On Sat, Apr 2, 2016 at 4:05 PM, Rowland penny <rpenny at samba.org> wrote: > I compile Samba myself and I use init files, I would rather have them than > the bloat systemd comes with. They are not complex if you understand bash > and are a lot easier to understand than all that systemd comes with. At first I felt the same way but the service files are starting to seem simpler. Yes,

chkconfig is not installed, but systemctl seems to work together with update-rc.d. 21:02:19 # systemctl disable samba Synchronizing state for samba.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d samba defaults Executing /usr/sbin/update-rc.d samba disable update-rc.d: error: samba Default-Start contains no runlevels, aborting. 21:02:58 # systemctl disable nmbd

Hi, I have a question about samba 4 with systemd. I've followed the "Managing the Samba AD DC Service Using Systemd" and I've created /etc/systemd/system/samba-ad-dc.service file with the following content: [Unit] Description=Samba Active Directory Domain Controller After=network.target remote-fs.target nss-lookup.target [Service] Type=forking

On Mon, 5 Oct 2015, Rowland Penny wrote: > On 05/10/15 18:56, Birgit Berger (UV Wien) wrote: >> How do I stop scripts samba, smbd and nmbd being run at startup? > > I do not know because you are using Debian Jessie, this uses systemd which I > absolutely refuse to use! > > Perhaps somebody else can tell you how to do this and explain just how they > are all got

Hai, First he had problems with the suspend mode. See samba list subject : [Samba] Upgraded > Samba no longer listening on 192.168.0.x That got fixed, without changing any startup script, but by adding the interfaces line to smb.conf Now this one, ( sorry but winfried not attacking you, im attacting nobody ) And yes, that fix was from me to add that line, but not knowing you would hit the

Am 12.07.2016 um 21:35 schrieb Rowland penny: > On 12/07/16 20:25, Achim Gottinger wrote: >> Just backported 4.4.5 from debian sid to jessie. samba.service is >> masked there. If running as an fileserver the services are started >> via smbd.service,nmbd.service, winbind.service. >> There is an samba-ad-dc script which is masked by default. >> To get the ad-dc up

Hi Louis, I've modify my /etc/systemd/system/samba-ad-dc file following your advice, I only changed bind9.service to named.service (I've run samba on CentOS 7 with Bind9_DLZ). I've checked again if there are others smbd, nmbd, winbindd an samba services on systemd, but they there aren't. The samba-ad-dc service still to fail when I've tried stop it. I've installed samba