SMB1,2 and 3 -OpLocks etc. What is the current experience/view

Hi All,

I was wondering what the current views or experience is regarding enabling/disabling SMB1,2 or3 and or Oplocks and any other caching. Particularly with SMB1 effectively dead and buried.

Main reason for asking, is I am getting some weird problems on a site I don't support the network for, which until now has been fairly stable.

temporary "pub_" files being reported as locked??

more worryingly - the balance/details being updated on the wrong record.

reconciled balance updated onto wrong cashbook account in NBANK
2 people doing Purchase Orders, one crashes and the other emails their order to his supplier

40 Opera users

HyperV on 2012 host

Pegasus Server is VM (probably P2V of old box) 2008r2

clients a mixture of Win7, Win10 and 2012RDS/TS

Alan, I saw your link to https://www.gerjon.com/citrix/xenappxendesktop/windows-2012r2-slow-and-slow-vfp-visual-foxpro-databases/ which I am also reviewing.

I have my suspicions around Webroot, but just being thorough.

Thanks in advance

Colin

Find more posts tagged with

Pegasus - Partner General Discussions

Comments

unknown

Hi Colin,

Strangely enough we are seeing a similar thing in a very similar environment as well as one when doesn't use Citrix. All started with Windows 1803 update to Windows 10!

We're investigating it too so shall share any knowledge we come across.

Thanks,

Bhav

jodie

We saw similar issues caused by client computers with windows 10 v1803+.

We have applied the following reg keys to all affected computers and its resolved the issues:

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanWorkstationParameters]

"FileNotFoundCacheLifetime"=dword:00000000

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanWorkstationParameters]

"FileInfoCacheLifetime"=dword:00000000

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanWorkstationParameters]

"DirectoryCacheLifetime"=dword:00000000

unknown

Hi Colin, Not sure if this is related. We seem to be getting a lot of issues, with clients reporting problems around POP. lines going missing, PO's not posting correctly. Relogging back in and them appearing. Suggestion was to increase the ram on the server, this we applied and still the problems is happening. Just seems odd, that it's not just one client, but a variety. Some with bespoke and some totally without, so we have ruled out bespoke.

Thanks

Mark

colin-avey

Hi Mark,

The registry entries mentioned by Jodie above seem to be gaining some traction and are definitely worth a try. I am surprised there is nothing in the installation guide on the topic. An official line from Pegasus would be useful (apologies if I have missed something).

If you are running the Opera Client on a Terminal Server or similar it may be worth adding "Temp User=YES" to the opera.ini file. This will create separate Temp folders for each Windows User.

HTH

Colin

alan-bourke

The changes to SMB caching will resolve the issue, however they can have an detrimental impact on network performance. Also I think that fully updated Windows 10 1809 and 1803 may now have fixed the original SMB problem that Microsoft introduced anyway.

For those reasons they should be taken as being a last resort as opposed to something that should be applied across the board to all workstations.

colin-avey

Thanks Alan.

Copyright © 2025 Infor. All rights reserved.