One of the ways to access files located on network computers from STB is the protocol public access SMB, which is a standard Microsoft Windows protocol and provides the functionality "Networks Microsoft Windows» and “File and Printer Sharing”.
Samba - free implementation of the SMB protocol for UNIX-like and other operating systems.

The use of SMB / Samba protocols allows access from STB (running Linux OS) to folders and files located on network computers (running Linux OS, Windows, etc.). Thus, STB users have the opportunity to play media files (video, audio, images) on the STB, which are located on network computers running one of the types of OS that supports the SMB protocol.

Protocol SMB/Samba is an application protocol (in terms of the OSI network model). The TCP/IP transport protocol is used for data exchange.
The SMB / Samba protocol uses a client-server architecture: a PC acts as a server, on which certain network resources (folders) with media files are located, and a STB acts as a client, from which media files are played.

Network resources (in the form of shortcuts) are displayed in the STB, in the menu, in accordance with the standard LAN network architecture of Windows OS: Network / Workgroup / Computer / Folder.

By default, access to computer resources is blocked by settings on the computer side. If it is necessary to gain access to a specific network folder, the computer user opens access to this folder. To control access to folders, use the procedureWindows OS" File sharing".

There are two types of network access to folders (the type of access is determined on the server side):

• by password- to access a network folder from the STB side, use the procedure Authorizations(you must enter the login name of a specific computer user and his password);
• without password - access to the network folder is open for all users, without having to enter a password.

Discovery of shared network resources on the STB side occurs automatically (unless it is prohibited on the computer side or except in cases related to incorrect work networks). A connection to a network folder is established when the STB user opens network folder. If a folder is accessed using a password, the user is prompted to specify login And password.

It is also possible manual connection network folders (if they were not detected automatically). Configuring and accessing network resources using the protocol SMB/ Samba on STB it is carried out in the menu Home media .

Below is an example of how to connect a network folder on a Windows 10 PC to play media files from STB.

Parameters used in the example

Computer (file server):

• Operating system - Windows 10 64-bit;
• Computer name – My_ computer;
• Working group - WORKGROUP (the name of the “default” workgroup in the OS “Windows»);
• IPPC address: 192.168.1.186.
• Network resource to which access is opened (folder with media files) - folder Video_ E1.
• Username - Usr.

STB (client)

• IPaddressSTB: 192.168.1.230

Setting up a connection on the PC side

Checking the availability of the network connection between the PC and STB

Before setting up the connection, make sure that the network connection between the PC and STB is available - send ICMP Echo Requests ( PING) from PC to STB.

Examination enabling the SMB protocol

1. Open Control Panel⇒ All control panel elements ⇒ Programs and components.
2. In the left panel select the item Enable and disable Windows components .
3. Make sure the option is enabled SMB 1.0/CIFS file sharing support.

Configure sharing settings for different Windows profiles

1. Open Control Panel⇒ All control panel elements ⇒ Network and Sharing Center .

2. In the left panel, select the item Change advanced sharing options .

2. Configure sharing settings for three profiles (" Private", "Guest or public" And "All networks"):

Private

Guest or public

All networks

Opening access to a folder on the PC side

1. Share the folder Video_E1: Properties ⇒ Access⇒ Sharing.
2. In the window that opens File sharing select and add users to access the folder:

2.1 To organize access to a folder using a password (the PC user password is used), select and add the necessary users (in the example, access for current user Usr). In this case, when you try to open a folder from the STB, you will be prompted for a login (computer user name) and password (computer user password).

Please note. Nessesary to use specific value password account user. The absence of a password (empty password) will make it impossible to access the folder!

2.2 If you need to provide access to the folder to all network users, select a user from the list "All"(if such an item is not in the list, select and add).

The figure below shows an option for setting up passwordless access to a folder Video_E1(for all network users).

Automatic connection to a network folder from the STB side

1. In the Built-in portal, go to Main window⇒ HomeMedia⇒ Network ( Network ) ⇒ WORKGROUP

2. In a folder WORKGROUP are displayed network computers working group.
Open the shortcut to the desired network computer - My_ Computer(In chapter My_ Computer folders of the network computer with the same name are displayed, for which access is open).

3. To make sure that automatic detection network resource has taken place and to check the protocol type, you need to select the folder and use the “i” (INFO) button on the remote control:

4. Open folder Video_E1. Inside the folder, follow the path where the media file you want to play is located.

