TrueNAS Scale (updated) and 3 Windows 11 computers hooked up to the same Mikrotik network switch. Initially used DHCP and all 3 computers could access everything. Tried fixed IP and nothing worked. Switched back to DHCP. NAS shows: “The web user interface is at 192.168.50.55”. My Asus router shows it at 192.168.50.55 (Router gateway is 192.168.50.1). I can access web interface and files from one of the 3 Windows computers but not from the other two. All 3 are set to “private network” and static IPs (192.168.50.6, 8 and 11) with same gateway (192.168.50.1) and DNS.
Accessing 192.168.50.55 from any browser from 2 of the machines gives me nothing “Can’t reach this page…” but no issues with the third computer.
File manager shows on the one computer “TRUENAS” and all the datasets and files (fully accessible) and on the other 2 desktops: it doesn’t show under Network but if I go directly to the IP (\\192.168.50.55) it will show me the datasets and the directories in one dataset (still not the files) but not the directories from the other 2 datasets.
I went into Windows credentialing manager and reset credentials and when I try to log in to the IP it does not accept my truenas_admin logon and password or my user logon and password.
So I have 1 computer that works perfectly well and has full access to web interface and all files and 2 computers that cannot access anything.
This is very frustrating as in the beginning (before tinkering) and I was using DHCP, everything was fine. I then tried static IP and after going back to DHCP, I can access the NAS only through one computer and not the other two.
Somehow all my permissions and credentials got scrambled up.
Did you possibly mess up the prefix lengths / subnet masks of the system involved? Are they all /24 or 255.255.255.0 - or, if different from this most common value, are they all the same?
Well, did you try to reboot the boxes? Windows is Windows…
Also, could it be that there are multiple network cards, and you have accidentally changed settings of another one? Another possibility from top of my mind is a firewall and/or VPN - if you (or your employer if this is a company one) enforces one or both, accessing of the local network is not always possible.
They are all at 192.168.50.X, 255.255.255.0 GW: 192.168.50.1.
The interesting part is that the one computer that can access everything has also some IP6 values although I have only IP4 checked off (as if there was some IP6 in the past and Windows kept them somehow?).
Rebooted everything, still the same. Activated on one of the computers IP6, TrueNAS doesn’t show up. I went to file manager and did \\192.168.50.55 and it asked for login credentials. My “truenas_adnmin” didn’t work but my own login worked and showed me the datasets but not the directories and files. Could I have screwed up permissions in TrueNAS?
If you get to the Web GUI from one machine and not from the other two, that needs to be solved first. There is an access control for the Web/API specifically (System / Advanced / Allowed IP Addresses), and also for the shares themselves (three dots on the share / Edit / Advanced Options / Hosts allow or deny), you’d probably remember playing with that.
Are you 100% sure that there is no duplicate IP in your network?
That’s normal, the user needs to be enabled for SMB and truenas_admin is by default not.
Ping between all systems needs to work. Assuming you set the Windows network to “home” or “company” (or similar - don’t remember from the top of my head, because I am not a Windows guy), not “public”.
Before you solved that and you can access the web UI from each Windows PC, there is no use mucking about users and permissions and stuff.
You have a network issue.
Wired connections throughout? If wireless, possibly “client isolation” active on your AP?
Everything wired. Cannot figure out why one Windows 11 PC can do everything and the other two cannot when all settings are the same. I tried to change from static IP to DHCP, turning on IP6.. no difference.
I went to Allowed IP: it was empty. I added the IPs of all 3 desktops, no difference.
I went to all SMB shares to make sure user “sgunes” is allowed to do everything, no change.
Still stumped with one desktop being able to do everything and the other ones unable.
I tried this: “Use “Start->Run” and type in “gpedit.msc” in the “Run” dialog box. A “Group Policy” window will open.
Click down to “Local Computer Policy → Computer Configuration → Windows Settings → Security Settings → Local Policies → Security Options.
Find the policy “Network Security: LAN Manager authentication level”.
Right click on this policy and choose “Properties”.
Choose “Send NTLMv2 response only/refuse LM & NTLM”.
Click OK and confirm the setting change.
Close the “Group Policy” window.” from community/threads/windows-cant-connect-to-smb-share.102736/ (cannot post links) and changed Group Policy, still no change.
Why are you messing around with Group Policies? Please read what people are writing in trying to help you. You change/try too many things at once. One. Problem. At. A. Time.
Now, as pmh already said, the first step is to see if all machines can see each other. I assume you know how to ping on windows. Try pinging your TrueNAS from all machines. What happens?
Then try to ping all machines from all machines. What happens?
Then try to ping all machines from TrueNAS. What happens?
I can ping all 3 machines from the NAS (.2ms), the 2 desktops that cannot access the NAS have 100% packet loss. The one desktop that can do everything has no packet loss (.2ms).
The NTLMv2 is related to authentication and logins for the SMB protocols. Altering these are most effective done through Group Policy, as this typically isn’t visible in the normal control panel.
With certain changes, may be trying to change authentication (depending on what version of Windows is being used by the clients). Also what OS and version is on the 1 working client computer?
Are the hostnames unique, if not in a clustered environment?
All three hosts can ping each other without problems.
As for why 2 cannot ping the NAS I am now looking into the network adapter settings to see if there is a difference between the one who can and the two who cannot connect to the NAS.
