Bizarre issues trying to access NAS from Windows 11 computers

Hostnames are unique as they show up on one desktop.

The windows version for all 3 is 11 Pro 25H2, fully updated.

I checked the NIC settings, and they are the same on the one that works versus the other two. I even changed the NIC on one to see if it does make a difference, no change.
Now I cannot access one dataset from the host that was able to access it before, permissions look good. Will reboot the NAS.

@sgunes What version and product of TrueNAS? Is it from during the time of TrueNAS Core and TrueNAS Scale, or just TrueNAS Scale (aka Community and Enterprise)?

Community. 25.10.2.1. Goldeye.

I now suddenly lost access to one of the 3 datasets. Checked permissions: still supposed to have full control. Windows states that I do not have permission to access that one dataset…

Another thing is Windows likes to use the same account that is used for Logging into the OS on the client. Also what’s the network load like generally also any alerts from TrueNAS on its interface including TrueNAS Connect?

I can confirm now that it is a Windows 11 issue. I can access everything from my MacbookPro from the web interface to the files (except for one data set that I cannot access from anywhere).

So, something is rotten with the 2 Windows 11 Pro computers that I have to figure out. I uninstalled NordVPN on one (no difference). I have to keep looking.

If you have VPNs installed they might interfere. Even after uninstalling them.

I’d suggest as a first step to reset your network connections[1] on your Windows 11 machines (note the static IPs first so you can assign them again later):

Method 1: Reset network work adapters via the Settings app

This method offers the easiest system-wide process for restoring all network components to their factory settings—wiping all saved network accounts, static IP settings, custom DNS, VPN connections, and virtual network adapters for all users in a device.

  1. Press Win + I, then go to Network & Internet > Advanced network settings.

  2. Find and select Network reset on the right pane, then click the Reset now button.

  3. A prompt will pop up asking you to confirm the change; select Yes.

  4. Once the process is done, the system will automatically restart after a short delay.

Method 2: Reset network stack via Command Prompt

This method wipes key layers of the Windows network architecture without removing adapters or saved Wi-Fi profiles, helping end users stay connected even after a reset.

  1. Press Win + R, type cmd, and then press Ctrl + Shift + Enter.

  2. Execute the following commands in the correct sequence as outlined:

netsh winsock reset

netsh int ip reset

ipconfig /release

ipconfig /renew

ipconfig /flushdns

  1. Once you’re done, close the Command Prompt and restart your device.

  1. via Ninjaone, so I don’t have to type as much ↩︎

I just did the full reset and rebooted. Cannot access the NAS at the IP address (192.168.50.55). File manager shows all networked devices but not the TrueNAS. Typing the NAS IP in file manager shows me the three datasets but folders only in one. Clicking on folders does nothing.

Have you tried DHCP assigned IPs and making them static on the DHCP server? I’ve had similar issues before which I never satisfactory understood, but were fixed by this.

Forget this one for now. One step at a time. Make sure you can access the Web GUI from all clients. My bet is still on the VPN (as I suggested right in my first reply, you did not confirm you have one until 20 posts later). Was it ever installed on the machine that works (in other words, what known differences, however small, are there in the configuration of the machines working and not working)? If you go to Network Connections, how many do you see? Is there anything suggesting a TAP or VPN or virtual adapter or anything?

If so, the VPN was not uninstalled completely and the NordVPN support would be the best bet to start.

3 Likes

All three hosts have static IP 192.168.50.6 and 8 and 11. They are also set to static in the Asus router menu.

Regarding the VPN: Two computers do not have VPN (Windows Network interfaces only show Wi-Fi/Wired/Bluetooth and nothing else). One of the 2 computers can access everything and the other one cannot. The computer with NordVPN was able to access everything in the past, so I don’t think it is a VPN issue.

Out of desperation I turned off wired internet and switched to WiFi. Trying to log in I got “Access from this IP is not allowed”. I then added the WiFi IP to the advanced settings→ allowed IPs and I can access the web interface and the files!!! Somebody please make sense of this to me.

I tried this with the other host that couldn’t connect and the same result. The second I switched to WiFi, I could access everything.

I then connected the wired ethernet instead of the Mikrotik to the Omada (TP-Link) switch and no difference.

I compared the Wired Ethernet properties of the host that can access via wired ethernet with the other ones and even having identical settings under Control Panel→Network and Sharing Center→10G Ethernet (Aquantia)→Properties and made sure the same items were checked, and it made no difference.

I’m saying let the router assign the IP. This should be quick to test. How was IP assigned on your wifi interface?

I went to Settings→Network & Internet→Advanced Network Settings→Network Reset and now everything works on the two computers where nothing worked before.

All along it was a Windows 11 issue and not really a TrueNAS problem. Thanks everybody for their input.

2 Likes

If your issue is solved, please mark the post that most helped you in your opinion as solution so others can maybe find something helpful here.

Yes, this can happen in Windows when the network stack gets corrupted.

This usually shows a being able to ping everything, but DNS does not work (DNS setting correct, but the DNS system simply cannot reach the DNS server’s IP address).

I have only seen this in VMs. Can’t remember if it was due to a windows crash, installing newer virtio drivers, or installing software VPN nic adapters.

Next time, to save everybody’s time, basic network testing should be first!

Can each system ping the rest of the systems?
Can each system ping the Internet?

Shares, domain and policy issues mean NOTHING, until basic networking is assured.

3 Likes