Hello! I’m new to the TrueNAS world and am currently setting up my first NAS as a personal project. I currently have SMB configured and set up to accept SMB1.0 and that allowed my laptop to connect to it.
The issue I’m having is that my desktop, which is hardwired via a switch that is connected to a router on the same network/subnet. The desktop cannot connect as it says windows credentials are incorrect no matter what password/username I use, I’ve even tried changing the password so that it would work and clearing my credentials manager, nothing has worked.
Any ideas on what I could do to remedy this?
SMB1.0 is waaaaaay out of date and riddled with security problems. I’m surprised there’s still an option to use it in TruesNAS, tbh. In Scale you have to explicitly enable it, and you’re warned against doing so.
MS dropped support for SMB1.0 in Windows on 2022, and you have to jump through some hoops to re-enable, which is probably why your desktop won’t connect (although you don’t say what version of Windows it’s running, I assume it’s relatively modern).
What OS is your laptop running that still supports SMB1.0?
Solution? Stop using SMB1.0 and I would imagine your Windows desktop will start connecting, but that may then stop your laptop working. Then you need to fix/update your laptop.
Thank you for replying so quickly!
Currently I’m running the most up-to-date versions of Windows 11 on my laptop (23H2 08-2024), I believe my desktop is on the same but I’m unsure. in the network and sharing center inside control panel there was SMB1.0 client and server in there (I enabled it when I saw some saying it was helping them) but that’s really good to know that I shouldn’t be using that!
Just incase though would there be anything else that my desktop would be missing to be able to access the nas? I got it working once before but I have 0% of a clue on how I managed to do that
UPDATE:
Updated my desktop and completely turned off SMB1.0 on both desktop and laptop, my laptop can still connect and ssh into the nas (for good measure), but my desktop still can’t connect, but can connect through ssh. Any thoughts?
Maybe incorrect credentials were cached?
With PowerShell or CMD, run this command to clear the cached credentials:
NET Use * /D /Y
Then reboot and try to connect the SMB share again.
I’ll give it a go!
UPDATE:
Unfortunately clearing the credentials did not work, whenever I ran the command I would get the “there are no credentials in this list” message. I tried rebooting thinking maybe it did work but unfortunately did not work. I do appreciate the idea though!
Any other thoughts?
