similar to: [4.2.14-Debian] Smbd not listening on 192.168.0.x on cold start

try changing the interface names, (lo and eth0) to there ipadresses. if that didnt fix it, then you need to adjust the startup order. (in systemd) Greetz, Louis > Op 18 jun. 2017 om 12:12 heeft Winfried via samba <samba at lists.samba.org> het volgende geschreven: > > Forgot to give the smb.conf: > > ========== > root at debian:~# cat /etc/samba/smb.conf >

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

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,

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

Hai, Really, you dont need to edit the systemd files. Try first with only the interface change. Then if you still need to edit the systemd files. You need these settings, but i dont thing you need it after the interface change. cat /lib/systemd/system/smbd.service [Unit] Description=Samba SMB Daemon Documentation=man:smbd(8) man:samba(7) man:smb.conf(5) After=network.target nmbd.service

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

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

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.

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 I'm running Samba 3.6.6 on a Linux host on a LAN connected to the Net, with my ADSL modem acting as firewall/router so as to keep local services like Samba unaccessible from the Net. Still, I wanted to check if it's safe to have nmbd reachable from 0.0.0.0 on UDP137/138: ~# netstat -tunlp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address

On Sun, 9 Jul 2017 03:24:16 -0700 (PDT) Winfried via samba <samba at lists.samba.org> wrote: > Hello > > I'm running Samba 3.6.6 on a Linux host on a LAN connected to the > Net, with my ADSL modem acting as firewall/router so as to keep local > services like Samba unaccessible from the Net. > > Still, I wanted to check if it's safe to have nmbd reachable from

Hello I've two strange problems: - smbd I've attached you my smb.conf, inetd.conf and my log file. Sometimes smbd and nmbd run and somtimes only nmbd run (I check it with ps -ax). But I have access over my shares (I test it with my Win95 machine). Also in my log file there're some error messages (I don't now from where the came). - login scripts My scripts won't run but if

netstat -lptu gives me tcp6 0 0 [::]:16514 [::]:* LISTEN 1314/libvirtd so the server is correctly listening on interfaces. My /etc/libvirt/libvirtd settings are defaulted. My /etc/default/libvirt-bin has "-d -l" options so server is listening. If I do virsh -c qemu://143.225.229.190/system (that is my ip or an ip belonging to my network) I

I?ve held off reporting this since I thought it might just be some kind of fluke, but I?ve seen it now on three different boxes. The symptom is that the stock configuration of Apache only listens for IPv6 connections: $ netstat -na | grep :80.*LISTEN tcp6 0 0 :::80 :::* LISTEN You should see a second line there for IPv4, but you don't:

Hi all, I'm maintaining a small AD system on a computer called "ad" in our small charity, and it has been working fine for a year or so. However, "ad" is very rickety so we got a proper server purchased and now I'm trying to move the AD system over.  I've set up the new server called "org-ad" with Debian 9 and followed the instructions here

Hello all, I'll cut to the chase -- several weeks ago, I thought I had an upstart configuration file that would start Samba4 when the VM was turned on; but it turns out I was wrong. At the time there was nothing on the wiki about it (the links were broken). The script I thought was working was simply: start on runlevel [2345] exec /usr/local/samba/sbin/samba In any case, looking at the

Dear Rowland, Indeed. Guess my KMail client is playing with me. I disabled HTML formatting. Here is the info again: /etc/hostname: lotus /etc/hosts: 127.0.0.1 localhost 192.168.1.254 lotus.intra.dam-application.ro lotus /etc/resolv.conf: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE

On OpenBSD 2.8 when i start rsync with: # rsync --daemon the daemon doesn't bind to the ipv4 tcp port instead it only listens to the ipv6 port. The daemon works properly using the same argument on linux. Any help would be greatly appreciated. # netstat -la Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp 0

Another strange thing. I tried, in order to solve this, to put my hostname as listening address. I started with the ip, 192.168.2.2, and it works. I then decided to use the domain name, pasquale-Dell, but the socket is not created. Looking into logs it seems it tries to resolve the name, without success. After a lot of tries it just decides to give up. However, in file /etc/hosts the resolution is