Post the output of:AlexeyVP wrote: [~] # smb2status
smbd (samba daemon) Version 4.4.15 ] #[/color]
smbd (samba daemon) is not running.
max protocol SMB 2.1 enabled.
[~
[~] # cat /var/log/log.smbd
...
[~] # cat /var/log/log.nmbd
...
Post the output of:AlexeyVP wrote: [~] # smb2status
smbd (samba daemon) Version 4.4.15 ] #[/color]
smbd (samba daemon) is not running.
max protocol SMB 2.1 enabled.
[~
Sorry, rolled out to 4.2.0 already ( i need my data for a job).schumaku wrote:Post the outtut of:AlexeyVP wrote: [~] # smb2status
smbd (samba daemon) Version 4.4.15 ] #[/color]
smbd (samba daemon) is not running.
max protocol SMB 2.1 enabled.
[~
[~] # cat /var/log/log.smbd
...
[~] # cat /var/log/log.nmbd
...
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:Sorry, rolled out to 4.2.0 already .
Well, all worked fine again.
Rule is sparely applicable in today's security, IT audit, and IT risk world.AlexeyVP wrote:The old rule of all admins: "if the system works fine - do not touch it."
Totally agree with you. Especially in terms of security.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.
Is this again on 4.3.3.0262?testparm
Yes, it's was logs 4.3.3.0262 saved before rollback .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:
Is this again on 4.3.3.0262?testparm
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.AlexeyVP wrote:Now i am on 4.2.0 again, wait for the fixed version.
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.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.
There is much more in place than what a scratch install does.mcflyy wrote:unfortunately it happened again. I did a complete fresh installation yesterday. From scratch.
Workgroup, Member Server in an Active Directory, or LDAP integrated NAS?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.
Which one? Windows 10 Creators updates exist since early April 2017, Windows 10, version 1703 aka. Version 10.0.15063 for example.glandelf wrote:I found that after the Win10 Creators update that my PC stopped seeing the NAS 451.
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.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.
I confirm that after the upgrade , my Qnap stopped being visible in my networkglandelf 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.