>hello all,
>
>recently one of our client moved their file server to windows 2008 from windows 2003. they also upgraded their Terminal server to windows 2008. since then, we have many problems (index corruption,invalid seek offset and others) whenever trying to access our vfp program from terminal server which access database on the file server.
>both these machines are windows 2008 server.
>i have read somewhere to try disabling smb2 on file server. we tried disabling smb2 on both file server and TS server and it resulted into communication problems between 2 machines. should we disabled smb2 only on the file server?
>anyone has any other suggestion re vfp and windows 2008.

There is a bug with the current SMB2 implementation, that affects so-called "file-server" databases such as VFP and Microsoft Access. This bug has not been resolved. The most recent discussion thread here starts with message#1440085 . You can click on the "View all messages of this thread" button below the first message, to read the whole thread.

If you're going to disable SMB2, I'd start with the file server. This is because, if you have any local machines running Vista or Win7 that access the app, they will also attempt to communicate with the file server via SMB2 if available. If you leave SMB2 enabled on the file server and disable it on the TS server, you could still get corrupted indexes from local Vista/7 workstations, without the TS server being involved at all.

If you have real-time antivirus scanning on the TS machine or the file server, you could try temporarily disabling the real-time scanning (on both machines), or configuring it so VFP files on the file server and the TS machine (including temp files in temp folders) don't get scanned.

It's probably a good idea to be certain you've fixed your index files before doing any further testing, otherwise your test results may not be valid.