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

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?

pfsense had tracking of the gateway built in, check your router to see if it already has something.