June 2, 20224 yr Hi Some explanation is needed: I run a (Hansson) Nextcloud VM on VMWare Vsphere server. The server has a smb network share (called nextcloud) on my Unraid server. The Unraid SMB settings is set to use Active Directory. I have created a AD initial owner in AD (unraid_admin) and a AD initial group (UNRAID-DEFAULT-RW). In addiction, I have added a user called nc_admin that is actually used to map up the share from the Nextcloud VM. This works fine as long as I use Unraid v6.9.2. Using smbstatus, it looks like this: root@Unraid:~# smbstatus Samba version 4.12.14 PID Username Group Machine Protocol Version Encryption Signing ---------------------------------------------------------------------------------------------------------------------------------------- 5117 nc_admin unraid-nextcloud-rw 2c43:97e0:cbbd:c0ce:250:56ff:fe8b:7e3f (ipv6:2c43:97e0:cbbd:c0ce:250:56ff:fe8b:7e3f:58120) SMB3_02 - partial(AES-128-CMAC) Service pid Machine Connected at Encryption Signing --------------------------------------------------------------------------------------------- nextcloud 5117 2c43:97e0:cbbd:c0ce:250:56ff:fe8b:7e3f Sun May 29 12:19:01 PM 2022 CEST - - When I upgraded to Unraid 6.10, this stopped working, and smbstatus shows me nothing at all. I'm not able to map up the nextcloud share from a regular Windows PC either (using the nc_admin user). unraid_admin and Administrator is still able to map it, though. So the question is, are there any significant changes in SMB that causes this, or is it a bug? Thanks
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.