Thanks Frank Unfortunately the application in this instance is not written by us, and although a SQL based version of the application is available it doesn’t have all the modules over the VFP version so in most cases we are only able to install the VFP version.
We are mostly talking about Server 2012R2+ (Some Server 2008) including 2016 and Windows 7/10 clients, so SMB1 is for the most gone and this is about using SMB2 without issue. Thanks Chris. -----Original Message----- From: ProfoxTech <profoxtech-boun...@leafe.com> On Behalf Of Frank Cazabon Sent: Tuesday, 27 August 2019 13:30 To: profoxt...@leafe.com Subject: Re: SMB Hi Chris, I moved away from DBF and DBC a long time ago but I don't think it was very difficult to check the registry settings manually. There is a tool available here: http://www.symantec.com/connect/downloads/smb2-toggle-too-mikes-tool-set Here are my notes from back then: *To Disable SMB2* When using the terms "client" and "server" in case of file and print sharing, it does not necessarily mean that a client-type OS such as Vista "always" connects to a server-type Os such as Windows Server 2008. Sometimes, a Vista computer will connect to another Vista computer, and in that case, the computer that is "serving" the shares is considered to be the "server". Here's how SMB is used when related to SMB versions: When a Windows Server 2008/Vista "client" connects to a Windows Server 2008/Vista "server", SMB 2.0 is used. When a Windows Server 2008/Vista "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used. When a Windows 2000/XP/2003 "client" connects to a Windows Server 2008/Vista "server", SMB 1.0 is used. When a Windows 2000/XP/2003 "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used. So, for troubleshooting purposes, mostly in an environment that has mixed operating systems, you might want to consider disabling SMB 2.0. You need to do so on both the "client" and the "server" operating systems. To disable SMB 2.0 for Windows Vista or Windows Server 2008 systems that are the “client” systems run the following commands: sc config lanmanworkstation depend= bowser/mrxsmb10/nsi sc config mrxsmb20 start= disabled Note there's an extra " " (space) after the "=" sign. To enable back SMB 2.0 for Windows Vista or Windows Server 2008 systems that are the “client” systems run the following commands: sc config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsisc config mrxsmb20 start= auto Again, note there's an extra " " (space) after the "=" sign. In order to disable SMB 2.0 on the server-side computer, follow these steps: Warning! This document contains instructions for editing the registry. If you make any error while editing the registry, you can potentially cause Windows to fail or be unable to boot, requiring you to reinstall Windows. Edit the registry at your own risk. Always back up the registry before making any changes. If you do not feel comfortable editing the registry, do not attempt these instructions. Instead, seek the help of a trained computer specialist. 1. Run "regedit" on Windows Server 2008 based computer. 2. Expand and locate the sub tree as follows. HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters 3. Add a new REG_DWORD key with the name of "Smb2" (without quotation mark) Value name: Smb2Value type: REG_DWORD0 = disabled1 = enabled 4. Set the value to 0 to disable SMB 2.0, or set it to 1 to re-enable SMB 2.0. 5. Reboot the server. This paper may also be of some assistance: https://www.dataaccess.com/KBasePublic/Files/2476.Tuning%20Microsoft%20Networks%20for%20the%20Legacy%20Embedded%20Database_PDF_FMT.PDF Frank. Frank Cazabon On 27/08/2019 06:57 AM, Chris Davis wrote: > Hi All > > With any networked VFP application sharing a DBC the SMB performance of the > server hosting the DBC is very important? > > Assuming your answer to the above question is Yes or Of Course, then when you > have one server that seems to perform well and one that doesn't it would be > useful to easily compare the setup of the two. > > Is anyone aware of any utilities that make the configuration and tweaking of > SMB easy or at least allow you to compare to setups? > > Of course, if your answer to the first question isn't yes I would also be > interested in your thoughts. > > I know there is a lot more that comes into the performance of an application > other than the setup of the server, i.e the spec of the client, the os of the > client, other software such as anti virus, network infrastructure etc etc. > > Where I am going with this... > > We have lots of sites where an application works well and one site where it > doesn't, and without having to spend hours and hours investigating all the > various settings and registry entries, I just want to start with the servers > and make a comparison to see if there are any obvious differences. > > Thanks > > Chris. > > > > > > > --- StripMime Report -- processed MIME parts --- multipart/alternative > text/plain (text body -- kept) > text/html > --- > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/c8f4e5c6-d5ee-0ab6-1fe5-89629e65e...@gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious. Report [OT] Abuse: http://leafe.com/reportAbuse/c8f4e5c6-d5ee-0ab6-1fe5-89629e65e...@gmail.com _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/cwlp265mb1668e3690060fae7ccf3cc0a8f...@cwlp265mb1668.gbrp265.prod.outlook.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