5. If password access is set for a folder, or for some reason STB cannot “mount” the folder (that is, gain access to it - see section), then when you try to open this folder window opens Network connection.

6. Launch the media file.

Forced connection to a network folder from the STB side

For cases where automatic connection is not established, there is a manual setting access to a network folder:

• Open in the Built-in portal Main window⇒ HomeMedia⇒ network
• Call window Operations (Operations) - button Menu on the remote control.
• Click Connect NFS/SMB ( Connect NFS/SMB) .
• In the window Connecting a network folder (Connect network folder) enter connection parameters:
  • Server address (Server Address) – IP address of the PC (file server) on which the required network folder is located;
  • Folder on the server (Server folder) – name of the folder (directory) on the PC for which shared access is set;
  • Local folder (Local folder) – folder name on STB (by default, the same as the folder name on the server);
  • Connection type (Connection type) – SMB.
  • Login (Login) – access login - entered if password access is used for the folder. Entered value with matches the PC username;
  • Password (Password) – folder access password - entered if password access is used for the folder.
    Note. If the folder uses passwordless access, the fields Login And Password must be empty!

Disabling a network folder, changing connection settings on STB

To force a specific network folder to be disabled, use the command for that folder Disable NFS/SMB.

If you need to make changes to the connection settings of a specific folder (for example, when changing access parameters for a folder on the PC side), use the command for this folder Edit share.

Mounting a folder

Establishing a connection to a specific folder, described in subsections and , is accompanied by automatic mounting of the folder on the STB. If a certain folder is "mounted" on the STB, its shortcut appears on upper level menu Home media.

The user can also mount required folder manually (this also leads to folder connection), the command is used for this purpose Mount share.

To "unmount" a folder in the STB (this also leads to disconnecting the folder from the STB), use the command Unmount share.

Check on your computer.

Check on your computer.

Reboot the STB and PC and try connecting again.

2. If, when opening a network folder on the STB, you are prompted to perform authorization, but password access has not been assigned to the folder:

1. • On a network computer, check that the folder properties are set to user-accessible "All";

3. If, when opening a folder on STB, you are prompted to perform authorization (enter login, password), but the password value is not specified (empty password):

1. • Set a specific value for the computer user password;
   • If access is not restored, reboot STB.

4. If the file does not open:

1. • check if the file is played locally on the PC;
   • try to launch other files from the STB from the same network folder, from other network folders;
   • try to play a file of a different format (it is advisable to check a file that was previously played on the STB, for example, from a USB drive). Maybe, this format file is not supported by the STB player.

In the dialog boxNew Registry Propertiesselect the following:

• Action:Create


• Bush: HKEY_LOCAL_MACHINE


• Path to section:SYSTEM\CurrentControlSet\Services\Lanman Server\Parameters


• Parameter name:SMB1


• Value type:REG_DWORD.


• Meaning: 0

This will disable SMB version 1 server components. This group policy must be applied to all required workstations, servers, and domain controllers in the domain.

Note. WMI filters can also be configured to exclude unsupported operating systems or selected exceptions such as Windows XP.

Attention!Be careful when making changes to controllers where legacy systems such as Windows XP or later Linux and third party systems(which do not support SMB version 2 or SMB version 3 protocols) requires access to SYSVOL or other shared folders where SMB version 1 has been disabled.

Disable SMB client version 1 with Group Policy

To disable the SMB version 1 client, the registry key service key must be updated to disable MRxSMB10 from starting, and then the dependency on MRxSMB10 must be removed from the entry for LanmanWorkstation so that it can start in a standard way without prompting MRxSMB10 on first launch.

This update replaces the default values ​​in the following two registry items

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl Set\services\mrxsmb10

Parameter: Start REG_DWORD: 4 = disabled

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl Set\Services\LanmanWorkstation

Parameter: DependOnService REG_MULTI_SZ: “Bowser”,”MRxSmb20″,”NSI”

Note. Contains MRxSMB10 by default, which is currently excluded as a dependency

To configure using group policy:

1. Open Group Policy Management Console. Click right click Click on the "Group Policy Object (GPO)" that should contain the new preferred item, then click Edit.


2. In the console tree in the section Computer configuration expand the Settings folder, then expand the Windows Settings folder.


3. Right-click the Registry node, click New, and select Registry Item.

In the dialog box New Registry Properties select the following:

• Action: Update


• Bush: HKEY_LOCAL_MACHINE


