The VideoLAN Forums

Hi,

Client:

– VLC for iOS 3.1.8 returns constant pinwheel. VLC for iOS 3.1.7, which introduced SMB 2 support was fine.

– Settings: Server=IP address, Port=blank, User: username only, Password: password. These all worked on VLC for iOS 3.1.7 but I've tried all variations I can think of, such as using Sever=computer name, Port=defined ports, User: prepending domain/computer, using inside and outside VPN.

Server:

– Windows Server 2008 R2 Enterprise running SMB 2.1.0 (I appreciate there's no canonical SMB, but Windows Server 2008 is the server platform which introduced SMB 2).

To emphasise, settings that worked on VLC for iOS 3.1.7 no longer work on VLC for iOS 3.1.8, and I can't find any that do.

Thanks

VLC 3.1.7, like most software (including macOS Finder and Windows Explorer) used to display list of top-level shares when you connect to a computer. e.g.:

server: computername

Would list top-level shared folders. But 3.1.8 just hangs with the constant spinning wheel (I think it hangs with the constant spinning wheel on all empty shared folders).

But it works if you specify a shared folder and the shared folder isn't empty e.g.:

server: computername/sharedfolder

A workaround, but I think this it is a new bug. e.g. most software, including the system ones specified and iOS apps like File Explorer, File Browser – and VLC itself before 3.1.8 – list top-level shared folders when you connect via computer name only

In addition to this:

If you specify the computer name in the format:

server: computername//

VLC 3.1.8 lists top level shared folders like VLC 3.1.7 used to.

BUT if you select any of these shared folders, it opens the folder only to re-list the top-level shared folders again, ad infinitum

What server is that?

I am having the same problem! But only on iOS, my android devices can connect fine!
I have an OpenVPN server running on my server (OpenWrt) to access my smb shares from outside.
My android clients auto detect and can access my smb shares directly through vlc player, either while beeing in my local network or while beeing connected to it via openvpn.

On iOS however VLC 3.1.8 auto detects the DLNA services and smb shares of my server (and windows PCs) while beeing directly connected via wifi.
I can access the DLNA shares fine, smb shares give me a infinite spinning circle for my server. (windows shares without user/pw work fine)
When connecting to my network from outside, vlc no longer detects the dlna or smb shares. It can still manually connect to my windows smb shares when specifying the IP.

Using any network file browser app for iOS I can connect to my OpenWrt and windows smb shares just fine. From outside and inside of my network.
My windows smb shares work without user/pw. My openwrt shares just need a username to be accessible.

What are your SMB servers? Windows?

As said in my post. One is running on my OpenWrt router and the other ones are windows servers.
Oh and the mentioned workaround isn't working for me.

Any news regarding this issue? I think it should be easy to reproduce.

Did you find a way to get rid of that? I have the same problem!

Help me understand how the version to download is 3.0.10, but this discussion is referencing 3.1.8?? What am I missing?
I received a new vulnerability report today stating VLC Media PLayer has an upgrade to version 3.2.8, but where's the download link?

Note that there are different numbering schemes on iOS and macOS. For the Mac, the latest version is 3.0.10 while for iOS, it is 3.2.8. The underlying libvlc version is the same.

Same problem here. The VLC iOS app on my iPhone is version 3.2.13.
I no longer can access SMB shared folders on ANY or my other Linux machines on my home WiFi LAN. Used to be VERY EASY to access with no problems, ever. No connection problems either using an iPad or Sony(Android OS) TV or iMac OSX or Windows 7 via home WiFi either. They ALL work just fine. The ONLY issue is connecting using the iPhone. IT''S B-R-O-K-E-N.

And NO ONE at VLC has ANY idea why this is occuring? It SHOULDN'T be this difficult. Any suggestions anyone? Help appreciated.

We have an idea why this is occurring and fixed it for the next update.

Just tried it. It works. It's FIXED. Thanks.

Glad it works!