Bug: Network page device folders can not be accessed (ERROR_BAD_NET_NAME)

[armadix]

Description

Steps To Reproduce

1. In VM install Windows10 or Windows11
2. In the VM go to virtual machine settings and in the options tab shared folder to enabled
3. In the Folder sharing select alawasy enabled and add folders from host sample c:\xampp or c:\temp
4. then click ok to save settings
5. Run VM windows10 or Windows 11
6. Install classic File 4.0
7. Run File 4.0 then in the left pane select Network
8. Under Network select vmware-host this will show Network folder error or ERROR_BAD_NET_NAME

Files Version

4.0.0.0

Windows Version

10.0.19045.6216

User ID

No response

Log File

[Josh65-2201]

Thanks for the report, in future please don't make your title the description and upload the log file, not copy and paste the text.

[Josh65-2201]

@armadix Can you see if this is still an issue in the preview version. https://files.community/download

[jasiekmiko]

I have a similar issue where I can't access a samba share on my local network when using Files. I have the network location mapped as a disk and can access it fine using FileExplorer. In Files I can see it under the Discs section on the left-hand-side menu, but when I click it I receive the ERROR_BAD_NET_NAME error.

debug.log

I've just installed the preview version and the problem persists