Windows 7 служба samba

Samba is a free and open-source software that allows you to share files and printers between Windows, macOS, and Linux operating systems. If you’re a Windows 7 user, you might be wondering how to use Samba to access shared resources on a network. In this comprehensive guide, we’ll take you through the process of installing, configuring, and using Samba on Windows 7.

What is Samba?

Before we dive into the nitty-gritty of using Samba on Windows 7, let’s take a brief look at what Samba is and how it works. Samba is a free and open-source software that implements the Server Message Block (SMB) protocol, which is used to share files, printers, and other resources between computers on a network.

Samba allows you to access shared resources on a network, including files, folders, printers, and other devices. It’s commonly used in business environments to share files and resources between employees, but it can also be used in home networks to share files and devices between family members or roommates.

Installing Samba on Windows 7

To use Samba on Windows 7, you’ll need to download and install the Samba software on your computer. Here’s how to do it:

Downloading Samba

1. Open a web browser and navigate to the official Samba website (www.samba.org).
2. Click on the “Download” button and select ” Binary Packages” from the drop-down menu.
3. Select the “Windows” option and choose the correct architecture (32-bit or 64-bit) for your Windows 7 system.
4. Click on the “Download” button to download the Samba installation package.

Installing Samba

1. Once the download is complete, run the installation package and follow the prompts to install Samba on your Windows 7 system.
2. Accept the license agreement and choose the installation location.
3. Select the components you want to install, including the Samba server and client.
4. Choose the startup type (Automatic or Manual) and click “Next” to continue.
5. Click “Install” to begin the installation process.

Configuring Samba on Windows 7

After installing Samba, you’ll need to configure it to connect to a shared resource on a network. Here’s how to do it:

Configuring the Samba Server

1. Open the Samba configuration file (smb.conf) using a text editor such as Notepad.
2. Add the following lines to the end of the file:
   “`
   [global]
   workgroup =
   security = user
   map to guest = Bad User

[share]
comment = My Shared Folder
path = /path/to/shared/folder
browsable = yes
writable = yes
guest ok = yes
``
Replacewith the name of your workgroup, and/path/to/shared/folder` with the path to the folder you want to share.

1. Save the changes to the smb.conf file.

Configuring the Samba Client

1. Open the Command Prompt as an administrator.

2. Type the following command to connect to the Samba server:
   net use <SHARE_NAME>: \\<SERVER_IP>\<SHARE_NAME>
   Replace <SHARE_NAME> with the name of the shared folder, and <SERVER_IP> with the IP address of the Samba server.

3. Press Enter to connect to the Samba server.

Accessing Shared Resources with Samba

Now that you’ve configured Samba, you can access shared resources on a network using the following methods:

Mapping a Network Drive

1. Open the Command Prompt as an administrator.

2. Type the following command to map a network drive:
   net use z: \\<SERVER_IP>\<SHARE_NAME>
   Replace <SHARE_NAME> with the name of the shared folder, and <SERVER_IP> with the IP address of the Samba server.

3. Press Enter to map the network drive.

Browsing the Network

1. Open the Windows Explorer and navigate to the “Network” section.
2. Look for the Samba server and the shared folder.
3. Double-click on the shared folder to access its contents.

Troubleshooting Common Issues

If you encounter any issues while using Samba on Windows 7, here are some common solutions to try:

Samba Server Not Found

• Check the Samba server’s IP address and make sure it’s correct.
• Ensure that the Samba server is running and configured correctly.

Unable to Connect to the Samba Server

• Check the workgroup name and make sure it matches the one configured on the Samba server.
• Ensure that the Samba client is configured correctly and the correct IP address is specified.

File Permissions Issues

• Check the file permissions on the shared folder and ensure that the correct users or groups have access.
• Use the chmod command to change the file permissions on the Samba server.

Conclusion

Using Samba on Windows 7 is a relatively straightforward process, but it does require some technical knowledge and configuration. By following the steps outlined in this guide, you should be able to install, configure, and use Samba to access shared resources on a network. Remember to troubleshoot common issues and adjust your configuration as needed to ensure seamless file sharing and collaboration.

Key Takeaways:

• Samba is a free and open-source software that implements the SMB protocol for sharing files and resources between computers on a network.
• Installing Samba on Windows 7 requires downloading and installing the Samba software and configuring the Samba server and client.
• Configuring Samba involves editing the smb.conf file and specifying the workgroup name, security settings, and shared folder path.
• Accessing shared resources with Samba can be done by mapping a network drive or browsing the network.
• Troubleshooting common issues involves checking the Samba server’s IP address, workgroup name, and file permissions.

