>>Alaska Software claims to know the details of the problem and offers a patch that changes some SMB2/3 parameters without disabling the protocols entirely: http://www.alaska-software.com/fixes/smb2/overview.shtm
>>
>>In a perfect world yes, we would all be running against an RDBMS backend. However, if VFP tables are still being used I believe the Alaska Software patch is a good place to start.
>
>Maybe. There's no guarantee that the next tuesday's patch won't revert those values behind admin's back. We've had reports from Brandon, IIRC, that such things were happening. Actually, no setting is safe in Windowses - you may put it any way you want, but it's quite possible that some checking mechanism would detect a setting it doesn't like and set it differently.

True. However, according to the link the patch gets applied to workstations, not server(s). If the user running a VFP app has enough local privileges, the app could check those registry values at startup and warn if they're not set as expected.