Hey all, i was just notified that the recent Win 10 update, KB5001330 shuts off SMB1 on Windows 10.
So any VFP apps on file shares out there on servers that are using SMB1 might be affected.
https://support.microsoft.com/en-us/topic/april-13-2021-kb5001330-os-builds-...
https://www.reddit.com/r/msp/comments/mqpb1r/kb5001330_blocking_access_to_ne...
What do any experts on SMB protocol say/recommend for this situation?
Philip B. Vicksburg, MI
Hi Phillip,
What do any experts on SMB protocol say/recommend for this situation?
As strange as this might sound.... The most reliable results we recently had with Ubuntu as the server instead of Windows. With Ubuntu you can entirely disable all caching and all oplocks which both are the reasons for the problems we have in VFP. Windows doesn't disable all of them, even if you ask nicely.
For Windows here's my current set of registry settings that must be applied to the server and the client and requires a reboot of both when making any changes.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters DisableLeasing DWORD 1 EnableOplocks DWORD 0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters CacheFileTimeout DWORD 0 DirectoryCacheLifetime DWORD 0 DormantDirectoryTimeout DWORD 1 DormantFileLimit DWORD 0 FileInfoCacheLifetime DWORD 0 FileNotFoundCacheLifetime DWORD 0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Parameters OplocksDisabled DWORD 1
If you make these changes you are removing all the performance benefits of SMB3 for *all* applications on workstations and server, including file copying etc.
Hi Alan,
If you make these changes you are removing all the performance benefits of SMB3 for *all* applications on workstations and server, including file copying etc.
Yes, that's true. It's a matter of priorities, I'd say: You can have correct data, or you can get data fast.
We recommend terminal services with data stored locally on the terminal server or remotely on an iSCSI storage. For extra redundancy we recommend using terminal server in a virtual environment with redundant servers and redundant storage. But usually that advice is being ignored. <shrug>
Yes, that's true. It's a matter of priorities, I'd say: You can have correct data, or you can get data fast.
Even when the issues that occurred in 2018 Windows 10 1809 (IIRC) aren't a problem any more (in my experience at least) ?
Also if you are running recent Windows 10 and Server 2019 you can set UseWriteThrough on the server on a per-share basis, so if you really want writes to your VFP data to go straight to disk at all times then you can do that for your VFP share without crippling everything else on the network.
https://techcommunity.microsoft.com/t5/storage-at-microsoft/controlling-writ...
Even when the issues that occurred in 2018 Windows 10 1809 (IIRC) aren't a problem any more (in my experience at least) ?
My experience differs from yours. We have more issues with SMB every year unless oplock and caching is disabled. And even then we sometimes run into corruption issues that look like SMB problems.
UseWriteThrough doesn't solve this issue, because corruption happens due to client side caching caused by oplocks.
Hi Christof,
Is there a word missing from the key below (before Parameters)?
Peter
On 14/04/2021 16:54, Christof Wollenhaupt wrote:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Parameters OplocksDisabled DWORD 1
This communication is intended for the person or organisation to whom it is addressed. The contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email.
www.whisperingsmith.com
Whispering Smith Ltd Head Office:61 Great Ducie Street, Manchester M3 1RR. Tel:0161 831 3700 Fax:0161 831 3715
London Office: 101 St. Martin's Lane,London, WC2N 4AZ Tel:0207 299 7960
My guess is he meant this:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters
Frank.
Frank Cazabon
On 15/04/2021 6:53 am, Peter Cushing wrote:
Hi Christof,
Is there a word missing from the key below (before Parameters)?
Peter
On 14/04/2021 16:54, Christof Wollenhaupt wrote:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Parameters OplocksDisabled DWORD 1
This communication is intended for the person or organisation to whom it is addressed. The contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email.
www.whisperingsmith.com
Whispering Smith Ltd Head Office:61 Great Ducie Street, Manchester M3 1RR. Tel:0161 831 3700 Fax:0161 831 3715
London Office: 101 St. Martin's Lane,London, WC2N 4AZ Tel:0207 299 7960
[excessive quoting removed by server]
SMB1 is very slow, very insecure, and deprecated since 2014. They removed it from servers in 2017 IIRC.
What do any experts on SMB protocol say/recommend for this situation?
In general, don't worry about it IMO. Every 5-10 years or so MS will update something in SMB and break it for applications like VFP and Access. The last of these flaps was in 2018, whereby updates were not getting written straight away in VFP, and the database file was getting corrupted in Access. At the time affected customers had to set one or all of FileInfoCacheLifetime, FileNotFoundCacheLifetime and DirectoryCacheLifetime to zero on problem workstations. MS seem to have fixed the problem in subsequent releases of Windows 10.
Hi Philip,
I am no expert, but here is an article that helped the IT people at one of our customers.
https://www.windowscentral.com/how-access-files-network-devices-using-smbv1-...
Rick White Light Computing, Inc.
www.whitelightcomputing.com
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Philip Borkholder Sent: April 14, 2021 11:42 AM To: profoxtech@leafe.com Subject: File Server Sharing SMB1: W10 Update KB5001330 shuts off SMB1
Hey all, i was just notified that the recent Win 10 update, KB5001330 shuts off SMB1 on Windows 10.
So any VFP apps on file shares out there on servers that are using SMB1 might be affected.
https://support.microsoft.com/en-us/topic/april-13-2021-kb5001330-os-builds-... 42f-d67fec538490
https://www.reddit.com/r/msp/comments/mqpb1r/kb5001330_blocking_access_to_ne...
What do any experts on SMB protocol say/recommend for this situation?
Philip B. Vicksburg, MI
[excessive quoting removed by server]
-
Alan Bourke -
Christof Wollenhaupt -
Frank Cazabon -
Peter Cushing -
Philip Borkholder -
Rick Schummer