VFP 9 and Win 2008 Opportunistic Locking 1

[Auguy]

I hope somebody can clear this up for me. I have a VFP 9 app that is going to use Win 2008 SBS for data storage. I have read here and other places about problems with opportunistic locking. Here is my understanding of what needs to be done.

1. Disable SMB 2.0 on the server which causes it to default to SMB 1.0
2. Disable SMB 1.0 on the server
3. Disable SMB 1.0 on the XP clients
4. Disable SMB 2.0 on the any Win 7 or Vista clients.

Has anybody done this? Can you point me to some sources to do this correctly? Thanks.

Auguy
Northwest Ohio

 

[Auguy]

Will it make a diference if the exe is stored and run from the client pc's rather than storing the exe on the server?

Auguy
Northwest Ohio

 

[Olaf Doschke]

Your first post: You turn off SMB2, true. But you don't turn off SMB1, you turn off opportunistic locking.

Your second post: No, an exe on the server is also executed at the client, if we talk about a network share users point to instead of a local copy, the only difference is there is one central folder storing the exe. Mayn users adress that exe, which adds to network traffic and opportunistic locking problems are then also problems with code, nit just with data.

Instead put a cmd file with an xcopy and let users start that.

The situation differs when using terminal server, but anyway that changes nothing in terms of opportunistic locking.

Bye, Olaf.

 

[Auguy]

Thanks Olaf, your posts are always very imformative.

Auguy
Northwest Ohio

 

[Olaf Doschke]

Thanks, Auguy!

Besides, heres a link to explainations and how to disable SMB2 nd oplocks:

http://www.dataaccess.com/whitepapers/opportunlockingreadcaching.html

Bye, Olaf.