Windows Update killed access to share

[speed41ae]

Updated Windows 10 workstations lost access to my freenas. Unupdated workstations work file. I am uninstalling updates to see if I can figure which one broke my access.

 

[speed41ae]

It looks like KB5001330 caused this issue.

 

[Samuel Tai]

Are you using root to access your shares?

 

[anodos]

What's output of testparm -s? Curious about share configuration.

 

[speed41ae]

Are you using root to access your shares?

No I am using guest access. I cannot even browse the Freenas using Windows explorer. An workstation that did not apply this weeks updates can still the Freenas without any issues.

 

[speed41ae]

What's output of testparm -s? Curious about share configuration.

I am not sure how do that.

 

[Samuel Tai]

This is due to Microsoft deprecating guest access from the client. See https://docs.microsoft.com/en-us/tr...g/guest-access-in-smb2-is-disabled-by-default.

You could try using gpedit.msc to set the GPO mentioned in the Microsoft KB article, and then rebooting the client.

 

[anodos]

I am not sure how do that.

SSH session is an option, but it may be as Samuel said, related to the deprecation of guest access in Windows clients.

 

[speed41ae]

This is due to Microsoft deprecating guest access from the client. See https://docs.microsoft.com/en-us/tr...g/guest-access-in-smb2-is-disabled-by-default.

You could try using gpedit.msc to set the GPO mentioned in the Microsoft KB article, and then rebooting the client.

This was already done.

1. Open the Local Group Policy Editor (gpedit.msc).
2. In the console tree, select Computer Configuration > Administrative Templates > Network > Lanman Workstation.
3. For the setting, right-click Enable insecure guest logons and select Edit.
4. Select Enabled and select OK.

 

[Samuel Tai]

OK, then if the Registry fix for guest access is already in place, then you may have to set a guest account in the SMB service other than the default of nobody, and change the ownership of all the files and directories in the share to match that non-default guest account.

On my system, I have the SMB service configured to use the plex account (UID 972, GID 972) as the guest account:

On my guest share, I configure guest access, and add guest only = yes to the share's Auxiliary Parameters:

Finally, in the dataset backing the share, I have everything owned by plex:plex:

Code:

root@raven:/mnt/main/media # ls -al
total 131
drwxr-xr-x    6 plex  plex     6 May 31 18:48 ./
drwxr-xr-x    9 root  wheel    9 Jan 30 17:16 ../
drwxr-xr-x   59 plex  plex    59 Sep 24  2020 Movies/
drwxr-xr-x   43 plex  plex    43 Aug 17  2020 Music/
drwxr-xr-x  127 plex  plex   127 Jun  8 21:29 Photos/
drwxr-xr-x   16 plex  plex    16 Sep 24  2020 TV Shows/

 

[anodos]

I saw some reports of the guest access setting becoming effectively unset during some Windows updates. If windows update rollback fixed the issue, then it's somewhat implausible that it's related to guest settings on TN.