• Partition path: SYSTEM\CurrentControlSet\services\mrxsmb 10


• Parameter name: Start


• Value type: REG_DWORD.


• Data value: 4

Then remove the dependency in MRxSMB10 that was disabled

In the dialog box New Registry Properties select the following:

• Action: Replace


• Bush: HKEY_LOCAL_MACHINE


• Partition path: SYSTEM\CurrentControlSet\Services\Lanman Workstation


• Parameter name: DependOnService


• Parameter type REG_MULTI_SZ


• Data value:
  
  
  • Bowser
  
  
  • MRxSmb20
  
  
  

Note. These three lines will not have markers (see below)

The default values ​​contain MRxSMB10 in a large number of versions of Windows, so replacing them with a multi-valued string will remove MRxSMB10 as a dependency for LanmanServer and go from the four default values ​​to just the three values ​​described above.

Note. When using the Group Policy Management Console, you do not need to use quotation marks or commas. Just enter each entry on a separate line as above

Reboot required:

Once the policy is applied and the registry settings are entered, SMB version 1 will be disabled when the system is rebooted.

annotation

If all the settings are in one Group Policy Object (GPO), then Group Policy Management will display the settings below.

Testing and verification

Once configured, give permission to the policy to perform replication and update. Because this is necessary for testing, run gpupdate /force from the CMD.EXE line and then browse the target machines to ensure that the registry settings are applied correctly. Ensure that SMB version 2 and SMB version 3 are running for all systems in the environment.

Attention! Don't forget to reboot the target systems.

Due to the recent epidemic WannaCry ransomware exploiting the SMB v1 vulnerability, advice on disabling this protocol has again appeared on the network. Moreover, Microsoft strongly recommended disabling the first version of SMB back in September 2016. But such a disconnection can lead to unexpected consequences, even funny things: I personally came across a company where, after fighting with SMB, they stopped playing wireless speakers Sonos.

Especially to minimize the likelihood of being “shot in the foot,” I want to remind you of the features of SMB and consider in detail the consequences of ill-considered disabling its older versions.

SMB(Server Message Block) – network protocol For remote access to files and printers. This is what is used when connecting resources via \servername\sharename. The protocol initially worked on top of NetBIOS, using UDP ports 137, 138 and TCP 137, 139. With the release of Windows 2000, it began to work directly, using TCP port 445. SMB is also used for domain logon Active Directory and work in it.

In addition to remote access to resources, the protocol is also used for interprocessor communication through “named streams” - named pipes. The process is accessed along the path \.\pipe\name.

The first version of the protocol, also known as CIFS (Common Internet File System), was created back in the 1980s, but the second version appeared only with Windows Vista, in 2006. The third version of the protocol was released with Windows 8. In parallel with Microsoft, the protocol was created and updated in its open implementation Samba.

In each new version Various improvements were added to the protocol aimed at increasing performance, security and support for new functions. But at the same time, support for old protocols remained for compatibility. Of course, there were and are quite a few vulnerabilities in older versions, one of which is exploited by WannaCry.

Under the spoiler you will find a summary table of changes in SMB versions.

Version	operating system	Added compared to the previous version
SMB 2.0	Windows Vista/2008	The number of protocol commands has changed from 100+ to 19
		Possibility of “conveyor” work – sending additional requests before receiving a response to the previous one
		Symbolic link support
		Signing HMAC messages with SHA256 instead of MD5
		Increase in cache and write/read blocks
SMB 2.1	Windows 7/2008R2	Performance improvement
		Larger MTU support
		Support for the BranchCache service - a mechanism that caches requests in global network V local network
SMB 3.0	Windows 8/2012	Possibility to build a transparent failover cluster with load distribution
		Support for direct memory access (RDMA)
		Manage via Powershell cmdlets
		VSS support
		AES–CMAC signature
		AES–CCM encryption
		Ability to use network folders for storage virtual machines HyperV
		Ability to use network folders for storage Microsoft databases SQL
SMB 3.02	Windows 8.1/2012R2	Security and performance improvements
		Automatic balancing in a cluster
SMB 3.1.1	Windows 10/2016	AES–GCM encryption support
		Integrity check before authentication using SHA512 hash
		Mandatory secure “negotiations” when working with SMB 2.x clients and higher

We consider conditionally victims

It’s quite easy to view the currently used protocol version; we use the cmdlet for this Get-SmbConnection:

Cmdlet output when open network resources on servers with different version Windows.

