SMB from Android to Win10 - error 0x80070035 - Path not found
▲
0
▼
Motivation: To get files from Android to my PC, I have some FTP server on the Android for long already, but it is not convenient: File manager on the PC is much better.
When the SMB server started, the phone appears on my PC, with Win10: OK.
But when I try to click this (just appeared) network source, in the FileExplorer, an error pops-up: Something like "0x80070035 - Path not found."
What is going on? ..is the root cause in the phone, or in the Win10?
Or is there another solution, possibly easier?
Settings:
port 1445, TCP
There is no "samba.conf" file, all of the server is set from GUI of the app.
And it is really unsure, what to set on the side of Win10..? I.e. FireWall..? I did some additional settings there to create a new rule to allow the TCP port 1445, but no effect.
..nor where is the root cause really: In the server (Android side), or in the Win10?
The rights I set on the Android Samba are 77x: read/write is the purpose. To empty my mobile, to move the files manually, (through the Win10) to my NAS.
I do not care about the user settings: Even "public" guest is enough in the moment, because it is for "LAN" only, and time connection/download/emptying. As a PoC. (In the future I might want to access the phone from my notebook even in non-home networks, but it would be another use case.)
I did not set any "starting folder": The server URL is just the preset \\SONYF5321 or \\192.168.2.179, as the app itself suggests. Does Win10 require any folder explicitly? It does not ask for it. Also, the server FS-root "\" should be enough, as the Android app states. (without any necessity to "root" the phone OS.) I have also tried to map the LAN-source as a LAN-disk, using \\192.168.2.179\storage\emulated\0, but again the same error, after a while of waiting.