Oplock when installed on local pc but data is on network server?

[Vince Wen]

I've read all I can on this forum re: oplock with VFP9 application on a network server.

My question is a little different.

What about if the application is installed on a local pc, but the data is on a network server? Would this setup still have the same oplock issue?

Logically, I think it would, but I wanted to double-check this.

ps. I am a newb. So apologies in advance if this question is basic.

-vince

 

[Chris Miller]

The per share command is

Set-SmbShare -Name "Sharename" -LeasingMode None

If you can do

set-SmbServerConfiguration -EnableLeasing $False

you can also do that, but usually you won't have permission to do either. That's the point, so when you rely on admins defining the shares, you also depend on them making the leasing setting, don't you? And they will generally be much happier with only effecting a share than the whole server.

I wonder how you don't know the share names. Do you they only tell you the mapped drive letter for a share? In the interest of not polluting clients drive letters in my case they actually were very happy to not map shares to drive letters and let me use UNC path notation with the share name. \\servername\sharename\...

Well, besides that, when a share is configured that way you also don't need to know the share name, if that's what the admins of your customer is happier with. But in a larger company I don't think they will ever be happy to create a drive letter mapping for every application needing a share for it's centralized files, like data is.

 

[tomk3]

We use MS-SQL for years but anyway, an interesting thread

I remember that using a Linux fileserver or a NAS also solves the OPlock problems