Unable to access shared folders since firmware 4.3.3 update

FTP Server, File Server, DDNS, SAMBA, AFP, NFS
Locked
User avatar
schumaku
Guru
Posts: 43578
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

Post by schumaku »

AlexeyVP wrote: [~] # smb2status

smbd (samba daemon) Version 4.4.15 ] #[/color]
smbd (samba daemon) is not running.
max protocol SMB 2.1 enabled.
[~
Post the output of:

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

[~] # cat /var/log/log.nmbd
...
AlexeyVP
Starting out
Posts: 10
Joined: Fri Aug 04, 2017 10:23 pm

Re: Unable to access shared folders since firmware 4.3.3 update

Post by AlexeyVP »

schumaku wrote:
AlexeyVP wrote: [~] # smb2status

smbd (samba daemon) Version 4.4.15 ] #[/color]
smbd (samba daemon) is not running.
max protocol SMB 2.1 enabled.
[~
Post the outtut of:

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

[~] # cat /var/log/log.nmbd
...
Sorry, rolled out to 4.2.0 already ( i need my data for a job).
Well, all worked fine again.

The old rule of all admins: "if the system works fine - do not touch it."
Despite the higher release number 8) .
Last edited by AlexeyVP on Sat Aug 05, 2017 1:39 am, edited 1 time in total.
User avatar
schumaku
Guru
Posts: 43578
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

Post by schumaku »

AlexeyVP wrote:Sorry, rolled out to 4.2.0 already .
Well, all worked fine again.
Typical cause is a removed guest account, or a modded smb.conf file with a "guest account" line missing in [global] or pointing to another non-existing user. Should be easy to troubleshoot.
AlexeyVP wrote:The old rule of all admins: "if the system works fine - do not touch it."
Rule is sparely applicable in today's security, IT audit, and IT risk world.
AlexeyVP
Starting out
Posts: 10
Joined: Fri Aug 04, 2017 10:23 pm

Re: Unable to access shared folders since firmware 4.3.3 update

Post by AlexeyVP »

AlexeyVP wrote:The old rule of all admins: "if the system works fine - do not touch it."
Rule is sparely applicable in today's security, IT audit, and IT risk world.
Totally agree with you. Especially in terms of security.
This is a home NAS, and without connecting to the Internet (behind the h/w firewall, with ACL, MAC filtering, smart politics, SNORT etc..) :D .

P.S. However, when i try to troubleshoot this problem, saved smb.conf and log.smbd.
But I needed access to my data, so I did not exam this reports carefully ..

smb.conf ("GLOBAL" part):
[global]
passdb backend = smbpasswd
workgroup = NAS
security=user
server string=NAS Server
encrypt passwords = Yes
username level = 0
map to guest = Bad User
null passwords = yes
max log size = 10
name resolve order = bcast wins
socket options = TCP_NODELAY SO_KEEPALIVE
os level = 20
preferred master = no
dns proxy = No
smb passwd file=/etc/config/smbpasswd
username map = /etc/config/smbusers
guest account = guest
directory mask = 0777
create mask = 0777
oplocks = yes
locking = yes
disable spoolss = no
load printers=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/
delete veto files = yes
map archive = no
map system = no
map hidden = no
map read only = no
deadtime = 10
use sendfile = yes
unix extensions = no
store dos attributes = yes
client ntlmv2 auth = yes
dos filetime resolution = no
inherit acls = yes
wide links = yes
force unknown acl user = yes
template homedir = /share/homes/DOMAIN=%D/%U
domain logons = no
case sensitive = auto
domain master = auto
local master = yes
enhance acl v1 = yes
remove everyone = yes
kernel oplocks = no
mangled names = yes
printcap cache time = 0
printcap name=/etc/printcap
printing=cups
show add printer wizard=no
min receivefile size = 256
conn log = yes
pid directory = /var/lock
server role = auto
smb2 leases = yes
durable handles = yes
kernel share modes = no
posix locking = no
lock directory = /share/MD0_DATA/.samba/lock
state directory = /share/MD0_DATA/.samba/state
cache directory = /share/MD0_DATA/.samba/cache
acl allow execute always = yes
server signing = disabled
streams_depot:delete_lost = yes
streams_depot:check_valid = no
fruit:nfs_aces = no
fruit:veto_appledouble = no
winbind enum groups = Yes
winbind enum users = Yes
winbind expand groups = 1
max protocol = SMB2_02
vfs objects = shadow_copy2 catia fruit qnap_macea streams_depot



