You are not logged in.
Currently I have Systemd - initscrips hybrid in use, cause I haven't dared to make full transition on my server yet.
I'm experiencing strange situation. My Samba shares are not visible to my lan, when started by systemd.
systemctl shows:
nmbd.service loaded active running Samba NetBIOS name server
smbd.service loaded active running Samba SMB/CIFS server
$ nmap -p 139 -sT 10.0.0.1
Starting Nmap 6.01 ( http://nmap.org ) at 2012-11-18 19:08 EET
Nmap scan report for **** (10.0.0.1)
Host is up (0.0077s latency).
PORT STATE SERVICE
139/tcp closed netbios-ssn
Nmap done: 1 IP address (1 host up) scanned in 0.05 seconds
However, when I stop smbd.service and nmbd.service, and start samba by
rc.d start samba
, my samba shares become visible.
And also
nmap -p 139 -sT 10.0.0.1
Starting Nmap 6.01 ( http://nmap.org ) at 2012-11-18 19:47 EET
Nmap scan report for **** (10.0.0.1)
Host is up (0.0038s latency).
PORT STATE SERVICE
139/tcp open netbios-ssn
Nmap done: 1 IP address (1 host up) scanned in 0.04 seconds
Does the Systemd handle the network differently, or nmbd.service doesn't start properly, does it need some additional configuration? There is not much info about systemd yet, so maybe somebody can help?
Last edited by uhuu (2012-11-27 21:48:03)
Windows is not a virus, virus does something...
Offline
Hmm.. sounds like it could be something to do with the WINS service not starting properly?
Offline
Does it work if you restart using systemd?
#systemctl restart smbd
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
First of all, provide the full 'systemctl status' output for the services that don't seem to work, then we can see if you have a problem and what it might be.
Offline
I was playing around with it and I noticed, that shares become visible, when I stop smbd.service & nmbd.service after boot, then start manually nmbd.service before smbd.service, it won't work other way around.
I tried to modify smbd.service file and add
after=nmbd.service
That didn't work either.
Status after fresh boot
$ systemctl status nmbd
nmbd.service - Samba NetBIOS name server
Loaded: loaded (/usr/lib/systemd/system/nmbd.service; enabled)
Active: active (running) since Tue, 2012-11-20 23:16:32 EET; 54s ago
Main PID: 375 (nmbd)
CGroup: name=systemd:/system/nmbd.service
└ 375 /usr/sbin/nmbd -F
[****@**** ~]$ systemctl status smbd
smbd.service - Samba SMB/CIFS server
Loaded: loaded (/etc/systemd/system/smbd.service; enabled)
Active: active (running) since Tue, 2012-11-20 23:16:32 EET; 1min 0s ago
Main PID: 382 (smbd)
CGroup: name=systemd:/system/smbd.service
├ 382 /usr/sbin/smbd -F
└ 432 /usr/sbin/smbd -F
Seems that simply restarting smbd&nmbd simply manually also works.
Windows is not a virus, virus does something...
Offline
I get the same behaviour, though as I use my shares very infrequently I've not yet itched enough to scratch.
I might try and look into it this week, but let us know if you find anything else out.
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
For me, the case is closed. I removed network daemon from rc.conf and installed networkmanager. The services seem to be working nicely now.
Windows is not a virus, virus does something...
Offline
For me, the case is closed. I removed network daemon from rc.conf and installed networkmanager. The services seem to be working nicely now.
Okay thanks for the info.
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline