redge76

NTLM is deprecated and has already been completely disabled on my corporate PC. For reference: https://www.neowin.net/news/microsoft-confirms-ntlm-is-dead-beyond-windows-11-24h2-and-server-2025/ This was done using the Group Policy Object (GPO) described here: https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/network-security-restrict-ntlm-outgoing-ntlm-traffic-to-remote-servers The policy "Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers" is set to "Deny all" on my machine. Unfortunately, I’m not the admin of my PC and can’t add any exceptions. As I understand it, this restriction will soon become the default for everyone, and I don’t see any easy workaround without having local admin rights. Has anyone found a solution? Kerberos authentication is not straightforward to implement.

Yea down for me too when I upgraded. I had a macvlan that down not work anymore.

So I had to use a custom NFS export to solve this. I export directly the /mnt/DiskName/share so I skip all the issues with /mnt/user

Hi, My current setup: Unraid 6.12.3 installed on an Asustor NAS. 3 "volumes" (the array with a single 3Tb HDD, a "small" 500gb ZFS mirror and a "big" 2tb ZFS mirror). A few Windows smb clients and an Ubuntu 22.04 server. The shares are exported with the "default" options. There is only a primary storage (secondary = none for ALL "volumes" event for the array). # exportfs -v | grep cub /mnt/user/cub-data 192.168.1.11(async,wdelay,hide,no_subtree_check,fsid=102,sec=sys,rw,secure,no_root_squash,no_all_squash) On client side, the mount looks like this: # grep cub-data /etc/fstab asus:/mnt/user/cub-data /asus/cub-data nfs rw 0 0 # mount -v | grep cub-data asus:/mnt/user/cub-data on /asus/cub-data type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.11,local_lock=none,addr=192.168.1.14) In dmesg on the server I got one instance of (I don't think it's related): [ 962.833521] nfsd: non-standard errno: -38 [ 962.833541] WARNING: CPU: 3 PID: 8235 at fs/nfsd/nfsproc.c:909 nfserrno+0x45/0x51 [nfsd] If I stop the array, I get the following on client: root@cub:/asus# cd /asus/cub-data -bash: cd: /asus/cub-data: Permission denied in dmesg: [ 1491.418450] NFS: state manager: check lease failed on NFSv4 server asus with error 13 [ 1492.438333] NFS: state manager: check lease failed on NFSv4 server asus with error 13 When I restart the array (of I restart the unraid server), I get the following on client: root@cub:/asus/cub-data# cd /asus/cub-data root@cub:/asus/cub-data# ls ls: cannot open directory '.': Stale file handle #dmesg [ 1883.562037] NFS: server asus error: fileid changed fsid 0:58: expected fileid 0x34000000000022, got 0x3a000000000022 But If I change to a subdirectory of the shared folder, it works: # cd /asus/cub-data/dokuwiki # ls docker-compose.yml dokuwiki_data (files in the directory...) I can correct the issue with mount /asus/cub-data ; umount /asus/cub-data So I guess the issue is that the /mnt/user/cub-data directory on the server is a FUSE "directory". But how is it possible that I'm the only one with this issue ? What am I doing wrong ? Is there a way to force an exclusive share so that it is possible to bypass shfs ? I saw the note in the release notes of 6.12.0 about NFS & exclusive shares. asus-diagnostics-20230813-2359.zip

Came here to complain about this too. I could not beleive I had to stop the array just to change a small configuration setting. Stopping the array is very disruptive and should be avoided.