Page 1 of 1

SMB and libdsm issues

Posted: 07 Mar 2017, 22:51
by loekf2
As some fruit company keeps failing to approve 3.x on tvOS, I wanted to give MrMc a try on my Shield:

- libdsm fails to see my two QNAP NAS devices (both running the latest firmware)
- when disabled it only sees my 1-drive NAS, which AFAIK is running an older SMB rev.
- my 4-drive NAS is only seen when I add its path manually (smb:// etc) with libdsm off

On tvOS and iOS libdsm works fine, but of course running an older version of MrMC.

Re: SMB and libdsm issues

Posted: 08 Mar 2017, 13:58
by davilla
Which QNAP and which fw version running on it. Both Amet and I have QNAPs and both flavors of smb seem fine. With both browse and zeroconfig.

Re: SMB and libdsm issues

Posted: 05 May 2017, 20:58
by loekf2
The issue popped up again, either after MrMC 3.0.3 on both tvOS and ShieldTV...or it's related to the latest QNAP firmware, 4.3.3 if I'm not mistaken.

I see timeout issues again and funny enough when use libdsm it keep asking for account settings. After you enter these, it just asks for them again.

Using libdsm, it also does not detect SMB drives.

Without libdsm it sees SMB drives but you get connection errors when the drive has to get out of sleep mode.

Just wondering which SMB level are using ? 3.0 or less ?

Re: SMB and libdsm issues

Posted: 16 May 2017, 20:15
by loekf2
davilla wrote: 08 Mar 2017, 13:58 Which QNAP and which fw version running on it. Both Amet and I have QNAPs and both flavors of smb seem fine. With both browse and zeroconfig.
It also shows up on the ATV4, but of course you are using the same codebase.

The QNAP NAS is running 4.3.3 with SMB rev 3 enabled.

Looks like I fixed it by changing the timeout to 12 secs, now even with libdsm enabled all looks ok. Zeroconfig also sees the NAS.