What is Samba and why do I need it on my Windows 7?

Samba is a free and open-source software that allows Windows machines to share files and printers with other devices on a network. It is essentially an implementation of the SMB/CIFS protocol that allows Windows to communicate with Linux and other Unix-based systems. If you have a mixed environment with Windows and Linux machines, Samba is a must-have to seamlessly share resources between them.

By installing Samba on your Windows 7 machine, you will be able to access files and printers shared from Linux machines, and also share your own files and printers with others on the network. This eliminates the need for tedious workarounds, such as using FTP or cloud storage services, and makes it easy to collaborate with colleagues or access resources on other systems.

Is Samba compatible with Windows 7 64-bit?

Yes, Samba is compatible with Windows 7 64-bit. In fact, Samba is available in both 32-bit and 64-bit versions, so you can install the appropriate version depending on your system architecture. During the installation process, you will be prompted to choose the correct version, so make sure to select the 64-bit option if you have a 64-bit system.

It’s worth noting that Samba is a relatively lightweight software, so it won’t consume a significant amount of system resources. This means you can install and run Samba on your Windows 7 64-bit machine without worrying about performance issues or system crashes.

How do I install Samba on Windows 7?

Installing Samba on Windows 7 is a relatively straightforward process. First, download the Samba installer package from the official Samba website or a reputable mirror site. Once downloaded, run the installer and follow the prompts to install Samba on your system. The installation process typically takes only a few minutes, and you will be prompted to reboot your system after completion.

After rebooting, you will need to configure Samba to connect to your network and set up the necessary shares. This involves editing the Samba configuration file, typically located at /etc/samba/smb.conf. You can use a text editor or the Samba GUI configuration tool to edit the file and set up your shares.

How do I configure Samba to connect to my network?

Configuring Samba to connect to your network involves editing the Samba configuration file to specify the necessary settings, such as the workgroup, server name, and share definitions. You can use the Samba GUI configuration tool or a text editor to edit the file. The configuration file is usually located at /etc/samba/smb.conf.

A typical Samba configuration file will include settings for the workgroup, server name, and share definitions. For example, you might set the workgroup to “WORKGROUP” and the server name to “MyWindows7Machine”. You can also specify share definitions, such as sharing a specific folder or printer. Once you have edited the configuration file, save the changes and restart the Samba service to apply the new settings.

How do I access Samba shares from another machine on the network?

To access Samba shares from another machine on the network, you will need to map the share to a drive letter on the client machine. This involves opening the File Explorer or My Computer, and then navigating to the Network section. Look for the Samba server in the list of available network devices, and then double-click on it to access the shares.

Once you have accessed the shares, you can map the share to a drive letter by right-clicking on the share and selecting “Map network drive”. You can then choose a drive letter and specify the share path. This will create a persistent connection to the share, allowing you to access it easily in the future.

Is Samba secure?

Samba is a secure protocol, but like any network service, it can be vulnerable to security risks if not properly configured. By default, Samba uses encryption to protect data in transit, and it also supports user authentication and access control lists (ACLs) to restrict access to shares.

However, it’s still important to take additional security measures to protect your Samba installation. This includes setting strong passwords, limiting access to shares, and keeping your Samba installation up to date with the latest security patches. You should also use a firewall to block incoming traffic from unauthorized sources and limit access to the Samba service.

What are some common issues I might encounter with Samba on Windows 7?

One common issue you might encounter with Samba on Windows 7 is connectivity problems. This can occur if the Samba configuration file is not set up correctly, or if the server name or workgroup is not specified correctly. You might also encounter issues with authentication, such as being unable to log in to the Samba share.

Another common issue is slow performance or slow file transfer speeds. This can occur if you have a large number of files to transfer, or if your network connection is slow. To resolve this, try using the smbfs file system instead of the default cifs file system, or use a third-party file transfer utility that supports Samba. Additionally, make sure to update your Samba installation regularly to ensure you have the latest performance optimizations.

Enterprise Networking Planet content and product recommendations are editorially independent. We may make money when you click on links to our partners. Learn More.

Windows 7 is out, and everyone says they are going to upgrade, finally. What does this mean for your Samba servers? In this article we will talk about our experience using Windows 7 with Samba, both as a domain controller and as a basic file server.

