this post was submitted on 18 Mar 2024
11 points (100.0% liked)
techsupport
2468 readers
1 users here now
The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.
If something works or if you find a solution to your problem let us know it will be greatly apreciated.
Rules: instance rules + stay on topic
Partnered communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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?
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
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