Communication between the RDP clients and the Terminal Server does not matter, that's not causing any corruption issues you're seeing. All the "action" is taking place on the TS.

Each RDP client is getting a separate session on the TS. Are these sessions accessing VFP tables/index files that are local to the TS machine, or on another server? If on another server, and communication between the TS and that other server is SMB2 you could get the problem.

If the VFP files are nominally local, is the "local" storage "normal" hard drive(s) or is it something like a SAN or a NAS device?

Even if the files are local to the TS machine, but you access them via mapped drive letters to shares (F: etc., or even via UNC), that is invoking the network redirector and may be bringing SMB2 into play. Can you test by putting tables in a subfolder of C: drive on the TS?

In case antivirus is interfering, you could try temporarily disabling it on the TS, or at least getting it to exclude VFP file types (including temp files in temp folders).

>Thank you.
>
>Users are running VFP9 application using RDP protocol through terminal server.
>Does SMB2 issue really apply to RDP clients also ?
>
>Andrus.
>
>>Hi,
>> Disable SMB2, oplocking & Disk caching if available on the drive.
>> See http://www.petri.co.il/how-to-disable-smb-2-on-windows-vista-or-server-2008.htm