Unable to access shared folders since firmware 4.3.3 update
- schumaku
- Guru
- Posts: 43579
- Joined: Mon Jan 21, 2008 4:41 pm
- Location: Kloten (Zurich), Switzerland -- Skype: schumaku
- Contact:
Re: Unable to access shared folders since firmware 4.3.3 update
Still able to ping the NAS under it's name?
c:\> ping NASname
...
Show us the content of /var/log/log.nmbd
[~] # cat /var/log/log.nmbd
...
c:\> ping NASname
...
Show us the content of /var/log/log.nmbd
[~] # cat /var/log/log.nmbd
...
-
- New here
- Posts: 4
- Joined: Fri Oct 10, 2014 3:15 am
Re: Unable to access shared folders since firmware 4.3.3 update
1.DLNA server is working.
2.ping 10.0.0.2 working
ping name of my Qnap not working
tracert 10.0.0.2 give a name of my Qnap.
I tried to google, downloaded programs on Qnap. I could not get
2.ping 10.0.0.2 working
ping name of my Qnap not working
tracert 10.0.0.2 give a name of my Qnap.
Sorry.I'm new and I do not know how to pass the log here.Show us the content of /var/log/log.nmbd
[~] # cat /var/log/log.nmbd
I tried to google, downloaded programs on Qnap. I could not get
-
- New here
- Posts: 4
- Joined: Fri Oct 10, 2014 3:15 am
Re: Unable to access shared folders since firmware 4.3.3 update
Ok. I think that the problem is solved.
I had a manual address ip address. I put DHCP and now it works on the computer.
On the TV, Qnap is not visible. TV DHCP.
SMB 3.0 encryption is not enabled
I had a manual address ip address. I put DHCP and now it works on the computer.
On the TV, Qnap is not visible. TV DHCP.
SMB 3.0 encryption is not enabled
- schumaku
- Guru
- Posts: 43579
- Joined: Mon Jan 21, 2008 4:41 pm
- Location: Kloten (Zurich), Switzerland -- Skype: schumaku
- Contact:
Re: Unable to access shared folders since firmware 4.3.3 update
The TV does allow direct SMB (Windows) File Share access - or do we face a TV working with DLNA only?homeless wrote:On the TV, Qnap is not visible. TV DHCP.
-
- New here
- Posts: 4
- Joined: Fri Oct 10, 2014 3:15 am
Re: Unable to access shared folders since firmware 4.3.3 update
Yes,kodi 17.3 Before the upgrade everything workedschumaku wrote:The TV does allow direct SMB (Windows) File Share access - or do we face a TV working with DLNA only?homeless wrote:On the TV, Qnap is not visible. TV DHCP.
-
- New here
- Posts: 4
- Joined: Mon Oct 06, 2014 7:16 am
Re: Unable to access shared folders since firmware 4.3.3 update
Hello everyone.
I think I have the same problem here.
In Windows Explorer (Network) I can't see the QNAP. Even from different PC's. Only if I type in the IP Adress in the adressbar, I can reach it.
The QNAP is on Firmware 4.3.3.0262
If anyone could help me, i would appreciate it very much!
So as perviously suggested i did this:
I think I have the same problem here.
In Windows Explorer (Network) I can't see the QNAP. Even from different PC's. Only if I type in the IP Adress in the adressbar, I can reach it.
The QNAP is on Firmware 4.3.3.0262
If anyone could help me, i would appreciate it very much!
So as perviously suggested i did this:
Code: Select all
[~] # /etc/init.d/smb.sh restart
Restarting SMB services:
Shutting down SMB services: smbd smbd-notifyd cleanupd nmbd.
Shutting down winbindd services: winbindd.
locks path was set to /share/CACHEDEV1_DATA/.locks
Shutting down winbindd services: winbindd.
Starting winbindd services:Starting SMB services:.
done.
[~] #
Code: Select all
[~] # cat /var/log/log.smbd
[2017/08/12 19:04:42.496239, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2017/08/12 19:04:42.501935, 0] ../source3/lib/util_sock.c:334(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[2017/08/12 19:04:42.505151, 0] ../source3/lib/util_sock.c:334(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[2017/08/12 21:11:13.304751, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2017/08/12 21:11:13.310615, 0] ../source3/lib/util_sock.c:334(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[2017/08/12 21:11:13.313859, 0] ../source3/lib/util_sock.c:334(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[2017/08/12 21:19:24.101361, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2017/08/12 21:19:24.107270, 0] ../source3/lib/util_sock.c:334(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[2017/08/12 21:19:24.110451, 0] ../source3/lib/util_sock.c:334(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[2017/08/12 21:19:34.706838, 0] ../lib/util/pidfile.c:104(pidfile_create)
ERROR: smbd is already running. File /var/lock/smbd.pid exists and process id 3208 is running.
[2017/08/12 21:20:55.937867, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2017/08/12 21:20:55.943728, 0] ../source3/lib/util_sock.c:334(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[2017/08/12 21:20:55.946977, 0] ../source3/lib/util_sock.c:334(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[2017/08/12 21:26:42.065314, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2017/08/12 21:26:42.071165, 0] ../source3/lib/util_sock.c:334(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[2017/08/12 21:26:42.074411, 0] ../source3/lib/util_sock.c:334(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[~] #
Code: Select all
[~] # cat /var/log/log.nmbd
[2017/08/12 19:03:34.707001, 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/08/12 19:03:54.708716, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/08/12 19:04:06.585553, 0] ../source3/nmbd/nmbd.c:169(nmbd_sig_hup_handler)
Got SIGHUP dumping debug info.
[2017/08/12 19:04:06.585655, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 169.254.100.100: netmask= 255.255.0.0:
WORKGROUP(1) current master browser = UNKNOWN
NAS 40801a03 (NAS Server)
[2017/08/12 19:04:10.540120, 0] ../source3/nmbd/nmbd.c:169(nmbd_sig_hup_handler)
Got SIGHUP dumping debug info.
[2017/08/12 19:04:10.540217, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 192.168.1.14: netmask= 255.255.255.0:
WORKGROUP(1) current master browser = UNKNOWN
NAS 40801a03 (NAS Server)
[2017/08/12 19:04:43.345696, 0] ../source3/nmbd/nmbd.c:58(terminate)
Got SIGTERM: going down...
[2017/08/12 19:04:43.442937, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/08/12 19:04:44.664661, 0] ../source3/nmbd/nmbd.c:169(nmbd_sig_hup_handler)
Got SIGHUP dumping debug info.
[2017/08/12 19:04:44.664770, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 192.168.1.14: netmask= 255.255.255.0:
WORKGROUP(1) current master browser = UNKNOWN
NAS 40801a03 (NAS Server)
[2017/08/12 21:11:14.966393, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/08/12 21:19:25.806911, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/08/12 21:19:36.461165, 0] ../source3/nmbd/nmbd.c:58(terminate)
Got SIGTERM: going down...
[2017/08/12 21:19:36.556942, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/08/12 21:20:15.991025, 0] ../source3/nmbd/nmbd_become_lmb.c:418(become_local_master_fail2)
become_local_master_fail2: failed to register name WORKGROUP<1d> on subnet 192.168.1.14. Failed to become a local master browser.
[2017/08/12 21:20:15.991178, 0] ../source3/nmbd/nmbd_namelistdb.c:320(standard_fail_register)
standard_fail_register: Failed to register/refresh name WORKGROUP<1d> on subnet 192.168.1.14
[2017/08/12 21:20:57.639282, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/08/12 21:21:28.632397, 0] ../source3/nmbd/nmbd_become_lmb.c:418(become_local_master_fail2)
become_local_master_fail2: failed to register name WORKGROUP<1d> on subnet 192.168.1.14. Failed to become a local master browser.
[2017/08/12 21:21:28.632585, 0] ../source3/nmbd/nmbd_namelistdb.c:320(standard_fail_register)
standard_fail_register: Failed to register/refresh name WORKGROUP<1d> on subnet 192.168.1.14
[2017/08/12 21:26:43.721547, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[~] #
Code: Select all
[~] # testparm
Load smb config files from /etc/config/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: The "null passwords" option is deprecated
Processing section "[NAS]"
Processing section "[TMBackup]"
Processing section "[Recordings]"
Processing section "[VM]"
Processing section "[Container]"
Processing section "[Multimedia]"
Processing section "[Download]"
Processing section "[Web]"
Processing section "[Public]"
Processing section "[printers]"
Processing section "[homes]"
Processing section "[home]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
# Global parameters
[global]
server string = NAS Server
preferred master = No
smb2 leases = Yes
max log size = 10
cache directory = /share/CACHEDEV1_DATA/.samba/cache
lock directory = /share/CACHEDEV1_DATA/.samba/lock
pid directory = /var/lock
state directory = /share/CACHEDEV1_DATA/.samba/state
printcap cache time = 0
printcap name = /etc/printcap
show add printer wizard = No
min receivefile size = 256
name resolve order = host bcast
unix extensions = No
enhance acl v1 = Yes
guest account = guest
map to guest = Bad User
null passwords = Yes
passdb backend = smbpasswd
security = USER
server signing = No
smb passwd file = /etc/config/smbpasswd
username map = /etc/config/smbusers
deadtime = 10
socket options = TCP_NODELAY SO_KEEPALIVE
template homedir = /share/homes/DOMAIN=%D/%U
winbind enum groups = Yes
winbind enum users = Yes
winbind expand groups = 1
dns proxy = No
fruit:veto_appledouble = no
fruit:nfs_aces = no
streams_depot:check_valid = no
streams_depot:delete_lost = yes
idmap config * : backend = tdb
delete veto files = Yes
map archive = No
map readonly = no
store dos attributes = Yes
veto files = /.AppleDB/.AppleDouble/.AppleDesktop/:2eDS_Store/Network Trash Folder/Temporary Items/TheVolumeSettingsFolder/.@__thumb/.@__desc/:2e*/.@__qini/.Qsync/.@upload_cache/.qsync/.qsync_sn/.@qsys/.streams/.digest/
kernel share modes = No
posix locking = No
wide links = Yes
acl allow execute always = Yes
create mask = 0777
directory mask = 0777
force unknown acl user = Yes
use sendfile = Yes
vfs objects = shadow_copy2 catia fruit qnap_macea streams_depot
[NAS]
comment = System default share
path = /share/CACHEDEV1_DATA/NAS
recycle bin = Yes
guest ok = Yes
inherit permissions = Yes
invalid users = guest
smb encrypt = No
valid users = root admin
write list = admin
strict allocate = Yes
streams_depot:check_valid = yes
shadow:format = @GMT-%Y.%m.%d-%H:%M:%S
shadow:sort = desc
shadow:basedir = /share/CACHEDEV1_DATA/NAS
shadow:snapdir = /share/CACHEDEV1_DATA/_.share/NAS/.snapshot
[TMBackup]
comment = System default share
path = /share/CACHEDEV1_DATA/.timemachine
vol size limit = 2097152
guest ok = Yes
inherit permissions = Yes
invalid users = guest
smb encrypt = No
valid users = root admin TimeMachine
write list = admin TimeMachine
strict allocate = Yes
strict sync = Yes
streams_depot:check_valid = yes
shadow:format = @GMT-%Y.%m.%d-%H:%M:%S
shadow:sort = desc
shadow:basedir = /share/CACHEDEV1_DATA/.timemachine
shadow:snapdir = /share/CACHEDEV1_DATA/_.share/TMBackup/.snapshot
[Recordings]
comment = System default share
path = /share/CACHEDEV1_DATA/Recordings
recycle bin = Yes
guest ok = Yes
inherit permissions = Yes
invalid users = guest
smb encrypt = No
valid users = root admin
write list = admin
strict allocate = Yes
streams_depot:check_valid = yes
shadow:format = @GMT-%Y.%m.%d-%H:%M:%S
shadow:sort = desc
shadow:basedir = /share/CACHEDEV1_DATA/Recordings
shadow:snapdir = /share/CACHEDEV1_DATA/_.share/Recordings/.snapshot
[VM]
comment = System default share
path = /share/CACHEDEV1_DATA/VM
recycle bin = Yes
guest ok = Yes
inherit permissions = Yes
invalid users = guest
smb encrypt = No
valid users = root admin
write list = admin
strict allocate = Yes
streams_depot:check_valid = yes
shadow:format = @GMT-%Y.%m.%d-%H:%M:%S
shadow:sort = desc
shadow:basedir = /share/CACHEDEV1_DATA/VM
shadow:snapdir = /share/CACHEDEV1_DATA/_.share/VM/.snapshot
[Container]
comment = System default share
path = /share/CACHEDEV1_DATA/Container
recycle bin = Yes
guest ok = Yes
inherit permissions = Yes
invalid users = guest
smb encrypt = No
valid users = root admin
write list = admin
strict allocate = Yes
streams_depot:check_valid = yes
shadow:format = @GMT-%Y.%m.%d-%H:%M:%S
shadow:sort = desc
shadow:basedir = /share/CACHEDEV1_DATA/Container
shadow:snapdir = /share/CACHEDEV1_DATA/_.share/Container/.snapshot
[Multimedia]
comment = System default share
path = /share/CACHEDEV1_DATA/Multimedia
recycle bin = Yes
guest ok = Yes
inherit permissions = Yes
invalid users = guest
read list = @everyone
smb encrypt = No
valid users = root @everyone admin
write list = admin
strict allocate = Yes
streams_depot:check_valid = yes
shadow:format = @GMT-%Y.%m.%d-%H:%M:%S
shadow:sort = desc
shadow:basedir = /share/CACHEDEV1_DATA/Multimedia
shadow:snapdir = /share/CACHEDEV1_DATA/_.share/Multimedia/.snapshot
[Download]
comment = System default share
path = /share/CACHEDEV1_DATA/Download
recycle bin = Yes
guest ok = Yes
inherit permissions = Yes
invalid users = guest
smb encrypt = No
valid users = root admin
write list = admin
strict allocate = Yes
streams_depot:check_valid = yes
shadow:format = @GMT-%Y.%m.%d-%H:%M:%S
shadow:sort = desc
shadow:basedir = /share/CACHEDEV1_DATA/Download
shadow:snapdir = /share/CACHEDEV1_DATA/_.share/Download/.snapshot
[Web]
comment = System default share
path = /share/CACHEDEV1_DATA/Web
recycle bin = Yes
guest ok = Yes
inherit permissions = Yes
invalid users = guest
smb encrypt = No
valid users = root admin
write list = admin
strict allocate = Yes
streams_depot:check_valid = yes
shadow:format = @GMT-%Y.%m.%d-%H:%M:%S
shadow:sort = desc
shadow:basedir = /share/CACHEDEV1_DATA/Web
shadow:snapdir = /share/CACHEDEV1_DATA/_.share/Web/.snapshot
[Public]
comment = System default share
path = /share/CACHEDEV1_DATA/Public
recycle bin = Yes
guest ok = Yes
inherit permissions = Yes
invalid users = guest
read list = @everyone
smb encrypt = No
valid users = root @everyone admin
write list = admin
strict allocate = Yes
streams_depot:check_valid = yes
shadow:format = @GMT-%Y.%m.%d-%H:%M:%S
shadow:sort = desc
shadow:basedir = /share/CACHEDEV1_DATA/Public
shadow:snapdir = /share/CACHEDEV1_DATA/_.share/Public/.snapshot
[printers]
path = /var/spool/smb
browseable = No
printable = Yes
use client driver = Yes
guest ok = Yes
[homes]
comment = System default share
path = /share/CACHEDEV1_DATA/homes
recycle bin = Yes
guest ok = Yes
inherit permissions = Yes
invalid users = guest
smb encrypt = No
valid users = root admin
write list = admin
shadow:format = @GMT-%Y.%m.%d-%H:%M:%S
shadow:sort = desc
shadow:basedir = /share/CACHEDEV1_DATA/homes
shadow:snapdir = /share/CACHEDEV1_DATA/_.share/homes/.snapshot
[home]
comment = Home
path = %H
root preexec = /sbin/create_home -u '%q'
inherit permissions = Yes
invalid users = guest
read list = %u
read only = No
valid users = %u
write list = %u
shadow:format = @GMT-%Y.%m.%d-%H:%M:%S
shadow:sort = desc
shadow:basedir = %H
shadow:snapdir = /share/CACHEDEV1_DATA/homes/../_.share/homes/.snapshot
[~] #
-
- Starting out
- Posts: 31
- Joined: Sat Mar 30, 2013 4:49 am
- Location: Melbourne, Australia
Re: Unable to access shared folders since firmware 4.3.3 update
Hmm seems this issue is quite common. I've recently upgraded my firmware and noticed I cannot connect to \\QNAP-NAS but I can to \\192.x.x.x
One thing I've noticed when connected to the IP I need and am lacking permissions to copy to it.
The host file workaround worked fine, I can now browse to \\QNAP-NAS and copy to it / read from it (plex via Apple TV) but this isn't the true fix as something is underlying.
My problem is the same as everyone's but restarting SMB didn't work nor did starting samba 4.
I'm watching this thread with interest.
One thing I've noticed when connected to the IP I need and am lacking permissions to copy to it.
The host file workaround worked fine, I can now browse to \\QNAP-NAS and copy to it / read from it (plex via Apple TV) but this isn't the true fix as something is underlying.
My problem is the same as everyone's but restarting SMB didn't work nor did starting samba 4.
I'm watching this thread with interest.
-
- Know my way around
- Posts: 113
- Joined: Sun Oct 10, 2010 8:24 am
Re: Unable to access shared folders since firmware 4.3.3 update
This has been going on for several months. Is this a "bug" or a "feature" or something else? Any progress on a permanent fix?
-
- New here
- Posts: 4
- Joined: Fri Dec 07, 2012 9:45 pm
Re: Unable to access shared folders since firmware 4.3.3 update
There's a new version of firmware on Sep 1. Does that address the issue?ncnmra wrote:This has been going on for several months. Is this a "bug" or a "feature" or something else? Any progress on a permanent fix?
-
- Starting out
- Posts: 31
- Joined: Sat Mar 30, 2013 4:49 am
- Location: Melbourne, Australia
Re: Unable to access shared folders since firmware 4.3.3 update
fallsky wrote:There's a new version of firmware on Sep 1. Does that address the issue?ncnmra wrote:This has been going on for several months. Is this a "bug" or a "feature" or something else? Any progress on a permanent fix?
That version is what introduced the issue for me. Add your NAS I.P address and host name to your windows or unix host file. Worked for me
-
- Know my way around
- Posts: 113
- Joined: Sun Oct 10, 2010 8:24 am
Re: Unable to access shared folders since firmware 4.3.3 update
Adding the IP to the hosts file is a pretty lame solution. What is the cause of this issue in the first place, and the fact that QNAP doesn't address it seems pretty weak.
I upgraded regardless but the upgrade process takes so long that I left it and haven't tried. Will report back, but the last post makes me skeptical that anything has changed.
I upgraded regardless but the upgrade process takes so long that I left it and haven't tried. Will report back, but the last post makes me skeptical that anything has changed.
-
- Starting out
- Posts: 31
- Joined: Sat Mar 30, 2013 4:49 am
- Location: Melbourne, Australia
Re: Unable to access shared folders since firmware 4.3.3 update
I'd be interested to know if that works , it might mean somehow reloading the firmware might make a change.ncnmra wrote:Adding the IP to the hosts file is a pretty lame solution. What is the cause of this issue in the first place, and the fact that QNAP doesn't address it seems pretty weak.
I upgraded regardless but the upgrade process takes so long that I left it and haven't tried. Will report back, but the last post makes me skeptical that anything has changed.
I agree the host file is a lame solution but it's a work around for now. I couldn't write to it by accessing it by I.P address
-
- New here
- Posts: 4
- Joined: Fri Dec 07, 2012 9:45 pm
Re: Unable to access shared folders since firmware 4.3.3 update
Sorry to hear this. I got this disease in the last update before this one.mcewanc2 wrote:fallsky wrote:There's a new version of firmware on Sep 1. Does that address the issue?ncnmra wrote:This has been going on for several months. Is this a "bug" or a "feature" or something else? Any progress on a permanent fix?
That version is what introduced the issue for me. Add your NAS I.P address and host name to your windows or unix host file. Worked for me
My solution? Downgrade to the firmware version before that and stayed with it.
-
- Starting out
- Posts: 31
- Joined: Sat Mar 30, 2013 4:49 am
- Location: Melbourne, Australia
Re: Unable to access shared folders since firmware 4.3.3 update
Here's something more interesting , I have two NAS devices with the same firmware , only one has the problem.fallsky wrote:Sorry to hear this. I got this disease in the last update before this one.mcewanc2 wrote:fallsky wrote:There's a new version of firmware on Sep 1. Does that address the issue?ncnmra wrote:This has been going on for several months. Is this a "bug" or a "feature" or something else? Any progress on a permanent fix?
That version is what introduced the issue for me. Add your NAS I.P address and host name to your windows or unix host file. Worked for me
My solution? Downgrade to the firmware version before that and stayed with it.
TS-451 has the problem
TS-412 does not
-
- Know my way around
- Posts: 113
- Joined: Sun Oct 10, 2010 8:24 am
Re: Unable to access shared folders since firmware 4.3.3 update
Apparently this is isolated to inits with Marvell chipsets.
I'm not counting victory yet but as of the most recent firmware, it still seems to work. The issue is sporadic so I will post back in a bit to confirm if it is still working.
I'm not counting victory yet but as of the most recent firmware, it still seems to work. The issue is sporadic so I will post back in a bit to confirm if it is still working.