Unable to access shared folders since firmware 4.3.3 update

[schumaku]

Whenever I kill the nmbd process (tested on half a dozen Marvell Kirkwood units), maximum 60 seconds later (this is the "schedule" for the watchdog) the process does reappear. If it does not, it's certainly an issue for QNAP to investigate on your NAS.

[scsirob]

That's what we are trying to convince QNAP of. Unfortunately the support agent that answered my ticket ignored all details I provided and told me to copy /etc/default_config/smb.sh to /etc/config/smb.sh, removing all shares and identity from my QNAP.

Fortunately I anticipated on this so recovery was quick, but unless first-line support can be convinced to escalate this issue, it will be a rough time getting this fixed. I'm perfectly happy to share details with someone at QNAP who is more knowledgable.

[PatrickPR]

The ticket that I have open for this issue is escalated to the developers, they are trying to reproduce the issue. Has been so for a while though.

[scsirob]

Mine has been escalated to engineering as well now.

[palmerac]

The ticket that I have open for this issue is escalated to the developers, they are trying to reproduce the issue.

Would it be helpful if others try to get additional tickets open and escalated? I haven't yet called QNAP, but this problem is frustrating and I would like to see it get fixed soon.

Also, I wonder why so few users are complaining about this issue. Is it only happening with certain models or certain processors?

[scsirob]

This only happens on older models with Marvell chips, 4 - 6 years old I would guess, so it's unclear how many users actually still run them. Additionally, not everyone updates their NAS regularly, not everyone logs in to the GUI on a NAS that 'just works', so many people simply do not know there's new firmware out, or they don't want to upgrade because what they have now works just fine.

Additional tickets may raise awareness at QNAP, so don't hold back. One thing is clear for me, their 1st line support is clueless so it takes a few iterations of 'have you tried rebooting it yet' before they can be persuaded to escalate the ticket. Be persistent.

[Rufus_Dorminstarg]

Add me to the list of affected users (model TS-219).

[kickbackpunk]

Add me as well TS-453A

[scsirob]

Guys,

That's not helping. We (end-users) cannot open tickets for someone else. It only helps if you all enter your own ticket.
If all is well, your 4.3.3 update also installed the "Helpdesk" app if you didn't have it already. If not, find and install it from the App center. Use it to create a ticket, it's a few easy steps.

[Roby77]

thank you, ticket opened

[fransco]

Hi,
I resolve with the Qnap Support, i change the SMB version to 2.1

[scsirob]

Hi Fransco,
Please reboot your QNAP, then wait about 30 minutes. Let us know if it still works after that.

[Roby77]

last day i opened the ticket and support asked me to explain better the problem

BUT i don't know what's going on...if i try \\NASNAME\share no problem to explore it

I tried several reboot of pc and nas

double ckecked that host file is clean

flushed dns via prompt command and checked it and no entry is found

nas switched on 1 hour ago....

maybe i need to restart also the router ?

[Roby77]

Hi,
I resolve with the Qnap Support, i change the SMB version to 2.1

strange that my advanced options are different

https://s7.postimg.org/kli17ya3v/dns_entry.jpg

i don't have a menù to change smb version ( i already enabled smb 3.0

[schumaku]

strange that my advanced options are different ...i don't have a menù to change smb version ( i already enabled smb 3.0

Your Marvell Kirkwood based NAS is a CAT1 NAS which does not have this option in the controls, only the CAT2 ones have. when you check docs.qnap.com there are two columns, left CAT1, right CAT2.

I resolve with the Qnap Support, i change the SMB version to 2.1

Ready like a solution to a very specific, not further explained issue. From a scope of >1000 clients - most Windows 10 and more or less current mac OS systems - all work perfect on SMB 3.0 max protocol version.