Unable to access shared folders since firmware 4.3.3 update

[scsirob]

I'm starting to think it has something to do with daemon_mgr, a utility that runs and terminates daemon processes. Can anyone with access to a QNAP with older 4.2.x firmware upload the output of 'ls /etc/rcS.d', and the content of /etc/daemon_mgr.conf to this thread? I'd like to compare with the 4.3.3 situation

[gusa6666]

Qnap Support told me that i should downgrade to the older firmware. A new Firmware will not be available before Jul/Aug.

[Roby77]

that's great

so i resuggest to edit host file in windows

[2K9R56S]

From 4.2.4 Build 20170313

Code: Select all

[/] # ls /etc/rcS.d
QS100QcloudSSLCertificate@ S73ntpclient@
QS101QcloudSSLCertificate@ S75stunnel@
S55urandom@                S77recycled@
S56mariadb@                S78qraid1@
S56start_service@          S83ups@
S57init_qpkg@              S85login@
S57ldap@                   S89bonjour@
S58printer@                S90twonkymedia@
S59Qthttpd@                S92lunportman@
S62GQ@                     S93iSCSItrgt@
S62cupsd@                  S95snmp@
S62smb@                    S98init_nas@
S64MediaService@           S99atalk@
S65thttpd@                 S99init_iTune@
S66ImRd@                   S99mysqld@
S66wfm_thttpd@             S99nfs@
S67ftp@                    S99porter@
S68nvrd@                   S99qanalytic@
S70crond@                  S99qsyncman@
S72logo@                   S99z_antivirus@

[2K9R56S]

Code: Select all

DAEMON0 = hotswap, start, /sbin/hotswap &
DAEMON1 = qwatchdogd, start, /sbin/qwatchdogd -t 1 &
DAEMON2 = bcclient, start, /sbin/bcclient
DAEMON3 = modagent, start, /sbin/modagent
DAEMON4 = qsmartd, start, /sbin/qsmartd -d
DAEMON5 = nmbd, start, /usr/local/samba/sbin/nmbd -l /var/log -D -s /etc/config/smb.conf
DAEMON6 = radvd, stop, /usr/sbin/radvd
DAEMON7 = upnpd, start, /sbin/upnpd eth0 eth0
DAEMON8 = winbindd, stop, /usr/local/samba/sbin/winbindd
DAEMON9 = qpkgd, start, /sbin/qpkgd -d0 > /dev/null 2>&1 &
DAEMON10 = Qthttpd, start, /usr/local/sbin/Qthttpd -p 80 -nor -nos -u admin -d /home/Qhttpd -c '**.*'
DAEMON11 = cupsd, start, /usr/sbin/cupsd -c /etc/config/cups/cupsd.conf
DAEMON12 = smbd, start, /usr/local/samba/sbin/smbd -l /var/log -D -s /etc/config/smb.conf
DAEMON13 = mytranscodesvr, start, TERMINFO='/usr/share/terminfo/' LANG='en_US.UTF-8' /usr/sbin/screen -dmS 'MYTRANSCODE' /usr/local/medialibrary/bin/mytranscodesvr -s -debug -db /share/MD0_DATA
DAEMON14 = _thttpd_, start, /usr/local/sbin/_thttpd_ -p 58080 -nor -nos -u admin -d /home/httpd -c '**.*' -h 127.0.0.1 -i /var/lock/._thttpd_.pid
DAEMON15 = apache_proxy, start, /usr/local/apache/bin/apache_proxy -k start -f /etc/apache-sys-proxy.conf 2>/dev/null 1>/dev/null
DAEMON16 = lpb_scheduler, start, /sbin/lpb_scheduler -d
DAEMON17 = genthd, start, /sbin/genthd&
DAEMON18 = bluetoothd, start, /etc/init.d/bluetooth.sh btstart 2>/dev/null 1>/dev/null
DAEMON19 = remote_folder_d, start, /usr/local/sbin/remote_folder_daemon --reset >/dev/null 2>&1 &
DAEMON20 = proftpd, start, LD_PRELOAD=/usr/local/lib/libtrash.so TZ=/etc/localtime /usr/local/sbin/proftpd -n > /dev/null 2>&1 &
DAEMON21 = ntpdated, start, /usr/sbin/ntpdated
DAEMON22 = upsutil, start, /usr/sbin/upsutil  &
DAEMON23 = utelnetd, start, /bin/utelnetd -p 23 &
DAEMON24 = crond, start, /usr/sbin/crond -l 9 -c /tmp/cron/crontabs
DAEMON25 = apache_proxys, start, /usr/local/apache/bin/apache_proxys -k start -f /etc/apache-sys-proxy-ssl.conf 2>/dev/null 1>/dev/null
DAEMON26 = picd, start, /sbin/picd  1>/dev/null 2>/dev/null &
DAEMON27 = gpiod, start, /sbin/gpiod &
DAEMON28 = hwmond, start, /sbin/hwmond &
DAEMON29 = hd_util, start, /sbin/hd_util &
DAEMON30 = gen_bandwidth, start, /sbin/gen_bandwidth -r -i 5 &
DAEMON31 = klogd.sh, start, /etc/init.d/klogd.sh start &
DAEMON32 = qsyslogd, start, /sbin/qsyslogd
DAEMON33 = qLogEngined, start, /sbin/qLogEngined
DAEMON34 = qShield, start, /sbin/qShield
DAEMON35 = qNoticeEngined, start, /sbin/qNoticeEngined
DAEMON36 = vdd_control, start, /sbin/vdd_control -d >/dev/null 2>&1 &
DAEMON37 = cnid_metad, start, /usr/local/sbin/cnid_metad -F /etc/afp.conf
DAEMON38 = afpd, start, /usr/local/sbin/afpd -F /etc/afp.conf -p /var/afpd3.pid
DAEMON39 = pn_daemon, stop, /usr/local/bin/pn_daemon -d 7 > /dev/null 2>&1
DAEMON40 = porter, stop, /usr/local/bin/porter -d 7 > /dev/null
DAEMON41 = qb_daemon, start, /usr/local/bin/qb_daemon -d 7 > /dev/null 2>&1
DAEMON42 = qsyncman, start, /usr/bin/qsyncman 1>/dev/null 2>&1
DAEMON43 = upnpcd, start, /sbin/upnpcd -i 300 &

