VLC’s local-network browser depends on reaching the relevant server on the local network. A guest Wi-Fi network or device-isolation policy can allow internet access while preventing access to a household NAS. Check local reachability before changing the media player’s codec settings. Discovery, connection and file authentication are separate stages. Establish that the intended devices may communicate locally, then check that the server is awake and the share is available before investigating passwords or playback decoding.
Separate internet and local access
Being able to browse the web does not prove that two household devices may communicate. Router policies can intentionally separate guests from private storage. Compare the phone or television's active network with the NAS connection, including whether either uses a guest network. Two devices can reach the internet through the same router while being isolated from one another. Use the intended trusted household network rather than broadly removing network protections, and confirm that access is appropriate for the people using the viewing device.
Verify the server itself
Make sure the NAS or computer is awake and sharing the intended folder. A sleeping server is not a VLC decoding problem. Check the server's power state and sharing configuration from a device authorised to manage it. If other permitted household clients also cannot open the share, start with the server or network rather than VLC's decoder. A visible server can still have an inaccessible folder or account restriction, so preserve the distinction between finding the machine and successfully reading its media files.
Use a documented manual entry if needed
Automatic discovery and direct connection are different mechanisms. If the network permits access, the app’s supported manual server entry may help identify whether discovery alone is failing. Use the app's supported server-entry controls with the server owner's confirmed address and share details. If direct access works while automatic browsing does not, discovery is the narrower issue. If the address cannot be reached, investigate the network path; if a password prompt appears, you have reached an authentication stage. None of these earlier steps is repaired by changing video hardware acceleration.
A practical sequence
0 of 3 steps completed on this page.
An example to work through
A phone on guest Wi-Fi can play internet media while remaining unable to see a NAS on the private household network. Move the phone to the authorised private network and check the server is awake. If manual access works but discovery remains absent, report that distinction rather than changing the media decoder or entering streaming-provider credentials into a NAS prompt.
Questions about this topic
Will hardware acceleration make a hidden NAS appear?
No. Decoding and network discovery are separate stages.
Does every missing discovery result mean the files were deleted?
No. Reachability and server state should be checked first.
