>>Hi Kevin:
>>
>>Since the last time I answered, I've found new info that may be useful to your case.
>>
>>Disabling SMB2/3 may have bad secondary effects. I've read that the only thing that needs to be configured are the clients.
>>
>>Look at this:
>>
>>http://www.pcwizardsinc.com/home/visualfoxprosqlerror2066corruptedindexes
>>
>>Regards.-
>
>From the article: "However, disabling 2 and 3 has the side effect of breaking 2012 File shares through drive letter mapping. "
>
>We did have problem with shares with Windows 8.1 (8.0 worked fine) that we recently solved, but it was not related to SMB at all, although at first we thought it was because we do use SMB2 and SMB3, but... it turns out the Microsoft in its wisdom changed a default setting (from update to replace) when you map a share thru a policy, I cannot find the original article that our network admin found, but here you can read about this http://arstechnica.com/civis/viewtopic.php?f=17&t=1233859
>
>By the way, this is the output of Get-SmbConnection in my computer, and we have more than 200 users of our FoxPro applications (using hundreds of tables, not SQL).
>
>

>PS C:\WINDOWS\system32> Get-SmbConnection
>
>ServerName          ShareName           UserName            Credential       Dialect             NumOpens
>----------          ---------           --------            ----------       -------             --------
>**************      IPC$                **************      **************   2.10                1
>**************      APPS                **************      **************   2.02                2
>**************      APPS                **************      **************   2.02                1
>**************      mis                 **************      **************   3.00                1
>**************      shares              **************      **************   3.00                1
>**************      USERS               **************      **************   3.00                3
>

Hi Hugo:

That's why the same article says that the solution is not disabling SMB2/3 on server, but on clients!