I believe MS regards itself as a serious networking company. I would expect if they introduce a new network protocol, or a new version of an existing one, it would be subject to a huge matrix of tests with various products, both MS and otherwise.

The SMB2 issue arose with the introduction of Windows Vista and the original version of Server 2008 (not R2). At the time VFP was still an active MS product, and Access remains so to this day.

Regardless of whatever testing was done, the fact remains there are one or more bugs with SMB2 when used with file-based databases. The kindest explanation is the test matrix did not sufficiently test those products, so they were not found. A less palatable explanation is the bug(s) were found, but MS chose to do nothing about them.

You seem to have insider information not available to the rest of us. Could you please let us know the true explanation for the problems with SMB2?

>You obviously don't know what Microsoft does to test Windows. There is no lack of testing with regards to SMB2 or 3.
>
>>You are aware of the SMB2 issue with VFP, Access and other ISAM file-based databases? It will likely never be fixed. See the thread http://www.levelextreme.com/DataEntryThreadView.aspx?ID=1430067
>>
>>Also, Michel Fournier, the owner/operator of the UT, found that the latest available VFP OLEDB provider is not reliable under load. After much back-and-forth with MS, that's another issue that will not be fixed. Arguably, this shouldn't be too much of a problem because OLEDB is being deprecated by MS. But, the situation with ODBC is even worse, the latest driver only supports VFP6, and none of the data/database changes made since then are supported.
>>
>>Interop with 64-bit apps is challenging. Might not be a big problem now but it'll only get worse.
>>
>>MS is not so much actively trying to kill file-based databases, instead it's neglect and/or lack of testing. SMB3 is coming out in Windows 8/Server 2012, both are still in RC. I don't know if anyone has set up an environment with these OSs for testing but chances are the community is going to have to do it, because MS probably won't.