Samba is not important just for those rogue sysadmins who try to avoid buying Windows Server products. Samba is used by storage appliance manufacturers and within a wide variety of other embedded devices. Samba interoperability is therefore important for both IT shops that run Linux servers, and businesses that sell Linux-based devices. Microsoft may not, contrary to popular belief, intentionally break Samba, but updates to the protocol and client default settings (due to complaints about security in the Windows world) often leave Samba unable to operate, which brings us to some good news:

This time, with Windows 7, only half of Samba stops working.

Accessing Samba Shares

Accessing Samba shares from Windows 7 “just works.” That is, assuming you’re running a relatively recent version of Samba. Samba 3.3.2, which ships with Ubuntu Jaunty, works perfectly with Windows Vista and therefore Windows 7 (they are the same, really). In testing, we had no problem connecting to various different Samba servers and Windows XP-based shares.

If you are stuck with an older version of Samba and cannot upgrade, workarounds do exist. Many NAS devices still run Samba 2.x, and do not have an upgrade mechanism. Before modifying all your Windows 7 machines’ registries, it is worth checking with the manufacturer of your storage device to inquire about an upgrade. Failing that, you must “degrade” Windows 7.

Go to: Control Panel -> Administrative Tools -> Local Security Policy
Select: Local Policies -> Security Options

As shown in Figure 1, there are two settings to change.
“Network security: LAN Manager authentication level” -> Send LM & NTLM responses
“Minimum session security for NTLM SSP” -> uncheck: Require 128-bit encryption

Figure 1. Click for a larger image.

After these two settings have been changed, you will be able to connect to older Samba-based file shares.

If problems still exist, one final thing to try is removing the stored credentials for the Samba share. During testing, it’s possible that something strange got “stuck” in there. In the Control Panel -> Credential Manager, find and remove the stored credentials for the Samba server.

The “just works” comment should be true for people with an already-working Samba setup, who need to allow access from new Windows 7 clients. If you are trying this for the first time, we have left out a lot of details. Start the Samba project’s own documentation.

Joining to a Samba Domain Controller

To join a Windows 7 workstation to your Samba domain controller, you must be running Samba 3.3.4 or higher. It also requires registry hacks within the Windows 7 machine due to security upgrades from Microsoft. Microsoft is not intentionally breaking Samba support, they are simply forcing the Windows Server world to upgrade and deploy more secure mechanisms. Samba often gets caught in the crossfire of forced security hardening, but this is to be expected given that Microsoft doesn’t work with or inform the Samba team of upcoming changes.

Failure to join a Samba domain is confusing. The error, as seen in Figure 2, will state, “The specified domain either does not exist or could not be contacted.” If the domain controller really was inaccessible, you would get another error, before Windows asked for credential to join the machine to the domain. That error would explain how a domain controller was not found. This error, however, really has nothing to do with a connection error.

Картинка с сайта: www.enterprisenetworkingplanet.com

Figure 2. Some Windows errors are needlessly confusing.

To get Windows 7 clients to connect to the domain running Samba 3.3.4 or higher, four registry keys need to be changed. For the ones that don’t exist, create them.

Two dword keys within HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesLanmanWorkstationParameters:

«DomainCompatibilityMode» = 1
«DNSNameResolutionRequired» = 0

And two within HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesNetlogonParameters:

«RequireSignOnSeal» = 0
«RequireStrongKey» = 0

After setting these, you should be able to join the machine to the existing Samba-run domain. Again, this is assuming you’re working in an already-working environment. Configuring Samba to act as a domain controller is covered in the article, Build a Primary Domain Controller With Samba.

If you are adding a new Windows 7 machine to the domain, don’t forget to create the machine account in Samba, after the Unix account exists. In Samba: ‘useradd -a -m HOSTNAME’. And finally, remember that when joining the Windows 7 machine to the domain, you must use an account that has credentials to add machines.

Windows 7 is largely the same as Vista, so figuring out other problems that crop up doesn’t take long, since people have been using and testing the operating system for a few years now. If you are planning to run a Samba domain controller for Windows 7 workstations, we recommend automating those registry setting changes within your installation environment.

Overall, Windows Vista/7 didn’t present many surprises. The most common use case of Samba, as just a basic file server, works flawlessly assuming you have a fairly recent version of Samba. Most IT environments running a few Samba shares mixed within a Windows network, should have no problem supporting Windows 7 clients.

Сетевой протокол SMB (Server Message Block) используется для предоставления совместного удаленного доступа к файлам, принтерам и другим устройствам через порт TCP 445. В этой статье мы рассмотрим: какие версии (диалекты) протокола SMB доступны в различных версиях Windows (и как они соотносятся с версиями samba в Linux); как определить версию SMB на вашем компьютере; и как включить/отключить клиент и сервер SMBv1, SMBv2 и SMBv3.

