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

Displaying 20 results from an estimated 4000 matches similar to: "[4.2.14-Debian] Smbd not listening on 192.168.0.x on cold start"

2017 Jun 18
2
[4.2.14-Debian] Smbd not listening on 192.168.0.x on cold start
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:*
2017 Jun 19
0
[4.2.14-Debian] Smbd not listening on 192.168.0.x on cold start
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
2017 Jun 19
4
[4.2.14-Debian] Smbd not listening on 192.168.0.x on cold start
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
2017 Jun 20
1
[4.2.14-Debian] Smbd not listening on 192.168.0.x on cold start
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
2017 Jun 19
0
[4.2.14-Debian] Smbd not listening on 192.168.0.x on cold start
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
2017 Jun 18
4
[4.2.14-Debian] Smbd not listening on 192.168.0.x on cold start
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,
2017 Jun 19
5
[4.2.14-Debian] Smbd not listening on 192.168.0.x on cold start
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.
2017 Jun 19
0
[4.2.14-Debian] Smbd not listening on 192.168.0.x on cold start
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
2017 May 17
4
Upgraded > Samba no longer listening on 192.168.0.x
Hello Since I last ran "apt-get upgrade" on a Debian host which upgraded Debian to 8.8 and Samba to 4.2.14, Samba is no longer listening on the 192.168.0.x network after waking up from suspend mode. As a result, it's not listed in Windows' Network Neighborhood and, thus, not reachable from a Windows host where a backup job is running that uses the Debian host as a file server.
2017 May 17
2
Upgraded > Samba no longer listening on 192.168.0.x
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 >
2017 May 17
1
Upgraded > Samba no longer listening on 192.168.0.x
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
2017 Jul 09
0
[3.6.6] nmbd reachable on 0.0.0.0: Safe?
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
2016 Aug 08
0
Samba 4.2.14 Group Policy (GPO) sync error
Hai, Ive tested the following, i use static and dhcp ip here. Everything on static ip works perfect on win7 and win10. And at the domain join the a and ptr is created automaticly. GPO works fine for both. Dhcp ip. Win 7 works fine, AD join A and PTR is created and updated when the ip is changes. GPO works fine. Win 10 works, AD join A and PTR is created and but not updated when the ip is
2007 Oct 21
0
Taking a stab at a pure Ruby Dir.glob
Hi all, Here''s what I''ve come up with so far for a pure Ruby Dir.glob for MS Windows. It almost works. The problem right now is the [] notation, which I''m not translating properly into a regex. I haven''t started on the ''**'' notation yet either, but I figure that''s more of a control flow issue. Feel free to disagree with me and/or
2007 Mar 04
1
Problem using callNextMethod() in S4
Dear all, Maybe, I am doing something wrong, but using R-2.5.0 on my Intel-Mac, I have problems using function callNextMethod() in method initialize. I am loading the following code as file "testS4.R": setClass("baseClass", representation(myname = "character", mydir = "character", "VIRTUAL"),
2003 Jan 29
1
Scoping rule problem -- solved
Thanks to some comments from Brian D. Ripley, I found my error: I should not have given a data argument to lm() after creating a formula-object. This obviously confused things... Thanks again, I've really learnt again a bit more on R-programming... Cheers, Winfried --------------------------------------------------------------------- E-Mail: Winfried Theis <theis at
2013 Aug 16
2
Maildirmake equiv?
Since I am using dovecot I do not have courier installed, but Courier had a very handy tool for making maildir folders called `maildirmake` which I used in some automated backup scripts. How do I duplicate maildirmake in dovecot? for example: #!/bin/bash # v1.2a Testing for new dovecot install # Archive mail from folders without [0-9]{4} Maildirs # after they are 21 days old to a yearly folder
2013 May 21
1
R CMD check: unknown option ?--outdir==RCHECK?
Hi, I believe this is kind of a long standing bug though. In R-3.0.1, but this also happened in previous versions, the long version '--outdir' is not recognised: For `R CMD check --outdir=mydir pkg_0.1.tar.gz` we get: Warning: unknown option ‘--outdir=mydir’ But with `R CMD check -o mydir pkg_0.1.tar.gz` we get: * using log directory ‘/home/renaud/Documents/projects/mydir/pkg.Rcheck’
2000 Apr 12
1
Problems with SuSE 6.4
Hello! A friend of mine tried to install R 1.0.0 on a Linux SuSE 6.4 with new compilers and new X. First the X-libs could not be found. Using the apropriate flags to change the paths for X-libs for configure (deleting first configure.cache) did not solve the problem. So he copied the libs to the expected /usr/X11/lib/ resp. include (because linking was not possible) it compiled fine up to the
2002 Mar 12
2
problem with environment detecting
Hello! I want to detect some environment on a remote host (in C program, getenv()), but it is failed. Here is a little program which I try to run on a remote host with command: "#ssh myhost myecho" /* myecho */ #include <stdio.h> main (){ char *dir; if ((dir = getenv("MYDIR")) != NULL) printf ("environment is %s\n",dir);