Author: Frank Cazabon
Posted: 2014-07-17 at 13:50:18
On 17/07/2014 02:34 PM, Alan Lukachko wrote:
> One of my customers recently purchased a new HP Reliant server with Windows
> Server 2012 R2 installed. The hardware vendor installed our program and data
> and it worked as before without a site visit on our part. Our VFP 9.0
> program hasn't changed in more than 4 years. Now they get corruption of
> indexes.
Sounds like SMB2 needs to be switched off.
This might help:
or the short version:
These are my notes on switching it off (can't remember the site I got
this off of):
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
mixes 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.
--
Frank.
Frank Cazabon
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/53C81AEA.9070909@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.