[scsirob]

From 4.2.4 Build 20170313

Thank you. Unfortunately it doesn't show what I hoped for. 4.3.3 has a few more processes but the sequence is pretty much the same.
It's up to QNAP to fix this.

[RobbieSDA]

...
Permitting you have SAMBA 4 and QTS 4.3.3 in place - do this:

[~] # smb2status
smbd (samba daemon) Version 4.4.9
smbd (samba daemon) is running.
max protocol SMB 1.0 enabled.

[~] # smb3enable
smbd (samba daemon) Version 4.4.9
smbd (samba daemon) is running.
max protocol SMB 3.0 enabled.

That was the exact issue I had and this fixed it. Thank you!
Why does an upgrade not set the highest available protocol support? Mere mortal end-users will never find this unless they happen to know about this forum.

I have Windows 7 & 10 and TS-219P+ and TS-119II QNAP NAS's. Where do I enter the shell commands mentioned above? I tried in Windows command prompt and no luck.
Somewhere when logged into the NAS?

Thanks.

Rob Bamford (AKA RobbieSDA)

[OneCD]

Hi Rob and welcome to the forum.

Where do I enter the shell commands mentioned above? I tried in Windows command prompt and no luck.
Somewhere when logged into the NAS?

Yes, you'll enter these at the command-line interface for the NAS. But to access this, you'll need to SSH / PuTTY into your NAS as the 'admin' user.

[RobbieSDA]

OneCD, thanks for your quick reply. I think I'll be able to figure it out from here. (Fingers crossed!)

Rob Bamford (AKA RobbieSDA)

[effetredici]

Qfix for CVE-2017-7494
viewtopic.php?t=132991

[Roby77]

best solution for me thar restart nas every day is to edit host file

[palmerac]

Qnap Support told me that i should downgrade to the older firmware. A new Firmware will not be available before Jul/Aug.

It was so frustrating to lose the ability to see and browse NAS directories via Windows Explorer after updating to 4.3.3. I assume the relevant changes are related to security vulnerabilities, nevertheless this has been a disappointing experience.

Just downgraded to 4.2.5 build 20170413 and while the NAS does appear under Network in Windows Explorer, the following error message appears if/when we try to browse folders on the NAS:

"...not accessible. You might not have permission to use this network resource. Contact the administrator of the server to find out if you have access permissions."

[Roby77]

Temp fix edit your host file and restart your LAN connection

[Nickelodian]

Hi,

My Qnap TS-1079 Pro has gone completely bonkers nothing works.

Cant connect using ssh(so I can't test samba fix) it hangs after I enter password and the web-Ui "hangs" with "NAS busy or lost network connection"
anyone else has the same symptoms? (with ssh and web Ui ?)

//Niklas

[scsirob]

Temp fix edit your host file and restart your LAN connection

You have now repeated this several times as being 'the best fix'. It isn't. QNAP broke something in their Samba setup. They need to fix that.

Editing host files is a hard-wired way to force things. It is impractical for networks with many Windows clients, and with laptops where users cannot edit the file. It's a downright nightmare if in a year from now you need to change the IP plan on your network or the IP address of your QNAP and you now have to deal with bunches of users who can no longer access the QNAP and may have to re-edit every hosts file to change to a new address, or just to remove the entries because QNAP has long fixed the problem.

Editing your hosts file is snake oil.