The output shows that a client that supports all protocol versions uses the maximum possible version from those supported by the server. Of course, if the client only supports old version protocol, but on the server it will be disabled - the connection will not be established. Enable or disable support for older versions in modern systems Windows can be done using the cmdlet Set–SmbServerConfiguration, and see the state like this:

Get–SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol

Disable SMBv1 on a server running Windows 2012 R2.

Result when connecting with Windows 2003.

Thus, if you disable the old, vulnerable protocol, you can lose the functionality of the network with old clients. Moreover, in addition to Windows XP and 2003, SMB v1 is also used in a number of software and hardware solutions (for example, NAS on GNU\Linux using an old version of samba).

Below the spoiler, I will provide a list of manufacturers and products that will completely or partially stop working if SMB v1 is disabled.

Manufacturer	Product	A comment
Barracuda	SSL VPN
	Web Security Gateway backups
Canon	Scan to a network resource
Cisco	WSA/WSAv
	WAAS	Versions 5.0 and older
F5	RDP client gateway
	Microsoft Exchange Proxy
Forcepoint (Raytheon)	"Some Products"
HPE	ArcSight Legacy Unified Connector	Old versions
IBM	NetServer	Version V7R2 and older
	QRadar Vulnerability Manager	Versions 7.2.x and older
Lexmark		Firmware eSF 2.x and eSF 3.x
Linux Kernel	CIFS Client	From 2.5.42 to 3.5.x
McAfee	Web Gateway
Microsoft	Windows	XP/2003 and older
MYOB	Accountants
NetApp	ONTAP	Versions up to 9.1
NetGear	ReadyNAS
Oracle	Solaris	11.3 and older
Pulse Secure	PCS	8.1R9/8.2R4 and older
	P.P.S.	5.1R9/5.3R4 and older
QNAP	All storage devices	Firmware older than 4.1
RedHat	RHEL	Versions up to 7.2
Ricoh	MFP, scanning to network resource	In addition to a number of models
RSA	Authentication Manager Server
Samba	Samba	Over 3.5
Sonos	Wireless speakers
Sophos	Sophos UTM
	Sophos XG firewall
	Sophos Web Appliance
SUSE	SLES	11 and older
Synology	Diskstation Manager	Control only
Thomson Reuters	CS Professional Suite
Tintri	Tintri OS, Tintri Global Center
VMware	Vcenter
	ESXi	Older than 6.0
Worldox	GX3 DMS
Xerox	MFP, scanning to network resource	Firmware without ConnectKey Firmware

The list is taken from the Microsoft website, where it is regularly updated.

The list of products that use the old version of the protocol is quite large - before disabling SMB v1, you should definitely think about the consequences.

Still turning it off

If there are no programs and devices using SMB v1 on the network, then, of course, it is better to disable the old protocol. Moreover, if shutdown on SMB Windows server 8/2012 is done using the Powershell cmdlet, then for Windows 7/2008 you will need to edit the registry. This can also be done with Powershell help:

Set–ItemProperty –Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB1 –Type DWORD –Value 0 –Force

Or any other in a convenient way. However, a reboot will be required to apply the changes.

To disable SMB v1 support on the client, just stop the service responsible for its operation and fix the dependencies of the lanmanworkstation service. This can be done with the following commands:

sc.exe config lanmanworkstation depend=bowser/mrxsmb20/nsi sc.exe config mrxsmb10 start=disabled

To conveniently disable the protocol throughout the network, it is convenient to use group policies, in particular Group Policy Preferences. Using them you can conveniently work with the registry.

Creating a registry element through group policies.

To disable the protocol on the server, just create the following parameter:

path: HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters;

new parameter: REG_DWORD with the name SMB1;

• value: 0.

Create a registry setting to disable SMB v1 on the server through group policies.

To disable SMB v1 support on clients, you will need to change the value of two parameters.

First, disable the SMB v1 protocol service:

path: HKLM:\SYSTEM\CurrentControlSet\services\mrxsmb10;

parameter: REG_DWORD with the name Start;

• value: 4.

We update one of the parameters.

Then we will correct the dependency of the LanmanWorkstation service so that it does not depend on SMB v1:

path: HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation;

parameter: REG_MULTI_SZ with name DependOnService;

• value: three lines – Bowser, MRxSmb20 and NSI.

And we replace it with another one.

After applying Group Policy, you must restart your organization's computers. After a reboot, SMB v1 will no longer be used.