and log.smbd

192.168.1.13 - is a NAS gigabit eth.
192.168.1.86 - is DUNE media player


cat /var/log/log.nmbd and /var/log/log.smbd
[2017/08/04 17:04:37.488112, 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/04 17:04:57.489126, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/08/04 17:04:59.494883, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.13 for name WORKGROUP<1d>.
This response was from IP 192.168.1.86, reporting an IP address of 192.168.1.86.
[2017/08/04 17:05:01.873725, 0] ../source3/nmbd/nmbd.c:169(nmbd_sig_hup_handler)
Got SIGHUP dumping debug info.
[2017/08/04 17:05:01.873787, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 192.168.1.13: netmask= 255.255.255.0:
WORKGROUP(1) current master browser = UNKNOWN
MEGANAS0 40801a03 (NAS Server)
[2017/08/04 17:05:24.859581, 0] ../source3/nmbd/nmbd.c:58(terminate)
Got SIGTERM: going down...
[2017/08/04 17:05:24.898653, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/08/04 17:10:31.907420, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/08/04 17:14:55.498531, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/08/04 17:16:28.741346, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/08/04 17:16:59.033590, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/08/04 17:39:36.598394, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/08/04 17:53:40.518218, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/08/04 18:12:08.121584, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2017/08/04 18:31:56.364842, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'nmbd' finished starting up and ready to serve connections
cat: and: No such file or directory
[2017/08/04 18:13:40.401854, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:14:11.142553, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:14:41.867696, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:15:12.602148, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:15:43.327209, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:16:14.052275, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:16:44.777604, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:17:15.502219, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:17:46.231028, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:18:16.955616, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:18:47.680211, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:19:18.404667, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:19:49.128429, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:20:19.853228, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:20:50.577277, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:21:21.299738, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:21:52.023616, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:22:22.746979, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:22:53.471898, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:23:24.219655, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:23:54.946390, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:24:25.685958, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:24:56.410385, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:25:27.152309, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:25:57.882155, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:26:28.607599, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:26:59.341005, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:27:30.067550, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:28:00.796660, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:28:31.525507, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:29:02.250964, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:29:32.974780, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:30:03.700203, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:30:34.423404, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:31:05.146736, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:31:35.869996, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:31:54.534472, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:31:54.668989, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:31:55.664034, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:31:56.455823, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:31:57.451952, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:32:27.180133, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:32:57.903582, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:33:28.627348, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:33:59.353332, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:34:30.077725, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:35:00.802340, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:35:31.530502, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:36:02.255902, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:36:32.981927, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:37:03.712736, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:37:34.438849, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
[2017/08/04 18:38:05.162281, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
User avatar
schumaku
Guru
Posts: 43578
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

Post by schumaku »

sht log.smbd start with this...
[2017/08/04 18:13:40.401854, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
...I guess.

Run testparm on the config:
testparm
Is this again on 4.3.3.0262?
AlexeyVP
Starting out
Posts: 10
Joined: Fri Aug 04, 2017 10:23 pm

Re: Unable to access shared folders since firmware 4.3.3 update

Post by AlexeyVP »

schumaku wrote:sht log.smbd start with this...
[2017/08/04 18:13:40.401854, 0] ../lib/param/loadparm.c:1560(set_variable_helper)
set_variable_helper(y626-6F7E2611E522</guid>): value is not boolean!
...I guess.

Run testparm on the config:
testparm
Is this again on 4.3.3.0262?
Yes, it's was logs 4.3.3.0262 saved before rollback .
Now i am on 4.2.0 again, wait for the fixed version. 8)
User avatar
schumaku
Guru
Posts: 43578
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

Post by schumaku »

AlexeyVP wrote:Now i am on 4.2.0 again, wait for the fixed version.
Doubt it's a firmware issue - much more a problem with the existing smb.conf ... thus a testparm (on the updated system) might provide some insight.
Mackspower
New here
Posts: 2
Joined: Sun Jan 15, 2017 12:19 pm

Re: Unable to access shared folders since firmware 4.3.3 update

Post by Mackspower »

Mackspower wrote:Just wanted to add my name to the list of affected users: TS-653a running FW 4.3.3.0238.

Spent hours on this issue (thought I was losing my mind) only to discover it is known issue. :-(

QNAP, please fix this.
I manually updated to version FW 4.3.3.0262 yesterday. Problem initially appeared to be solved . . . but today, QNAP box has once again disappeared from the network view again in Windows explorer.

Confirmed Samba is running
smbd (samba daemon) Version 4.4.15
smbd (samba daemon) is running.
max protocol SMB 3.0 enabled.

It is map-able / accessible via IP address. What the heck QNAP?

I bought this box to simplify my home network maintenance and management. Really disappointed and regretting the purchase now.
User avatar
schumaku
Guru
Posts: 43578
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

Post by schumaku »

mcflyy wrote:unfortunately it happened again. I did a complete fresh installation yesterday. From scratch.
There is much more in place than what a scratch install does.

The NAS system log does not show a problem like a ram disk full ...?

When open File Station, there is a message about a problem with a source file. Suspect this cloud be about /etc/config/smb.conf ... SSH login, and run a testparm on it.
PatrickPR
Starting out
Posts: 21
Joined: Fri Aug 05, 2011 4:32 pm

Re: Unable to access shared folders since firmware 4.3.3 update

Post by PatrickPR »

I can confirm that the new firmware solved my issue.

I manually updated my 419P+ (which is now functioning as a rsync target) to 4.3.3.0262. After a scheduled shutdown and reboot, the shares where accessible by nas name and rsync still worked. So issue fixed for me.
I didn't had to update my nas because smb is not needed for rsync backup, but it's nice to know that the nas is running firmware with the latest security patches.
equ1nt1s
Starting out
Posts: 26
Joined: Sun Jul 30, 2017 10:43 pm

Re: Unable to access shared folders since firmware 4.3.3 update

Post by equ1nt1s »

TVS-882 user on 4.3.3.0262 and also having the same issue. Works in rollbacks to 4.2.5. I'm also getting the same issue where i check the smb status and it shows that SAMBA isn't even running. I've tried to restart the process, but that doesn't do anything. It does mention I/O errors.
User avatar
schumaku
Guru
Posts: 43578
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

Post by schumaku »

equ1nt1s wrote:TVS-882 user on 4.3.3.0262 and also having the same issue. Works in rollbacks to 4.2.5. I'm also getting the same issue where i check the smb status and it shows that SAMBA isn't even running. I've tried to restart the process, but that doesn't do anything. It does mention I/O errors.
Workgroup, Member Server in an Active Directory, or LDAP integrated NAS?

Show the complete transcript of

[~] # /etc/init.d/smb.sh restart
...

And then, to gain some more insight:

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

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

Typical cause are modded smb.conf, bad guest account mapping, or a removed guest account from /etc/passwd

Further on, please run

[~] # testparm
...
press enter when requested
...

This will show config issues in sb.conf.
glandelf
First post
Posts: 1
Joined: Mon Dec 12, 2016 6:58 pm

Re: Unable to access shared folders since firmware 4.3.3 update

Post by glandelf »

I found that after the Win10 Creators update that my PC stopped seeing the NAS 451. When I forced the NAS box to use Samba 3 instead of 2.1 all our PCs could see the box again in File Manager. However I am now having issues with Qfile transfering photos automatically. Probably unrelated. Hope that helps.
User avatar
schumaku
Guru
Posts: 43578
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

Post by schumaku »

glandelf wrote:I found that after the Win10 Creators update that my PC stopped seeing the NAS 451.
Which one? Windows 10 Creators updates exist since early April 2017, Windows 10, version 1703 aka. Version 10.0.15063 for example.
glandelf wrote: When I forced the NAS box to use Samba 3 instead of 2.1 all our PCs could see the box again in File Manager.
Neither SMB 2.1 nor SMB 3 serve for discovery or name resolution purposes - it's all continues to be NetBIOS based for a while.
homeless
New here
Posts: 4
Joined: Fri Oct 10, 2014 3:15 am

Re: Unable to access shared folders since firmware 4.3.3 update

Post by homeless »

glandelf wrote:I found that after the Win10 Creators update that my PC stopped seeing the NAS 451. When I forced the NAS box to use Samba 3 instead of 2.1 all our PCs could see the box again in File Manager. However I am now having issues with Qfile transfering photos automatically. Probably unrelated. Hope that helps.
I confirm that after the upgrade , my Qnap stopped being visible in my network
I reset the settings to factory settings and it did not help.
Media Streaming Add-on works.
Also my SONY TV has stopped seeing my Qnap
Windows 10 1703 last updates
Qnap TS-451 4.3.3.0262
Locked

Return to “File Sharing”