>>A while back Brandon Harker posted some repro code here. I set up a test between a couple of Win7 computers, ran it for a while but the error did not show up.
>>
>>I seem to recall someone saying the test has to be run for some time, under considerable load for the problem to manifest.
>
>
>FYI - That code I wrote would expose the SMB2 ICE error in under 30 seconds every time I ran it. In most cases it would bonk in less than 10 seconds.

Can you elaborate on your test environment e.g.

- # of machines used
- real or VMs
- OSs / SP level(s)

From what I recall:

- Issue first found in Vista/SMB 2.0
- MS issued some kind of patch/hotfix that was supposed to fix it, but did not (or at least not completely)
- The issue has never been completely fixed, despite enhancements to SMB now at 3.02 (Win 8.1/Server 2012 R2). However it is not known how severe the problem still is i.e. whether things are more reliable with the newer versions of SMB compared to the earliest unpatched SMB 2.0 in Vista
- The Alaska Software .MSI ( http://www.alaska-software.com/fixes/smb2/overview.shtm ) "allegedly" fixes SMB 2.0+ so VFP and other file-server databases work reliably