Cannot Access Win11 Shared Folder on Android (sh.itjust.works)

submitted 8 months ago* (last edited 8 months ago) by LazerDickMcCheese@sh.itjust.works to c/techsupport@lemmy.world

11 comments fedilink hide all child comments

The folders are accessible on every other device and SMB is enabled on the host machine. I'm trying to access hundreds of gigabytes of game roms via Retroarch when I'm out of the country so I'd appreciate an easier method if one exists, but I've ran through every troubleshooting guide I can find online, but the share folders still don't exist according to my phone. I've also tried 5 or 6 different file manager apps, but they all say the same thing

If someone sees this in the distant future, I'm still looking for a solution so please reach out.

top 11 comments

sorted by: hot top controversial new old

[-] WeirdAlex03@lemmy.zip 3 points 8 months ago

I've personally been used Cx File Explorer to locally access SMB-shared folders from a Win10 device and a OpenMediaVault-based NAS, without problem (neither accessible remotely so cant attest there)

What exactly is not working? Are you getting any usable error messages? If you're not out of the country yet, can you connect locally? Do other SMB shares work?

[-] LazerDickMcCheese@sh.itjust.works 1 points 8 months ago* (last edited 8 months ago)

So I have all of the devices connected through TailScale (for remote media server access) with a Pihole DNS. All of that works as intended, and my computers can share files between each other, but folders shared across my network aren't visible on my phone for some reason. The file manager that was recommended to me most recently was Material Files, but it isn't detecting my shared folders and plugging in the SMB info myself leads to a vague error.

I'll try CX and report back

"Could not log in to xxx.xxx.x.xxx with user xxxx" but my info is correct, copied and pasted to be sure

[-] ectofunk@lemmy.world 1 points 8 months ago* (last edited 8 months ago)

Maybe try hostname\username where hostname is the hostname of the server.

[-] LazerDickMcCheese@sh.itjust.works 1 points 8 months ago

Then I get a "SocketTimeoutError"

[-] WeirdAlex03@lemmy.zip 1 points 8 months ago

My guess would then be probably Tailscale or Pihole somehow interfering with that connection for some reason. Idk if you're able (or willing) to remove those from the equation, but that might help narrow things down. If you have access to another computer locally, maybe sharing a folder on that and gradually adding steps to make it closer to your target system until it stops working?

[-] drrodneymckay_@sh.itjust.works 2 points 8 months ago

are you using the hidden c$ shares ?

have you set the LocalAccountTokenFilterPolicy value properly ?

are you using a new version of the smb protocol ?

last immediate thought, are you trying to connect via name and having a dns issue?

[-] phanto@lemmy.ca 1 points 8 months ago

Upvote that last comment. I've had a couple shares only accessible by IP on a file explorer app I was using, way back when.

[-] LazerDickMcCheese@sh.itjust.works 1 points 8 months ago

I'm sorry in advance, but I don't know how to answer the first two questions...I'm using whichever protocol is default for Win11 (SMB2, I think). I've been trying to find the folder through an automated scan, then plugging the hostname and address in myself when nothing comes up

[-] drrodneymckay_@sh.itjust.works 1 points 8 months ago

So i just encountered something very close to this myself. I've used SolidExplorer on my phone for a long time with many windows hosts and shares connected via smb without issue. I just purchased a Samsung Galaxy Tab s9fe and tried to bring my paths over with SolidExplorer's back and restore settings. Well it wouldn't connect from the tablet to most of the shares. Checking the source phone it wouldn't work there anymore either.

SolidExplorer offers settings to use SMB1 or SMB2/SMB3. but according to a comment I found it seems like that is more of a '2 and 3', not '2 or 3'. The comment said if only 3 is enabled on the server you will not be able to connect.

I've only tested this with a single win10 host so far, but force enabling SMB2 via registry key and restarting LanManServer service allows my phone to connect again.

https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=server