SMB bug in 4.3.6.1040 (2019/08/20)

[emufan]

I have the same problem on my 453U.

noob question : What do I need to do once I've edited the smb.conf? Stop/starting MS networking from the GUI just overwrites the file and puts me back to square one.

thx

What worked here: Instead of trying to edit it on the NAS, I have downloaded /etc/init.d/smb.sh, edited and uploaded back again. Then I restarted smb with putty and now, it is working regardless of restarts.

[OneCD]

What worked here: Instead of trying to edit it on the NAS, I have downloaded /etc/init.d/smb.sh, edited and uploaded back again. Then I restarted smb with putty and now, it is working regardless of restarts.

This will only work until the NAS is rebooted.

[Toxic17]

Thanks a lot P3R!
This rocked. It was a piece of cake, not even enough to get out the strong liquor.
Looks like the machine comes back on 4.3.6.0993 in good health.
I'm spechless about the firmware upgrade...
Because, if there would be the one essential function that a NAS should always and ever be able to provide, well, network shares would be a good choice.
How can deployment with this kind of error get though internal testing?

However, that's QNAP to find out and decide how to treat their customers.

Thanks a lot for your specific and qualified help!

Frank

it happens every now and then

search.php?keywords=%5Bremoved%5D+QTS&t ... mit=Search

[mjstraw]

In my situation, shares like Public seem to work fine. It's only the Home shares that don't work - can connect and even retrieve some files. But double-clicking on .xlsx, .docx or .txt fails once the app opens and actually tries to retrieve the file.
Browsing around thru Home share directories is slow/sluggish.

[mjstraw]

"browse" button in firmware update doesn't do anything

[mjstraw]

On a TS-453S Pro with firmware 4.3.6.1040 (2019/08/20), in /etc/init.d/smb.sh at line 1038, we have:

Code: Select all

homes_smb_encrypt=`/sbin/getcfg homes "smb encrypt" -d "disable" -f /etc/config/smb.conf`

Which creates entries in /etc/config/smb.conf:

Code: Select all

smb encrypt = disable

These entries are invalid, it should be "disabled" with a "d", not "disable".
As a consequence, SMB fails to start properly, and it is not possible to connect to the NAS.

Here's what mine looks like under .1040

[/etc/init.d] # grep -i disable /etc/config/smb.conf |more
disable spoolss = no
server signing = disabled
smb encrypt = disabled
smb encrypt = disabled
smb encrypt = disabled
smb encrypt = disabled
smb encrypt = disabled
smb encrypt = disabled
smb encrypt = disabled
smb encrypt = disabled
smb encrypt = disabled
smb encrypt = disabled
smb encrypt = disabled
smb encrypt = disabled
smb encrypt = disabled
smb encrypt = disabled
smb encrypt = disabled
smb encrypt = disabled
smb encrypt = disabled
[/etc/init.d] #

[mjstraw]

"browse" button in firmware update doesn't do anything

Started new browser window and now it works. Go figure.

[mjstraw]

Even though my symptoms were quite different, downgrading firmware fixed my problem.

[the606]

Hi,

I have had the same issue, downgraded and all seemed well.

However I have several Windows 10 machines, some are prompting for username\password and some are not.

Strange! I have disconnected and reconnected mapped drives etc. but not luck.

Any ideas?

edit: works if I add Admin user\pass (NAS admin) on machine when prompted. Cant see any drives without it on the machines with issues.

[roytanck]

Just wanted to add that this affected my TS-231P2 as well. Adding the "d" to smb.sh and disabling+enabling Samba fixed the issue. I've not restarted the whole NAS since, and I'm hoping QNAP will release a fix before my next reboot.

[emufan]

Really QNAP?`This stupid bug in 1040. Then take 1040 back from the Server. Now 1050 is there. and …

this d is still missing in disable(d). I can not believe it.

[oli868]

I have a TS-453B and saw the same issue.

Just updated from 4.3.6.1040 to the latest f/w TS-X53B_20190830-4.3.6.1050 and the issue still exists.

A quick fix (w/o reboot) is to edit the files (replace 'disable' by 'disabled') and restart smb-service.

# ssh or telnet to NAS
# cp /etc/config/smb.conf /etc/config/smb.conf_ORG
# vim /etc/config/smb.conf
# modify & save
# cp /etc/init.d/smb.sh /etc/init.d/smb.sh_ORG
# vim /etc/init.d/smb.sh
# modify & save
# /etc/init.d/smb.sh restart

output:
Restarting SMB services:
Shutting down SMB services: smbd smbd-notifyd cleanupd nmbd.
Shutting down winbindd services: winbindd.
locks path was set to /share/MD0_DATA/.locks
Starting SMB services:Shutting down winbindd services: winbindd.
Starting winbindd services: winbindd.
.
done.

This fixed it right away on Windows 10. (net use ...)

Haven't rebooted since then, so I can't tell if smb.sh will be overwritten during reboot.

Enjoy!

[soulution]

I have a TS-453B and saw the same issue.

Just updated from 4.3.6.1040 to the latest f/w TS-X53B_20190830-4.3.6.1050 and the issue still exists.

A quick fix (w/o reboot) is to edit the files (replace 'disable' by 'disabled') and restart smb-service.

# ssh or telnet to NAS
# cp /etc/config/smb.conf /etc/config/smb.conf_ORG
# vim /etc/config/smb.conf
# modify & save
# cp /etc/init.d/smb.sh /etc/init.d/smb.sh_ORG
# vim /etc/init.d/smb.sh
# modify & save
# /etc/init.d/smb.sh restart

output:
Restarting SMB services:
Shutting down SMB services: smbd smbd-notifyd cleanupd nmbd.
Shutting down winbindd services: winbindd.
locks path was set to /share/MD0_DATA/.locks
Starting SMB services:Shutting down winbindd services: winbindd.
Starting winbindd services: winbindd.
.
done.

This fixed it right away on Windows 10. (net use ...)

Haven't rebooted since then, so I can't tell if smb.sh will be overwritten during reboot.

Enjoy!

Confirmed. 4.3.6.1050 nothing is fixed in regards to SMB. Workaround as stated by oli868 (still) works. This is embarassing for QNAP folks.

[Ron1963]

My 251 is OK with 4.3.6.1050. Although still embarrassing, not all platforms are affected apparantly. I did not install 4.3.6.1040 before.

[aesculus]

1050 did nothing for my TS-453Be. I still have to apply the hacks in the first post.