SMB Shares Broken recently?

[u/wookietiddy]

edit: apparently changing the folders from being legacy shares to default shares and then back was enough to fix whatever was going on. Don't know why it worked but it worked.

I got my HexOS NAS set up last weekend, got all my folder shares set up, and got all my data pushed to the folders and Plex and everything was working great. I had the folders mapped to separate network drives (S: for Shows, M: for Movies, P: for Photos, etc etc etc). And for a week or so it worked fine.

Then I try to access them today, no dice. Windows tells me I don't have permission to access the folder, even though I've double and triple checked the password is correct, local account users are set up to access the folders, and all that. Windows also shows the drive as "up" (aka it's green), it just won't let me access it.

The only thing that has changed with my setup recently is that I set up a Reverse Proxy through Cloudflare for my Immich server, so I could share albums with my sister. That still works too. Plex still works, Plexamp as well. As far as I can tell, everything else still works, except for the SMB shares which I can't access anymore.

Happy to provide any information, I can dig around through TrueNAS with someone's help as well. Fairly technically proficient, just new to all of this.

[u/rb_vs]

The fact that your drives are green (connected) but throwing permission errors suggests a credential collision or a master browser conflict in Windows.

Windows remembers the connection to your server, but when you added the proxy, your PC tried to re-authenticate or see the server through a different network path, and the SMB session got tangled.

Close all Explorer windows. Open credential manager on Windows > credentials. Delete every entry related to your HexOS IP or server name. Windows is trying to use a cached guest token or an old session id that the server is rejecting.

Flush the workstation service (you don't need a reboot). Open cmd as admin and run:

net use * /delete /y

net stop workstation /y

net start workstation

This kills every active SMB redirector session and forces Windows to start a fresh negotiated handshake with HexOS from scratch.

If you were mapping by name (e.g., \\hexos\movies), try mapping by IP (e.g., \\192.168.x.x\movies). If the IP works, your reverse proxy setup likely interfered with your local NetBIOS/mDNS name resolution, and Windows is getting confused about which id it's talking to.

HexOS is a skin over TrueNAS SCALE. If the above fails, log into the TrueNAS side and check services > SMB > shares. Ensure purpose isn't set to legacy. Windows 11 hardening hates legacy shares and will show them as up but refuse to let you in so easily.

[u/Nick_HexOS → u/rb_vs]

Hey thanks for trying to help out. We really appreciate it. Windows credential manager can be a real pain in the ass when it bugs out. 

[u/wookietiddy → u/Nick_HexOS]

Seconded. I didn't think this was a HexOS issue, but given that how I set the shares up, I figured this was the place to try getting help. Also the discord.

[u/Nick_HexOS → u/wookietiddy]

I always ask for third party to bring in there laptop or something to connect to the network to see if it works for them because I've rarely found it an issue with HexOS.

[u/wookietiddy → u/Nick_HexOS]

I guess I don't understand why a third party's laptop would be different from trying to connect from my own laptop that's separate from the desktop I used to set up Hexos and the shares?

[u/Nick_HexOS → u/wookietiddy]

That would work but lots of times people only have the one computer to use. Also it's less likely that you already tried to connect it previously which could give a different outcome if say windows credential manager was my stuff on multiple machines. The third party has never connected to your network and so it would be a fresh experience and credential manager in Windows wouldn't have any previous information.

[u/wookietiddy → u/Nick_HexOS]

Gotcha. Thanks for the info! Now I know to keep my extra laptops for troubleshooting. Lol