Prindl Valued Contributor.
Valued Contributor.

OES2018 SP1 DSFW SYSVOL access does not work with SMB 2 or SMB 3

I found out, that access to bigger policies on the SYSVOL is problematic on Windows 7 to Windows 10 PCs (and the equivalent server versions). This leads to not working policies, the inability to backup or save Group Policies from the mmc snapin and several other problems.

This does not happen, if you disable SMB2 and SMB3 on the Samba server via "server max protocol = NT1" in the smb.conf .

Downside of this solution is, that you have to enable the SMB 1.0 client on your Windows PCs and servers.

Labels (1)
1 Reply
Franz Sirl

Re: OES2018 SP1 DSFW SYSVOL access does not work with SMB 2 or SMB 3


I have reported this as SR#101251304101 and provided the requested traces. No feedback since then.

The whole issue can also be reproduced on Linux with "smbclient -m SMB1/2/3 //dsfw/sysvol" and then get a large GPO template file like inetres.admx "get \your.dsfw.domain\Policies\PolicyDefinitions\inetres.admx". This works with SMB1 and fails with SMB2/3: parallel_read returned NT_STATUS_IO_TIMEOUT.

Interestingly it works locally ("smbclient -m SMB3 //localhost/sysvol") on a DSFW server, but not from another DSFW server or with plain SLES12SP4 or SLES15SP1. Maybe a network timing issue?



The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.