Версии протокола SMB в Windows

Есть несколько версии протокола SMB (диалектов), которые последовательно появлялись в новых версиях Windows:

Для реализации протокола SMB в Linux/Unix системах используется samba. В скобках мы указали в каких версиях samba поддерживается каждый диалект SMB.

• CIFS — Windows NT 4.0;
• SMB 1.0 — Windows 2000;
• SMB 2.0 — Windows Server 2008 и Windows Vista SP1 (поддерживается в Samba 3.6);
• SMB 2.1 — Windows Server 2008 R2 и Windows 7 (поддерживается в Samba 4.0);
• SMB 3.0 — Windows Server 2012 и Windows 8 (поддерживается в Samba 4.2);
• SMB 3.02 — Windows Server 2012 R2 и Windows 8. 1 (не поддерживается в Samba);
• SMB 3.1.1 – Windows Server 2016 и Windows 10 (не поддерживается в Samba).

Начиная с версии Samba 4.14, по умолчанию используется SMB2.1.

При сетевом взаимодействии по протоколу SMB между клиентом и сервером используется максимальная версия протокола, поддерживаемая одновременно и клиентом, и сервером.

Ниже представлена сводная таблица, по которой можно определить версию протокола SMB, которая выбирается при взаимодействии разных версий Windows:

К примеру, при подключении клиентского компьютера с Windows 8.1 к файловому серверу с Windows Server 2016 будет использоваться протокол SMB 3.0.2.

Согласно таблице Windows XP, Windows Server 2003 для доступа к общим файлам и папкам на сервере могут использовать только SMB 1.0, который в новых версиях Windows Server (2012 R2 / 2016) может быть отключен. Таким образом, если в вашей инфраструктуре одновременно используются компьютеры с Windows XP (снятой с поддержки), Windows Server 2003/R2 и сервера с Windows Server 2012 R2/2016/2019, устаревшие клиенты не смогут получить доступ к файлам и папкам на файловом сервере с новой ОС.

Если Windows Server 2016/2012 R2 с отключенным SMB v1.0 используется в качестве контроллера домена, значить клиенты на Windows XP/Server 2003 не смогут получить доступ к каталогам SYSVOL и NETLOGON на контроллерах домена и авторизоваться в AD.

На старых клиентах при попытке подключиться к ресурсу на файловом сервере с отключенным SMB v1 появляется ошибка:

The specified network name is no longer available

Как проверить поддерживаемые версии SMB в Windows?

Рассмотрим, как определить, какие версии протокола SMB поддерживаются на вашем компьютере Windows.

В Windows 10, 8.1 и Windows Server 2019/2016/2012R2 вы можете проверить состояние различных диалектов SMB протокола с помощью PowerShell:

Get-SmbServerConfiguration | select EnableSMB1Protocol,EnableSMB2Protocol

Картинка с сайта: winitpro.ru

Данная команда вернула, что протокол SMB1 отключен (
EnableSMB1Protocol=False
), а протоколы SMB2 и SMB3 включены (
EnableSMB1Protocol=True
).

Обратите внимание, что протоколы SMBv3 и SMBv2 тесно связаны между собой. Нельзя отключить или включить отдельно SMBv3 или SMBv2. Они всегда включаются/отключаются только совместно, т.к. используют один стек.

В Windows 7, Vista, Windows Server 2008 R2/2008:

Get-Item HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters | ForEach-Object {Get-ItemProperty $_.pspath}

Если в данной ветке реестра нет параметров с именами SMB1 или SMB2, значить протоколы SMB1 и SMB2 по умолчанию включены.

Картинка с сайта: winitpro.ru

Также в этих версиях Windows вы можете проверить, какие диалекты SMB разрешено использовать в качестве клиентов с помощью команд:

sc.exe query mrxsmb10

SERVICE_NAME: mrxsmb10
TYPE : 2 FILE_SYSTEM_DRIVER
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

sc.exe query mrxsmb20

SERVICE_NAME: mrxsmb20
TYPE : 2 FILE_SYSTEM_DRIVER
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

В обоих случаях службы запущены (
STATE=4 Running
). Значит Windows может подключаться как к SMBv1, так и к SMBv2 серверам.

Вывести используемые версии SMB с помощью Get-SMBConnection

