Unable to access shared folders since firmware 4.3.3 update

[3rdparty]

@Roby77 can you email or post ticket number so I can ask my ticket to be cross referenced to yours? 3rdparty at gmail thx

[mydjtl]

This worked for me

http://docs.qnap.com/nas/4.2/SMB/en/ind ... tarted.htm

[Roby77]

@Roby77 can you email or post ticket number so I can ask my ticket to be cross referenced to yours? 3rdparty at gmail thx

Hi,
TBK-342-43301

i also sent an email

[scsirob]

So... Has anyone heard from support anymore? Or has QNAP given up on this issue?
If so, perhaps they can arrange some Synology coupons for us?

[kickbackpunk]

Haven't heard a peep.. from support. I finally had to abandon my TS-453a and get an equivalent Synology NAS to get back to work and the Synology is working great. Although I still prefer to use the QNAP.

[bushpig]

I'm not sure if this is the same problem but this information might be useful for someone.

I normally access my NAS from windows 7 and an Android box running Kodi which connects via SMB. I have a mapped network drive on the windows 7 box setup as \\[NAS servername]\[shared folder name] and the SMB connection from the Kodi box uses the same format.

After upgrading from 4.2.0 to 4.3.3 this morning everything stopped working! In the end I found that the Workgroup on the NAS no longer matched the Workgroup on my PC or Kodi box. This setting is found in Control Panel > Network & File Services > Win/Mac/NFS > Microsoft Networking. I believe that the upgrade changed it's previous value to NAS. Once I had set the Workgroup value to match what the other devices were using everything started working again.

I hope this helps someone out.

[effetredici]

New firmware 20170727-4.3.3.0262

[billmars]

This setting is found in Control Panel > Network & File Services > Win/Mac/NFS > Microsoft Networking. I believe that the upgrade changed it's previous value to NAS. Once I had set the Workgroup value to match what the other devices were using everything started working again.

This is not the case with me. My workgroup name has not been changed and I am still having this problem.
I suspect if you reboot your NAS the problem will reappear, (if it is, indeed, the same problem as others have on this thread).
I have had two tickets for this, neither of which has resulted in any remedy.

[scsirob]

New firmware 20170727-4.3.3.0262

QNAP support replied to me that this firmware version will be released today, and should have a fix for this longstanding issue.
Fingers crossed..

[etn777]

New firmware 4.3.3.0262 installed TS-212.
Issue seems to be fixed till now.
Fingers crossed

[scsirob]

Yup. Issue indeed seems to be fixed. The nmbd daemon still terminates after 5 minutes but a new instance (under control of daemon_mgr) starts right up.

Code: Select all

[~] # ps -ef | grep mbd
 4124 admin           Z   [nmbd]
 4302 admin           Z   [nmbd]
 4709 admin           Z   [nmbd]
 6883 admin       676 S   /usr/local/samba/sbin/smbd -l /var/log -D -s /etc/config/smb.conf
 6887 admin       464 S   /usr/local/samba/sbin/smbd -l /var/log -D -s /etc/config/smb.conf
 6888 admin       540 S   /usr/local/samba/sbin/smbd -l /var/log -D -s /etc/config/smb.conf
 6923 admin       532 S   /usr/local/samba/sbin/smbd -l /var/log -D -s /etc/config/smb.conf
 6962 admin       860 S   /usr/local/samba/sbin/nmbd -l /var/log -D -s /etc/config/smb.conf
14490 admin       576 S   grep mbd
[~] # tail -f /var/log/log.nmbd
[2017/07/30 21:58:44.553925,  0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
  *****

  Samba name server NASTER is now a local master browser for workgroup HOEVELAKEN on subnet 192.168.1.9

  *****
[2017/07/30 21:58:44.646101,  0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name HOEVELAKEN<1b> for the workgroup HOEVELAKEN.
  Unable to sync browse lists in this workgroup.
[2017/07/30 22:03:33.598405,  0] ../source3/nmbd/nmbd.c:58(terminate)
  Got SIGTERM: going down...
[2017/07/30 22:03:41.202366,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'nmbd' finished starting up and ready to serve connections
^C
[~] # ps -ef | grep mbd
 6883 admin       512 S   /usr/local/samba/sbin/smbd -l /var/log -D -s /etc/config/smb.conf
 6887 admin       384 S   /usr/local/samba/sbin/smbd -l /var/log -D -s /etc/config/smb.conf
 6888 admin       412 S   /usr/local/samba/sbin/smbd -l /var/log -D -s /etc/config/smb.conf
 6923 admin       444 S   /usr/local/samba/sbin/smbd -l /var/log -D -s /etc/config/smb.conf
14908 admin      1732 S   /usr/local/samba/sbin/nmbd -l /var/log -D -s /etc/config/smb.conf
15464 admin       576 S   grep mbd

Note the new PID for nmbd in the second list. Issue is fixed for me!

[palmerac]

Yup. Issue indeed seems to be fixed. The nmbd daemon still terminates after 5 minutes but a new instance (under control of daemon_mgr) starts right up...

Note the new PID for nmbd in the second list. Issue is fixed for me!

Hey, scsirob -

Before or after upgrading to the new firmware, will it be necessary for you and me to un-do the temporary fix that Alex implemented on our systems preventing the hand-over of the early-start nmbd?

[scsirob]

Hi palmerac,

I wondered about that too, but I have not removed any of the modifications that Alex made and applied the new firmware as-is.

[Roby77]

Today i received this email

. Can you please update your NAS to the latest Firmware release (QTS 4.3.3.0262) available today and let me know if the issue is solved.

Thanks for your help

Can't try cause i'm on holiday until 5 september

[kickbackpunk]

4.3.3.0262 Does seem to be working, I am no longer having issues connecting to shares after updating.