OK, I know that i shouldn’t ask for help here most likely, but I am at a loss in getting this to work.
I have an HP Microserver - N36L to be exact, 16 GB RAM and a 1.5 GHz AMD Turon proc. I have 4 IDENTICAL 1 TB hard drives, 10k RPM enterprise level, installed. I created a pool and Windows file share, user account, etc… with a friend who is fairly familiar with TrueNas. I am running the most current build of TrueNAS, version CORE 13.0-U6.2. It worked perfect on his home network - then I took it home and when trying to access it using DHCP (or for that matter, anything) on Windows 11, it would proclaim my user or password is incorrect. I can log into it on Linux, however, just fine. I had my friend check ALL of my networking settings, all my shares, he said it should have worked based off what he could see. We must have tried for 3 hours yesterday - even completely started over with a fresh install of TrueNAS CORE 13.0-U6.2 and even the TrueNAS CORE 13.3-RELEASE to see if it was a possible bug. No luck. Tried adjusting a few settings in my router to see if it was possibly the culprit - with no luck. I have had several FreeNAS systems running in the past but have never had this much trouble getting Windows 11 to connect to a NAS system.
Are there any other settings within Windows that could be the issue? I know for a fact I CAN see the TrueNAS unit within Network Neighborhood - it just rejects my user/password when i give it.
Hopefully this makes sense to you all, I am by no means a networking guy. Please let me know if i need to collaberate on anything.
Hi, i think the problem can be that your Windows PC is using NTLMv1, probably you will need to set NTLMv2 on security settings.
Just for be 100% sure, a quick test can be to enable NTLMv1 only for now on your SMB share, and test connection… if It works you can apply the change on the Win PC and remove the NTLMv1 access from SMB
Ive also had issues where windows wont map more than one smb with the same common name and had to use the ip\sharename rather than commonname\sharename
That is DNS. And the IP vs name is just chance ( the time you did a thing and the next time ).
Make sure your TrueNAS name is the same in all settings of the NAS
Well, the fix according to microsoft was to use the IP address. Cannot remember the exact error, but when I researched it, the MS resolution was as I described.
I think i got the connecting to Windows issue resolved. The NTLMv2 was needing enabled on Windows 11. I enabled this, rebooted my computer and then it connected. However, now I get an “Invalid Handshake Agreement” message when connecting to it from Ubuntu. I just can’t make both systems happy. Go Figure.
Is that windows machine part of a domain by any chance?
In that case you can try this:
When you access the SMB share and windows asks you for the username & password
try entering the username in this format: TrueNasIP\SmbUsername
example:
user: 192.168.1.5\chris
password: WutG4782@
That allows you to use local credentials to access that network storage.
If you have tested the NTLMv1 compatibility on the SMB service, remove It and restart SMB. No way that the Windows client settings can impact other Ubuntu clients. Otherwise do the same check on those clients
