22 Jun
2017
22 Jun
'17
9:37 a.m.
There was an issue with SMB2 in the early days of Server 2008, which was subsequently fixed by MS and before the fix the workaround was to knock it back to SMB1. Ever since it was fixed we have not had to touch anything to do with these types of networking settings in the normal course of events. These days you definitely want everything running at SMB2 or SMB3 (as negotiated automatically between clients and the server) or it you'll definitely see sub-optimal speed.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
On Thu, 22 Jun 2017, at 10:25 AM, Chris Davis wrote:
> Hi All
>
> I have read through previous posts on this subject, but the more I read
> the more confused I get as to what advice I should be following.
>
> We have a situation where speed issues are affecting a VFP application.
> The data is held on a Server 2012 server. Previously we have be told to
> disable SMB2 etc, but it seems now that this shouldn't be an issue.
>
> I have now found mentions of a SMB2 registry setting along the lines of
> the OPLOCKS thing years ago. This setting is DisableLeasing, has anyone
> else faced similar issues and/or used this DisableLeasing option to
> improve application performance?
>
> Thanks
>
> Chris.
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
> --- StripMime Report -- processed MIME parts ---
> multipart/alternative
> text/plain (text body -- kept)
> text/html
> ---
>
[excessive quoting removed by server]