You are not logged in.

Pages: 1

#1 2013-12-21 21:33:31

Piggoz
Member
Registered: 2013-03-31
Posts: 8

[Holy SOLVED] Weird problem with Nmbd

Hello,

I do have some Archlinux machine working fine, then I just installed another box with Archlinux and everything seems fine like usual, but this weird problem with Samba.

I installed Samba as usual (Arch wiki style) and now nmbd is properly running and everything, configuration file is the same of working Archlinux box I do adminiter, I can browse other devices in my lan, this new box is seen by other devices in lan but... when I do try to browse shares on this box it fails.

Checking with nmpa this failing box, I found nmbd didn't open the classic samba ports 138/139/445.

Now I was wondering the problem could be the firewall, then I didn't install any firewall.

Here the log when I do start nmbd:

Dec 21 14:32:18 localhost systemd[1]: Started Samba NetBIOS name server.
Dec 21 14:32:25 localhost systemd[1]: Stopping Samba NetBIOS name server...
Dec 21 14:32:25 localhost systemd[1]: Stopped Samba NetBIOS name server.
Dec 21 14:32:30 localhost systemd[1]: Starting Samba NetBIOS name server...
Dec 21 14:32:30 localhost systemd[1]: PID file /var/run/nmbd.pid not readable (yet?) after start.

if I do a:

smbclient -L localhost

I do have:

Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSED)

I said I do not have a firewall running, here the list of the programs running on my system:

PID TTY          TIME CMD
    1 ?        00:00:00 systemd
    2 ?        00:00:00 kthreadd
    3 ?        00:00:00 ksoftirqd/0
    5 ?        00:00:00 kworker/0:0H
    7 ?        00:00:00 migration/0
    8 ?        00:00:00 rcu_preempt
    9 ?        00:00:00 rcu_bh
   10 ?        00:00:00 rcu_sched
   11 ?        00:00:00 watchdog/0
   12 ?        00:00:00 khelper
   13 ?        00:00:00 kdevtmpfs
   14 ?        00:00:00 netns
   15 ?        00:00:00 writeback
   16 ?        00:00:00 bioset
   17 ?        00:00:00 kworker/u17:0
   18 ?        00:00:00 kblockd
   19 ?        00:00:04 kworker/0:1
   20 ?        00:00:00 khungtaskd
   21 ?        00:00:00 kswapd0
   22 ?        00:00:00 ksmd
   23 ?        00:00:22 khugepaged
   24 ?        00:00:00 fsnotify_mark
   25 ?        00:00:00 crypto
   30 ?        00:00:00 kthrotld
   33 ?        00:00:00 deferwq
   56 ?        00:00:00 ata_sff
   57 ?        00:00:00 mpt_poll_0
   58 ?        00:00:00 khubd
   59 ?        00:00:00 mpt/0
   60 ?        00:00:00 scsi_eh_0
   61 ?        00:00:00 scsi_eh_1
   63 ?        00:00:00 scsi_eh_2
   69 ?        00:00:00 kworker/u17:1
   77 ?        00:00:00 jbd2/sda2-8
   78 ?        00:00:00 ext4-rsv-conver
   98 ?        00:00:00 systemd-journal
  123 ?        00:00:00 systemd-udevd
  160 ?        00:00:00 ttm_swap
  176 ?        00:00:00 kpsmoused
  195 ?        00:00:00 ext4-rsv-conver
  202 ?        00:00:00 jbd2/sda4-8
  203 ?        00:00:00 ext4-rsv-conver
  212 ?        00:00:00 systemd-logind
  213 ?        00:00:00 dbus-daemon
  214 ?        00:00:00 syslog-ng
  221 ?        00:00:00 lxdm-binary
  226 tty1     00:08:43 X
  263 ?        00:00:00 dhcpcd
  264 ?        00:00:00 sshd
  267 ?        00:00:00 lxdm-session
  268 ?        00:00:00 systemd
  269 ?        00:00:00 mate-session
  271 ?        00:00:00 (sd-pam)
  278 ?        00:00:00 dbus-launch
  279 ?        00:00:00 dbus-daemon
  283 ?        00:00:00 dconf-service
  286 ?        00:00:01 mate-settings-d
  294 ?        00:00:00 mate-keyring-da
  298 ?        00:00:00 marco
  302 ?        00:00:01 mate-panel
  306 ?        00:00:00 gvfsd
  312 ?        00:00:00 gvfsd-fuse
  313 ?        00:00:02 caja
  337 ?        00:00:00 gvfs-udisks2-vo
  343 ?        00:00:00 udisksd
  349 ?        00:00:00 polkitd
  354 ?        00:00:00 polkit-mate-aut
  355 ?        00:00:00 mate-bluetooth-
  374 ?        00:00:00 wnck-applet
  378 ?        00:00:00 notification-ar
  380 ?        00:00:00 clock-applet
  382 ?        00:00:00 gvfsd-trash
  401 ?        00:00:00 gconfd-2
  431 ?        00:00:01 mate-terminal
  437 ?        00:00:00 gnome-pty-helpe
  438 pts/0    00:00:00 bash
  450 ?        03:24:26 opera
  463 ?        01:04:22 opera:libflashp
  519 ?        00:00:00 gvfsd-metadata
  528 ?        00:00:00 gvfsd-network
  534 ?        00:00:00 gvfsd-smb-brows
  541 ?        00:00:00 gvfsd-dnssd
  558 ?        00:00:00 gvfsd-smb
  599 ?        00:00:00 gvfsd-smb
 1245 ?        00:00:00 kworker/u16:1
 1890 ?        00:00:00 winbindd
 1891 ?        00:00:00 winbindd
 1912 ?        00:00:00 kworker/0:0
 1932 pts/1    00:00:00 bash
 1933 pts/2    00:00:00 bash
 1943 ?        00:00:00 nmbd
 1969 ?        00:00:00 kworker/u16:0
 1978 pts/0    00:00:00 ps

