>I know, I know... it is old news... I (only) just noticed some of the items listed in the deprecated and removed features in Windows Server 2012 R2.
>http://technet.microsoft.com/en-us/library/dn303411.aspx
>
>> SMB
>> SMB 1.0 is deprecated. Once this is removed, systems running Windows XP or Windows Server 2003 (or older)
>> operating systems will not be able to access file shares. SMB 1.0 has been replaced by SMB 2.0 and newer
>> versions.
>
>By the way... does anybody remember if we ever got any final resolution for the problems with SMB2 that VFP was having (when accessing DBF tables through shares using SMB2)? Turning off SMB2 (to force a fallback to SMB 1.0) will not be something we could count on to work (not that that was ever a "solution" of any sort).

That's news to me... thanks for the heads-up.

The most recent development I've seen re: SMB 2.0 and higher is Message#1584660 . That implies the higher versions of SMB can remain enabled but with some of the parameters modified/disabled. BUT... in the following message Neil McDonald claims that doesn't work under heavy load. I get the impression he has environment(s) that hammer networked DBFs hard.

At one point I was going to get serious about testing for this bug. I went as far as setting up a couple of Win7 machines, ran Brandon Harker's test code for a while but the error didn't show up. It seems to require significant load to manifest. It would be great to have a reliable test to check 2.0, 2.1, 3.0, 3.02 and future versions.

OTOH with free or cheap DB backends available the use cases for networked DBFs are getting fewer and fewer.