Qnap NAS not appearing on network (Windows Explorer)

[nikcha]

Also same problem. After latest firmware update no qnap file server appears on the windows 10 pro network or WD Live TV network shares. No fix works permanently. Some reboots of Qnap 119P+ sometimes work but after windows pc reboot nothing appears again in network. Other services work though (media servers for example)

[schumaku]

From the NAS shell, please check the presence of the nmbd process...

[~] # ps -ef | grep nmbd
4730 admin 484 S grep nmbd
17354 admin 1132 S /usr/local/samba/sbin/nmbd -l /var/log -D -s /etc/config/smb.conf

...and post the content of the log.nmbd please...

[~] # cat /var/log/log.nmbd
...

...check and let us know the local master config, ie. yes or no...

[~] # getcfg -f /etc/config/smb.conf global "local master"
no

[maurice1]

Same problem as Nicha
4.3.3 Windows10

[~] # ps -ef | grep nmbd
12160 admin 568 R grep nmbd
[~] # ps -ef | grep nmbd
12250 admin 568 S grep nmbd
[~] # getcfg -f /etc/config/smb.conf global "local master"
yes
[~] #

[maurice1]

Sorry Schmaku forgot the log:

[~] # cat /var/log/log.nmbd
[2017/04/27 12:23:31.484945, 0] ../lib/util/become_daemon.c:135(daemon_status)
STATUS=daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
[2017/04/27 12:23:41.388602, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/04/27 12:23:52.405535, 0] ../source3/nmbd/nmbd.c:58(terminate)
Got SIGTERM: going down...
[2017/04/27 12:23:53.414646, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/04/27 12:24:52.980595, 0] ../source3/nmbd/nmbd.c:58(terminate)
Got SIGTERM: going down...
[2017/04/27 12:24:53.560537, 0] ../lib/util/pidfile.c:146(pidfile_unlink)
Failed to delete pidfile /var/lock/nmbd.pid. Error was No such file or directory
[2017/04/27 12:24:53.663618, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/04/27 12:26:15.249397, 0] ../source3/nmbd/nmbd.c:169(nmbd_sig_hup_handler)
Got SIGHUP dumping debug info.
[2017/04/27 12:26:15.250022, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 192.168.0.50: netmask= 255.255.255.0:
WORKGROUP(1) current master browser = UNKNOWN
QNAS119 40011a03 (QNAS)
[2017/04/27 12:26:15.250892, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet UNICAST_SUBNET: netmask= 192.168.0.50:
WORKGROUP(1) current master browser = UNKNOWN
QNAS119 40011a03 (QNAS)
[2017/04/27 12:26:59.195118, 0] ../source3/nmbd/nmbd.c:169(nmbd_sig_hup_handler)
Got SIGHUP dumping debug info.
[2017/04/27 12:26:59.195658, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 192.168.0.50: netmask= 255.255.255.0:
WORKGROUP(1) current master browser = UNKNOWN
QNAS119 40011a03 (QNAS)
[2017/04/27 12:26:59.196450, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet UNICAST_SUBNET: netmask= 192.168.0.50:
WORKGROUP(1) current master browser = UNKNOWN
QNAS119 40011a03 (QNAS)
[2017/04/27 12:30:54.841048, 0] ../source3/nmbd/nmbd.c:58(terminate)
Got SIGTERM: going down...
[2017/04/27 12:30:56.746285, 0] ../lib/util/pidfile.c:146(pidfile_unlink)
Failed to delete pidfile /var/lock/nmbd.pid. Error was No such file or directory
[2017/04/27 12:31:00.859518, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections

[schumaku]

@maurice1, what NAS model is this?

Does restart SAMBA bring back the processes?

# /etc/init.d/smb.sh restart

[maurice1]

Its a QNAS119

I'm trying Post 6 from viewtopic.php?t=116096 and this seems to be going well, back to seeing Volume1 shared folders in Windows explorer, except for seeing my Esata and 2 x USB drives.
They don't show up in the new Filestation5 either, yet they show up in the top bar of Qnap GUI showing 3 attached storage.
Didn't have these problems until I updated to 4.3.3

[~] # mv /etc/config/smb.conf /etc/config/smb.conf.old
[~] # cp /etc/default_config/smb.conf /etc/config/
[~] # /etc/init.d/smb.sh restart
Restarting SMB services:
Shutting down SMB services: smbd smbd-notifyd cleanupd nmbd.
Shutting down winbindd services: winbindd.
umount: /msg.lock: not found
samba locks directory is not exist, create it
locks path was set to /share//.locks
Shutting down winbindd services: winbindd.
Starting winbindd services:Starting SMB services:.
done.
[~] #


"kernal - Processes" seem to be hammering my CPU to 100% so i will leave it till tomorrow.
Thanks for your suggestions schumaku

[schumaku]

@maurice1,

Unplug and re-plug (hot) the external storage devices. As you have reset SAMBA to the very defaults (loosing all access rights configured, too), the dynamically created eSATAdisk[n] and USBdisk[n] are gone now. Re-plug will trigger these shares will be re-added.

[mrlins]

Having the same problem here but only on 1 of 3 Qnap NASs in the same network (TS-219P+). Seems like this happened after the firmware update, build 20170413 (conducted yesterday)... very frustrating ...

[mrlins]

@maurice1, what NAS model is this?

Does restart SAMBA bring back the processes?

# /etc/init.d/smb.sh restart

This actually worked for me - thanks! I unchecked and applied then re-checked and applied and now the NAS appears as a 'computer' in the network again.

[maurice1]

@ schumaku
Took your advise and now everything is as it should except the CPU is a lot higher than it used to be.
Hopefully it will settle down
Kinda sorry I updated now

[hugdepop]

@ schumaku
Took your advise and now everything is as it should except the CPU is a lot higher than it used to be.
Hopefully it will settle down
Kinda sorry I updated now

for me as well and yes, also the cpu is indeed a lot higher than it supposed to be. Will QNAP pick this up for the next firmware update?

[pavel_b]

TS-112 and I'm not seeing neither of the SMB/AFP shared folders

[/share/Public] # /etc/init.d/smb.sh restart
Restarting SMB services:
Shutting down SMB services: smbd nmbd.
/etc/init.d/winbind: line 7: /usr/local/samba/sbin/winbindd: No such file or directory
Shutting down winbindd services: winbindd.
done.

Seems like something really screwed up has happened in the latest FW upgrade.

[/share/Public] # ls /usr/local/ -la
drwxr-xr-x 11 admin administ 4096 Apr 30 17:32 ./
drwxr-xr-x 10 admin administ 4096 Apr 30 17:39 ../
drwxr-xr-x 2 admin administ 4096 Apr 13 09:38 amazons3/
drwxr-xr-x 2 admin administ 4096 Apr 30 18:25 bin/
drwxr-xr-x 5 admin administ 4096 Apr 13 09:08 etc/
drwxr-xr-x 3 admin administ 4096 Apr 13 09:39 fs/
drwxr-xr-x 3 admin administ 4096 Apr 30 18:25 lib/
drwxr-xr-x 2 admin administ 4096 Apr 13 09:51 modules/
lrwxrwxrwx 1 admin administ 34 Apr 30 17:32 mysql -> /share/HDA_DATA/.qpkg/qmysql/mysql/
drwxr-xr-x 3 admin administ 4096 Apr 30 18:00 sbin/
drwxr-xr-x 2 admin administ 4096 Apr 13 08:58 share/
drwxr-xr-x 7 admin administ 4096 Apr 13 09:08 ups/

Samba folder to which the winbind points in Samba folder is just completely gone. Any ideas what to do with this mess?

Thanks

[pavel_b]

Manual load of same latest code revision via CLI took care of the shared folder problem with Samba.

[p92s]

Hi there, same problem here with Ts-219P and windows 7 ultimate EN. After the last firmware update 4.3.3.0188 the NAS is not visible in windows file manager.It is accessible from the web interface (Qfinder) I read all the posts and it seem a SAMBA application problem. Unfortunately I'm not very technical and unable to access command lines that you list in the posts. Do you think Qnap will solve the issue with a new firmware revision? Will a new firmware possibly solve the problem? So far I have not seen any sign in that direction. Thank you so much for your attention and a possible answer; I'm totally lost with the problem. Any HELP would be much appreciated. - gilbert

[greyC0re]

Same here:

TS-419P II @ 4.3.3.0210

Restarting the smb service with '# /etc/init.d/smb.sh restart' or restarting solves it (temporarily). Issue appeared with the latest firmware update.