It works - don't touch it

Oddly enough, this old commandment is not always useful - ransomware and Trojans can appear in rarely updated infrastructure. However, careless shutdown and update of services can paralyze the work of an organization just like viruses.

Tell me, have you already disabled the first version of SMB? Were there many casualties?

Hello! For those who are not in the know, I’ll start from afar. On computers and laptops with installed Windows There is a separate "Network" tab in Explorer. This tab displays devices from the network environment. That is, by opening the “Network” tab we can see computers, network storage (NAS), multimedia devices (DLNA), flash drives and external drives, which are connected to the router and to which public access is configured. Simply put, those devices that are connected through one router (located on the same network) and on which network discovery is enabled (devices that can be discovered on the local network). Our router may also be displayed there (section "Network infrastructure") and other devices.

Now I’ll explain what and how, and why I decided to write this article. I have an ASUS router to which I connected USB flash drive, and configured shared access to this flash drive for all devices on the network. And what do you think, this network drive appeared in the “Network” section on all computers (it is displayed there as "Computer"), but it didn’t show up on my computer. That is, my computer did not see the flash drive connected to the router, nor other computers on this network. But the DLNA server was displayed running on the same router. But this does not change anything, since I need the usual network access to the drive.

Also, I could not access the flash drive when I typed its address //192.168.1.1 in Explorer. This address was immediately opened through a browser. And I was unable to connect this drive as a network drive. It simply was not in the list of available devices in the network environment.

Such a problem when Windows 7, Windows 8, or Windows 10 does not see network devices is not uncommon. It doesn't have to be a flash drive, or external HDD, which you connected to your router, as in my case. Most often, shared access is configured between computers on a local network. And they face the same problem when computers are connected to the same network (to one router), the sharing settings are set correctly, but the "Network" tab is empty. Or only the router and your computer are displayed.