Как мы говорили раньше, компьютеры при взаимодействии по протоколу SMB используют максимальную версию, поддерживаемую как клиентом, так и сервером. Для определения версии SMB, используемой для доступа к удаленному компьютеру можно использовать командлет PowerShell
Get-SMBConnection
:

Картинка с сайта: winitpro.ru

Версия SMB, используемая для подключения к удаленному серверу (ServerName) указана в столбце Dialect.

Можно вывести информацию о версиях SMB, используемых для доступа к конкретному серверу:

Get-SmbConnection -ServerName servername

Если нужно отобразить, используется ли SMB шифрование (появилось в SMB 3.0), выполните:

Get-SmbConnection | ft ServerName,ShareName,Dialect,Encrypted,UserName

Чтобы на стороне сервера вывести список используемых клиентами версий протокола SMB и количество клиентов, используемых ту или иную версию протокола SMB, выполните команду:

Get-SmbSession | Select-Object -ExpandProperty Dialect | Sort-Object -Unique

Картинка с сайта: winitpro.ru

В нашем примере имеется 825 клиентов, подключенных к серверу с помощью SMB 2.1 (Windows 7/Windows Server 2008 R2) и 12 клиентов SMB 3.02.

С помощью PowerShell можно включить аудит версий SMB, используемых для подключения:

Set-SmbServerConfiguration –AuditSmb1Access $true

События подключения затем можно извлечь из журналов Event Viewer с помощью PowerShell:

Get-WinEvent -LogName Microsoft-Windows-SMBServer/Audit

Об опасности использования SMBv1

Последние несколько лет Microsoft из соображений безопасности планомерно отключает устаревший протокол SMB 1.0. Связано это с большим количеством критических уязвимостей в этом протоколе (вспомните историю с эпидемиями вирусов-шифровальщиков wannacrypt и petya, которые использовали уязвимость именно в протоколе SMBv1). Microsoft и другие IT компании настоятельно рекомендуют отказаться от его использования.

Однако отключение SMBv1 может вызвать проблемы с доступом к общий файлам и папкам на новых версиях Windows 10 (Windows Server 2016/2019) с устаревших версий клиентов (Windows XP, Server 2003), сторонних ОС (Mac OSX 10.8 Mountain Lion, Snow Leopard, Mavericks, старые версии Linux), различных старых NAS устройствах.

Если в вашей сети не осталось legacy устройств с поддержкой только SMBv1, обязательно отключайте эту версию диалекта в Windows.

В том случае, если в вашей сети остались клиенты с Windows XP, Windows Server 2003 или другие устройства, которые поддерживают только SMBv1, их нужно как можно скорее обновить или тщательно изолировать.

Включение и отключение SMBv1, SMBv2 и SMBv3 в Windows

Рассмотрим способы включения, отключения различных версий SMB в Windows. Мы рассматриваем отдельно включение клиента и сервера SMB (это разные компоненты).

Windows 10, 8.1, Windows Server 2019/2016/2012R2:

Отключить клиент и сервер SMBv1:
Disable-WindowsOptionalFeature -Online -FeatureName smb1protocol

Отключить только SMBv1 сервер:
Set-SmbServerConfiguration -EnableSMB1Protocol $false

Включить клиент и сервер SMBv1:
Enable-WindowsOptionalFeature -Online -FeatureName smb1protocol

Включить только SMBv1 сервер:
Set-SmbServerConfiguration -EnableSMB1Protocol $true

Отключить сервер SMBv2 и SMBv3:
Set-SmbServerConfiguration -EnableSMB2Protocol $false

Включить сервер SMBv2 и SMBv3:
Set-SmbServerConfiguration -EnableSMB2Protocol $true

Картинка с сайта: winitpro.ru

Windows 7, Vista, Windows Server 2008 R2/2008:

Отключить SMBv1 сервер:

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

Картинка с сайта: winitpro.ru

Включить SMBv1 сервер:
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB1 -Type DWORD -Value 1 –Force

Отключить SMBv1 клиент:

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

Включить SMBv1 клиент:

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

Отключить SMBv2 сервер:

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

Включить SMBv2 сервер

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

Отключить SMBv2 клиент:

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

Включить SMBv2 клиент:

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

При отключении SMB 1.0/CIFS File Sharing Support в Windows вы можете столкнуться с ошибкой “0x80070035, не найден сетевой путь”, ошибкой при доступе к общим папкам, и проблемами обнаружения компьютеров в сетевом окружении. В этом случае вместо служба обозревателя компьютеров (Computer Browser) нужно использовать службы обнаружения (линк).