Opportunistic Locking (Oplocks) in Parallels

[James Nachbar]

I am having trouble with corruption of an Access database being used from two separate Windows machines. I seem to have resolved the problem by turning off client oplock requests as in this article: http://support.microsoft.com/kb/296264

However, it appears that the root of the problem is that the Parallels database server is handling the oplock requests incorrectly. Indeed, this is a critically important topic for anyone using file sharing, yet the word "oplock" does not show up in a search of the entire parallels.com website.

Can anyone tell me how to control oplock functionality in Parallels? Is oplock functionality broken in Parallels Desktop for Mac? Does anyone at Parallels even know what an oplock is, and how can we get them to talk about this important topic?

 

[joevt]

A Parallels virtual machine behaves like any PC except with Mac file sharing. When Parallels shares a Mac folder with a PC through the \\.psf\ path, it is using it's own special file system driver (PrlSF), not SMB. If you're Access database is not on a Mac disk, then you shouldn't have a problem.

If you're Access database is on a Mac disk then you could try connecting to the Mac by enabling Windows File Sharing on the Mac and connecting using your Mac's IP address using a path like \\192.168.0.193\. Then you would be reliant on Apple's implementation of SMB.

To keep everything on PC, you could serve your Access database from a virtual machine server or PC server and have your other virtual machines or PC's connect to it using the server's IP address.