Since there can be many reasons and, accordingly, solutions, I’ll probably start with the simplest ones (which didn't help me) and at the end of this article I will share the solution that helped in my case. As a result, my laptop still saw all the devices on the network. Including a network storage device and another computer that is also connected to this network.

But this does not mean that you have the same case. Therefore, I advise you to check all the settings in order.

Checking sharing settings

We will consider two cases:

1. When computers do not see each other on the local network.
2. Sharing network storage. This could be a flash drive, or HDD which is connected to the router, or a separate drive (aka NAS).

First case

For computers to be able to see each other and appear in the Network section in Explorer, they must be connected through the same router. Or connected directly (cable or via Wi-Fi). Simply put, they must be on the same local network.

Next, on all computers (I don’t know how many of them you have there), it is advisable to assign the network status to “Home” (private). I wrote in the article how to do this in Windows 10. In Windows 7, just go to the Network and Sharing Center and change the status of the current connection there.

If after this the computer still does not detect other computers (or vice versa), then let's also check the sharing settings.

To do this, in the “Network and Sharing Center” window (if you don’t know how to open it in Windows 10, then see the article), click on the “Change advanced sharing settings” item.

And for the current profile (usually “Private”) we set the parameters as in the screenshot below.

Let's do it on all computers on the local network.

Articles on this topic:

As a rule, these tips solve all problems with detecting computers on a local network.

Second case

When you have problems accessing your network storage. As in my case. I haven't seen Windows 10 USB drive, which was connected to the ASUS router. Now many routers have a USB port for connecting drives and other devices, so the topic is relevant.

You need to make sure that this drive is defined in the router settings and that sharing is enabled. It is clear that this is done differently on different routers. On ASUS routers, for example, it looks like this:

Related articles:

Do not confuse sharing settings with FTP settings. The FTP server settings on the router have nothing to do with this.

Well, if other devices see the network storage and have access to it, but on a particular computer there is no access to it, then the problem is not on the router’s side. Go through the settings of the “problem” PC using this article.

An antivirus or firewall may be blocking network devices

If your antivirus or firewall (firewall) that is installed on your computer doesn’t like something, then it can easily make it so that neither you can see other devices in the network environment, nor can anyone detect you.

True, after disabling the firewall built into my antivirus, the problem was not solved (which means the problem is most likely not there), but it still seems to me that in my case it could not have happened without the participation of the antivirus.

Therefore, try to completely stop the antivirus for a while, or at least disable the firewall built into it (firewall). In NOD 32 this is done like this:

To check this you need to do on all computers, which will participate in the local network.

It is quite possible that you have some other programs installed that can monitor the network and manage network connections.

If it turns out that the problem is in the antivirus, then you need to add your network to the exceptions. Prevent the firewall from blocking the network itself or network devices.

If you don’t have an antivirus, you can experiment with disabling/enabling the firewall built into Windows.

Working group

The workgroup must be the same on all devices. As a rule, this is true. But it is advisable to check. To do this, open the computer properties "System" and go to "Advanced system settings".

"Working Group" will be indicated there. To change it, you need to click on the "Change" button.

Once again: the workgroup name must be the same on all computers.

If you have a problem accessing your network storage (to flash drive via router), then in the sharing settings on the same ASUS router the work group is also indicated. You can look at the screenshot above in the article. It should be the same as on the computer.

Problem accessing a shared network folder via SMB1 in Windows 10 (my solution)

Let's return specifically to my problem. Everything I described above has been checked and rechecked 10 times already. I did it a couple of times, but Windows 10 never saw other computers on the network and, most importantly, the shared folder in the form of a flash drive connected to the router never appeared in Explorer. And on other devices on the network everything was detected without problems. Including my laptop.

I read somewhere that you can try opening a shared folder through the Run window. Pressed the Win + R key combination and entered the network folder address //192.168.1.1 (aka router address).

I did not gain access to the drive, but an interesting error appeared:

You cannot connect to the shared folder because it is not secure. This shared folder runs on the legacy SMB1 protocol, which is insecure and may expose your system to attack.

Your system needs to use SMB2 or later.

This is already interesting. At least something.

SMB (Server Message Block) is a network protocol that is responsible for sharing access to files, printers and other network devices.

I started looking. And it turns out that Windows 10 abandoned the SMB1 protocol. Because of safety. And the Samba software package installed on my router seems to work using the SMB1 protocol. That's why Windows 10 doesn't see it. But other computers that also run Windows 10 were also not displayed on the “Network” tab.

Since I couldn’t update the protocol for SMB2 in the router settings, I decided that I needed to somehow enable SMB1 support in Windows 10. And as it turned out, this can be done without any problems. As a result, after connecting the “SMB Client 1.0/CIFS” component, everything worked for me. The system saw shared folders on computers on the network and a network folder configured on the router itself.

How to enable SMB1 in Windows 10?

Through the search, find and open the old “Control Panel”.

Switch to Small Icons and open Programs and Features.

Open "Turn Windows features on or off". Find the item “Support for SMB 1.0/CIFS file sharing”. Open it and check the box next to "SMB Client 1.0/CIFS". Click Ok.

If your computer prompts you to restart, restart it. If there is no prompt window, reboot manually.

After the reboot, all available devices on your network should appear on the “Network” – “Computer” tab.

I will be glad if this article is useful to someone and helps solve the problem that has arisen. Don't forget to write in the comments about the results. Or ask the question, where would we be without them :)

SMB or Server Message Block is a network communication protocol designed for sharing files, printers and others various devices. There are three versions of SMB – SMBv1, SMBv2 and SMBv3. For security reasons, Microsoft recommends disabling SMB version 1 as it is outdated and uses technology that is almost 30 years old. To avoid infection with ransomware viruses like WannaCrypt, you need to disable SMB1 and install updates for operating system. This protocol is used by Windows 2000, Windows XP, Windows Server 2003 and Windows Server 2003 R2 - therefore, network file access to these OS versions will not be available. The same applies to some network storages, scanners, etc.

Disabling SMB1 from Control Panel

Start -> Control Panel -> Programs and Features -> Turn Windows features on or off

Disable ‘Support for SMB 1.0/CIFS file sharing’

Disabling SMB1 via Powershell

Open a Powershell console with administrator rights and enter the following command:

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB1 -Type DWORD -Value 0 –Force

Disable SMB1 using Windows Registry

You can also disable SMBv1 by running regedit.exe and moving on to the next section:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

Create a DWORD in this section SMB1 with meaning 0 .

Values ​​for enabling and disabling SMB1:

• 0 = Off
• 1 = Enabled

After this you need to install the update MS17-010. The update is out for everything Windows versions, including Windows XP and Windows Server 2003, which are no longer supported.

And in conclusion I would like to say that, despite installed antivirus and regular operating system updates, if you value your data, you need to think about backup first.

Why and how you need to disable SMB1 in Windows 10/8/7