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.intothevoid wrote: ↑Sat Aug 24, 2019 5:49 pm 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
SMB bug in 4.3.6.1040 (2019/08/20)
-
- Getting the hang of things
- Posts: 67
- Joined: Sun Jun 12, 2011 7:55 pm
Re: SMB bug in 4.3.6.1040 (2019/08/20)
- OneCD
- Guru
- Posts: 12144
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: SMB bug in 4.3.6.1040 (2019/08/20)
This will only work until the NAS is rebooted.
- Toxic17
- Ask me anything
- Posts: 6477
- Joined: Tue Jan 25, 2011 11:41 pm
- Location: Planet Earth
- Contact:
Re: SMB bug in 4.3.6.1040 (2019/08/20)
it happens every now and thenfstueckradt wrote: ↑Sun Aug 25, 2019 5:24 am
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
search.php?keywords=%5Bremoved%5D+QTS&t ... mit=Search
Regards Simon
Qnap Downloads
MyQNap.Org Repository
Submit a ticket • QNAP Helpdesk
QNAP Tutorials, User Manuals, FAQs, Downloads, Wiki
When you ask a question, please include the following
NAS: TS-673A QuTS hero h5.1.2.2534 • TS-121 4.3.3.2420 • APC Back-UPS ES 700G
Network: VM Hub3: 500/50 • UniFi UDM Pro: 3.2.9 • UniFi Network Controller: 8.0.28
USW-Aggregation: 6.6.61 • US-16-150W: 6.6.61 • 2x USW Mini Flex 2.0.0 • UniFi AC Pro 6.6.62 • UniFi U6-LR 6.6.62
UniFi Protect: 2.11.21/8TB Skyhawk AI • 3x G3 Instants: 4.69.55 • UniFi G3 Flex: 4.69.55 • UniFi G5 Flex: 4.69.55
Qnap Downloads
MyQNap.Org Repository
Submit a ticket • QNAP Helpdesk
QNAP Tutorials, User Manuals, FAQs, Downloads, Wiki
When you ask a question, please include the following
NAS: TS-673A QuTS hero h5.1.2.2534 • TS-121 4.3.3.2420 • APC Back-UPS ES 700G
Network: VM Hub3: 500/50 • UniFi UDM Pro: 3.2.9 • UniFi Network Controller: 8.0.28
USW-Aggregation: 6.6.61 • US-16-150W: 6.6.61 • 2x USW Mini Flex 2.0.0 • UniFi AC Pro 6.6.62 • UniFi U6-LR 6.6.62
UniFi Protect: 2.11.21/8TB Skyhawk AI • 3x G3 Instants: 4.69.55 • UniFi G3 Flex: 4.69.55 • UniFi G5 Flex: 4.69.55
-
- Getting the hang of things
- Posts: 66
- Joined: Wed Mar 09, 2016 7:51 am
Re: SMB bug in 4.3.6.1040 (2019/08/20)
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.
Browsing around thru Home share directories is slow/sluggish.
Mark
----------
TS-453 Pro, 4.4.1.1117
2x WD RED 3TB (Raid 1), 2x empty
----------
TS-453 Pro, 4.4.1.1117
2x WD RED 3TB (Raid 1), 2x empty
-
- Getting the hang of things
- Posts: 66
- Joined: Wed Mar 09, 2016 7:51 am
Re: SMB bug in 4.3.6.1040 (2019/08/20)
"browse" button in firmware update doesn't do anything
Mark
----------
TS-453 Pro, 4.4.1.1117
2x WD RED 3TB (Raid 1), 2x empty
----------
TS-453 Pro, 4.4.1.1117
2x WD RED 3TB (Raid 1), 2x empty
-
- Getting the hang of things
- Posts: 66
- Joined: Wed Mar 09, 2016 7:51 am
Re: SMB bug in 4.3.6.1040 (2019/08/20)
Here's what mine looks like under .1040bigorno wrote: ↑Fri Aug 23, 2019 3:45 pm 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:
Which creates entries in /etc/config/smb.conf:Code: Select all
homes_smb_encrypt=`/sbin/getcfg homes "smb encrypt" -d "disable" -f /etc/config/smb.conf`
These entries are invalid, it should be "disabled" with a "d", not "disable".Code: Select all
smb encrypt = disable
As a consequence, SMB fails to start properly, and it is not possible to connect to the NAS.
[/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] #
Mark
----------
TS-453 Pro, 4.4.1.1117
2x WD RED 3TB (Raid 1), 2x empty
----------
TS-453 Pro, 4.4.1.1117
2x WD RED 3TB (Raid 1), 2x empty
-
- Getting the hang of things
- Posts: 66
- Joined: Wed Mar 09, 2016 7:51 am
Re: SMB bug in 4.3.6.1040 (2019/08/20)
Started new browser window and now it works. Go figure.
Mark
----------
TS-453 Pro, 4.4.1.1117
2x WD RED 3TB (Raid 1), 2x empty
----------
TS-453 Pro, 4.4.1.1117
2x WD RED 3TB (Raid 1), 2x empty
-
- Getting the hang of things
- Posts: 66
- Joined: Wed Mar 09, 2016 7:51 am
Re: SMB bug in 4.3.6.1040 (2019/08/20)
Even though my symptoms were quite different, downgrading firmware fixed my problem.
Mark
----------
TS-453 Pro, 4.4.1.1117
2x WD RED 3TB (Raid 1), 2x empty
----------
TS-453 Pro, 4.4.1.1117
2x WD RED 3TB (Raid 1), 2x empty
-
- First post
- Posts: 1
- Joined: Thu Aug 29, 2019 7:08 pm
Re: SMB bug in 4.3.6.1040 (2019/08/20)
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.
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.
-
- First post
- Posts: 1
- Joined: Tue Aug 17, 2010 9:50 pm
Re: SMB bug in 4.3.6.1040 (2019/08/20)
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.
-
- Getting the hang of things
- Posts: 67
- Joined: Sun Jun 12, 2011 7:55 pm
Re: SMB bug in 4.3.6.1040 (2019/08/20)
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.
this d is still missing in disable(d). I can not believe it.
-
- First post
- Posts: 1
- Joined: Thu Feb 18, 2010 6:35 am
Re: SMB bug in 4.3.6.1040 (2019/08/20)
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!
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!
-
- New here
- Posts: 2
- Joined: Sun Jan 18, 2015 6:51 pm
Re: SMB bug in 4.3.6.1040 (2019/08/20)
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.oli868 wrote: ↑Fri Sep 06, 2019 3:05 am 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!
-
- Been there, done that
- Posts: 530
- Joined: Wed Apr 28, 2010 9:22 pm
Re: SMB bug in 4.3.6.1040 (2019/08/20)
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.
1x TS251, 1x TS251D, 1x TS253
- aesculus
- Easy as a breeze
- Posts: 346
- Joined: Fri Dec 14, 2007 11:17 am
Re: SMB bug in 4.3.6.1040 (2019/08/20)
1050 did nothing for my TS-453Be. I still have to apply the hacks in the first post.
Chris