>>>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.
>>
>>SMB2 has, IMO, effectively killed the file sharing paradigm. I'd rather invest a couple of weeks to make sure my app works with the currently available DB than looking for patches to patch what Microsoft just won't.
>>
>>Specially in an area where you don't have the freedom to change the settings and be sure they won't be overwritten on next reboot/update/full moon.
>>
>>I just wonder how are the Access, Paradox, Clarion and other guys coping with this. I guess they also have their ways to hook into ODBC.
>
>Windows 8 and Server 2012 use SMB 3.0 . I thought somebody here did some testing with this?

Then there's Windows 8.1 and Server 2012 R2, which use SMB 3.02 ...

The message I linked in my earlier post is the most recent info I've seen, but NeilM claims it doesn't work (but doesn't say what/how he tested).

That's the whole problem with this issue, AFAIK there's no Wiki or other centralized, definitive information that describes:

- Repro code and test environment(s)
- Grid of test results e.g. "Server" OS - Client OS - Pass or Fail, so end users can quickly figure out if their environments may be affected. Ideally should include SPs or Releases e.g. Win7 SP1, Server 2012 R2 etc.
- Potential workarounds and if they have any effect (ideally, re-test the grid)
- Diagnostics

Regarding workarounds, Dragan is right - there's no guarantee that installation of a future Windows Update, Service Pack etc. won't set workarounds back to default settings. They're inherently fragile.

From the POV of a sysadmin I'm very reluctant to mess with protocol tuning parameters - or turn off protocols entirely i.e. disabling SMB2 as has been suggested. For my own reference http://support.microsoft.com/kb/2696547

UPDATE: there may be a different way to approach this. Suppose you have a Windows 8.1 client talking to a Server 2012 R2 server. By default they will communicate via SMB 3.02, however at this time SMB 1.0 is still supported. I wonder if it's possible to establish a new connection and specify that it be SMB 1.0, then use that for a file-server app?

Something like that would need to be baked in to an app, or a launcher but it would at least give control of SMB protocol version back to the app, and only for that app.