We have software that is written in visual foxpro and some of our clients have been getting corrupted index's and missing records and from past experiences we've found that OPLOCKS is the cause of these issues. To test if this is really is the issue we turn off OPLOCKS on SMB1 and disable SMB2/3(because there is no way to just disable OPLOCKS on SMB2 or 3) on the computer that is serving the data. We've recently just ran into the issue where if a client has both a Windows 8.1 computer acting as the server and a Windows 8.1 as a workstation when we disable SMB2/3 on the Windows 8.1 that acts like a server the Windows 8.1 workstation can no longer access the file share on the server through the \\computername\share. We can still access the file share from computers that are Windows 7 and lower. I also made sure the SMB1 client is enable on the workstation.
Here is how I disabled OPLOCKS and SMB2/3 on the server:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\EnableOplocks = 0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\SMB2 = 0
On the workstation I made sure SMB1 client was enable by running this command:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsisc.exe config mrxsmb10 start= auto
Is there something I'm missing that is causing file sharing not to work on just SMB1 with Win8 to Win8 setup?