unable to access my NAS using SMB from my android streaming device

[bocheh1]

Since upgrading on Monday to 3.3.2 I am unable to browse and access the files on my NAS. I have several Skystream android streaming boxes. A Skystream Pro, a Skystream 3 plus and a Skystream 2. The Skystream pro is running android 9 and is the unit for this topic. My skystream 3 plus and Skystream 2 are running old versions of VLC (3.1.6 and 3.3.1) and do not have this issue. When I select browsing,select local network,select My NAS, it says loading and never displays the folders. Eventually a message appears that says your input could not be opened. Before upgrading to 3.3.2 my folders would appear almost instantly. As the still do with my other two units. One thing that I noticed if I long press the open button my remote while i have selected my NAS device icon in the browser the following info is displayed the name of my server and under that smb// (name of my server). If I display that same info on my units that work properly the following info is displayed. The name of my server and under that smb//and then the ip address of server. not the name of the server. Is it possible to download 3.3.1 so I can continue running while this is corrected???
thanks
Hank

[tguillem]

Hello,

Thanks for the bug report. One users on iOS has the same issue. We could not reproduce it at VideoLan (but we will do our best to fix it)
Could you give us more information about your NAS ? Device, version. Do you know if your NAS is running Samba ? Could you give us your smb configuration on the server side.

[bocheh1]

NAS Synology DS420+ version 6.2.3-25426 update 2
Not familiar with samba I do not see any program with that name installed

SMB service enabled
maxmium SMB protocol SMB 3
miniumum SMB protocol SMB 2
transport encryption auto

let me know if you need anything else.
can you provide me a download link to 3.3.1??

[bocheh1]

when i browse my network with the units with the older versions of VLC and click on local network tab, when it opens there are two folders with the name of my NAS server. one is unable to load the file folders. the other instantly presents the folders contain on my server. the difference between these two folders is one contains the IP address of the server, the one that fails does not. my unit running the latest version of VLC has only one folder in the local network tab and it does not contain the IP address of the server. Do not know if this info helps or not. seems significate to me.

[hallergard]

What OS is your SMB server on? Is "minimum SMB protocol SMB 1" an option?

[bocheh1]

Synology NAS run DSM os.
Disk station Manager
SMB 1 is an option

[hallergard]

Try SMB1

[bocheh1]

I switched the minimum setting to SMB 1
Retried to access my shared drive on the server through the VLC browser. The 2nd host folder is now present and my shares appear when I open the folder in VLC.
I can access all files.

[Aza]

Could you please try with the latest beta and see if it's fixed?

[hallergard]

Just tried the latest beta. Works fine with my Linux SMB2 server, which requires user but accepts blank password. Does not work on my Windows SMB2 server, which is set up for anoymous access. VLC seems to require a user for SMB2.

[bocheh1]

my issue was resolved with a permissions setting in my NAS.

[bocheh1]

at your suggestion we changed the SMB setting min to SMB1 in The Nas.

[hallergard]

SMB1 yes, but think Aza wants feed back for SMB2/3 with latest beta

[bocheh1]

I will test it. What the link to the latest beta?

[hallergard]

http://get.videolan.org/testing/android/3.3.2-Beta-3/

[bocheh1]

I installed the Beta version and tested Nas access with the SMB minumum setting at SMB 1. everything worked fine. I then switched the SMB minummum setting to SMB 2 and reran test. VLC was unable to access my shares. browser displayed loading for several minutes and finally displayed error message unable to load.
switched back to SMB1 setting and was able to access shares immediately.

[Aza]

I was indeed talking about SMB2.
Thanks for the feedback @hallergard

[tguillem]

Hello @hallergard and @bocheh1

Could you test a debug version for me?
- VLC-Android-3.3.2-Beta-3-armv7.apk (armv7)
- VLC-Android-3.3.2-Beta-3-armv8.apk (arm64)
This is a debug build, it won't replace the VLC you installed from the store (the beta one), it will add a new android app, vlc-debug with a green cone.

I fixed the smb encrypt negotiation but I'm not sure this is the same issue you have. Anyway, this build is more verbose. Could you give me logs with "adb logcat" if it still fail?

Thanks a lot in advance for your feedback.

[hallergard]

On my 1 PC, 1 user, Local Network https://tinyurl.com/y7a7lsng I think passwords are overkill. But to get VLC to work with SMB2 on Windows 10, I gave up my resistance. Changed Windows 10 to user (=me) and password "blank" and used these for the VLC credentials. VLC now works with Windows 10, just like with Linux. Note that this is not anonymous login as the VLC SMB2 client requires a user!

[hallergard]

Tried the arm64 version and it works just as well as the store beta one. Have not found any difference in performance.

[bocheh1]

I tested the arm7 version with the SMB min setting at SMB2. the result was the same as the newest public release. unable to open and load share files.
I also tested the arm7 version with SMB min setting at SMB1. The result was it took 2 minutes to open and load my share files. Whereas the newest public release when set to SMB1 opens and loads my share instantly. I need instructions on how to gather the log files you ARE REQUESTING. I HAVE FORGOTTEN HOW TO DO SO.

[Aza]

To retrieve and share some logs, reproduce the issue and then go to: Settings > Advanced > Debug logs. Then share the logs with the sharing service you prefer (Google Drive, Dropbox, pastebin...).

[bocheh1]

There is no such setting under the advance tab.
For the green beta version you asked me to test.

[Aza]

You're right my bad. I didn't see that @tguillem sent you a debug version.
In the meantime, he made some more fixes and a new beta is available on the Play Store. It would be nice to see if it fixes the issue.

[bocheh1]

I will give it a shot!