I don't know what you tried, but at a certain point, MS has disabled the disabling registry keys to go back to SMBv1. SMBv2 can't be deactivated since I think Win8 Client and 2012 Server, so as far as I know you're forced to at least using SMBv2.
I see an article here that mentions deactivating even SMBv1 on several OSes via several methods and that's last updated this year, but it contradicts what I have read in the professional press about IT and from elsewhere:
SMB would likely cause more than just performance problems. Do you have frequent DBF corruptions? Memo corruptions? Index corruptions? If not, the problem likely isn't SMB version.
There are still all kinds of other reasons for an application to become slow. I guess you use DBFs, are there CDXes? Is data indexed? Is TEMP local? What's the LAN bandwidth and how is that shared among users and other applications?
I have an application installed in 1200 customers and it works very well, but once the application is moved to a server with Windows 2012 R2 or more, the application becomes very slow especially if the number of users increases.
I already look in the internet and forums, they always talk about SMB as indicated in the attached document
Yes, I know the deal with SMB on performance, but as already said, if SMB is the problem, it typically causes more than just a performance hit.
The 1200 references mean the code is OK, then what else differs, just the OS version? Are these your only customers with a larger user base? What are user numbers and amount of data, I'd look into that, a software can run nice non-optimized with low enough amounts of users and/or data. Especially since even many users are not always concurrent users and each has their own client, the only bottleneck is access to the shared DBFs.
Anyway, let's assume SMB is the culprit, then what have you tried from this article? Have you looked into the link I posted? It has other ways of disabling SMB.
The article you posted is only partly about SMB and doesn't use a method MS itself mentions in their article and besides that is on the topic of problems of Terminal server and Citrix clients, which have nothing, absolutely nothing to do with SMB.
Are you saying that in the meantime you did run the PowerShell commands? And restarted clients and servers?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.