Now I'm maybe wrong then I do not see any firewall running!

Here what testparm say about my smb.conf file:

Load smb config files from /etc/samba/smb.conf
Processing section "[homes]"
Processing section "[printers]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

[global]
	workgroup = myworkgroup
	server string = Samba Server
	log file = /var/log/samba/%m.log
	max log size = 50
	printcap name = /etc/printcap
	dns proxy = No
	idmap config * : backend = tdb

[homes]
	comment = Home Directories
	read only = No
	browseable = No

[printers]
	comment = All Printers
	path = /var/spool/samba
	printable = Yes
	print ok = Yes
	browseable = No

If nmap this failing machine from the LAN, it confirm port 138/139/445 are in state closed and I think this is the problem becouse I can't browse the server.

Starting Nmap 6.40 ( [url]http://nmap.org[/url] ) at 2013-12-21 14:59 CET
NSE: Loaded 110 scripts for scanning.
NSE: Script Pre-scanning.
Initiating Ping Scan at 14:59
Scanning arch2012 (192.168.1.135) [2 ports]
Completed Ping Scan at 14:59, 0.00s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 14:59
Completed Parallel DNS resolution of 1 host. at 14:59, 13.01s elapsed
Initiating Connect Scan at 14:59
Scanning arch2012 (192.168.1.135) [1000 ports]
Discovered open port 22/tcp on 192.168.1.135
Completed Connect Scan at 14:59, 0.04s elapsed (1000 total ports)
Initiating Service scan at 14:59
Scanning 1 service on arch2012 (192.168.1.135)
Completed Service scan at 14:59, 0.00s elapsed (1 service on 1 host)
NSE: Script scanning 192.168.1.135.
Initiating NSE at 14:59
Completed NSE at 14:59, 0.16s elapsed
Nmap scan report for arch2012 (192.168.1.135)
Host is up (0.00044s latency).
Not shown: 999 closed ports
PORT   STATE SERVICE VERSION
22/tcp open  ssh     OpenSSH 6.4 (protocol 2.0)
| ssh-hostkey: 1024 xxxxxxxxxxx

NSE: Script Post-scanning.
Initiating NSE at 14:59
Completed NSE at 14:59, 0.00s elapsed
Read data files from: /usr/bin/../share/nmap

Call me dumb, then explain me were I'm wrong if you guys can!


Thankx

Last edited by Piggoz (2013-12-25 09:58:45)

Offline

#2 2013-12-21 21:46:47

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,722

Re: [Holy SOLVED] Weird problem with Nmbd

Piggoz,
Welcome to Arch Linux.  When posting  files or program output, please use  BBCode code tags around your output.  There is also a convient link to BBCode under all post boxes on the forums.

Thanks

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#3 2013-12-25 09:53:50

Piggoz
Member
Registered: 2013-03-31
Posts: 8

Re: [Holy SOLVED] Weird problem with Nmbd

Piggoz wrote:

Hello,
I do have some Archlinux machine working fine, then I just installed another box with Archlinux and everything seems fine like usual, but this weird problem with Samba.

I installed Samba as usual (Arch wiki style) and now nmbd is properly running and everything, configuration file is the same of working Archlinux box I do adminiter, I can browse other devices in my lan, this new box is seen by other devices in lan but... when I do try to browse shares on this box it fails.

Checking with nmpa this failing box, I found nmbd didn't open the classic samba ports 138/139/445.

Holy god, I didn't touch anything, I didn't had any help by the holy community here, I still had the problem for few days and this morning, holy Christmas morning, accessing my LAN, show all the shares from the failing machine. Holy spirit fixed it becouse that machine is still in the state it was when it was failing, it wasn't even rebooted.

Now every authorized client in the LAN can access the ex failing, now holy machine shares.

Correctly holy nmap (Christmas edition) now show as open port 139 and 445.

Starting Nmap 6.40 ( http://nmap.org ) at 2013-12-25 10:45 CET
Nmap wishes you a merry Christmas! Specify -sX for Xmas Scan (http://nmap.org/book/man-port-scanning-techniques.html).
NSE: Loaded 110 scripts for scanning.
NSE: Script Pre-scanning.
Initiating Ping Scan at 10:45
Scanning 192.168.1.142 [2 ports]
Completed Ping Scan at 10:45, 0.01s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 10:45
Completed Parallel DNS resolution of 1 host. at 10:45, 13.06s elapsed
Initiating Connect Scan at 10:45
Scanning 192.168.1.142 [1000 ports]
Discovered open port 445/tcp on 192.168.1.142
Discovered open port 22/tcp on 192.168.1.142
Discovered open port 139/tcp on 192.168.1.142

Just in case, I rebooted and disconnected the ex failing and now holy machine from the LAN, then connected it again and it still works.

Holy spirit, holy Christmas, holy greetings to you all, passive holy readers.


Your truly Holy Piggoz

Offline

Pages: 1

Board footer

Powered by FluxBB