Solve the problem that Windows 7 client cannot access the Samba server

Fault description:

A friend's notebook (OS: Windows 7 flagship version, installed version of the pirated System) encountered a fault in trying to access the Samba server (which was already set up and has been running well. This means that the Samba server cannot find the shared content after the network is enabled.

Fault analysis:

Because the Samba server is configured by me, Samba runs in Working Group mode and the working group is set to workgroup. The client is in the intranet and is in the same subnet as the Samba server. The Samba server has been built and runs well. There is no possibility of problems on the server side. Therefore, I checked the configuration of the client and found that the Network was not enabled and the Working Group of the client was not working properly. The Working Group is unavailable, as shown in:

But in fact, the Working Group of this computer is Workgroup ,:

Therefore, we only need to solve the two problems analyzed above.

Solution:

Based on experience, this problem occurs in the Windows operating system because the related services are not enabled, as shown in (the functions of this service are described in each figure.

1. Workstation

2. Server

3. Computer Browser

After modification, we found that after starting the services listed above, we can use the Working Group and access Samba normally.

It is worth noting that:The computerbrowser Service (network discovery) depends on the preceding two services (server and workstation, as shown in ).

So far, the fault has been successfully ruled out.

Summary:

For management and maintenance personnel: Generally, the normal operation of an operating system (such as Windows) function is closely related to the services provided by the system. As described above (of course, there are no exceptions in the Linux system, and various services correspond to a daemon process, for example, you can enter 'service SMB status' in the command line to view the running status of SMB '). Sometimes it is better to use a graphical interface for management than to use a command line for efficiency, and sometimes operations cannot be completed. For example, if you want to view the started service or the running status of the service, you can use the command line to view it quickly. And so on.

For end users of windows, I strongly recommend that you use a genuine system to avoid problems that may easily be overlooked in the operating system itself. Even if you don't want to buy a genuine version, it should at least be installed (of course, I cannot guarantee that there will be no problem, because it depends entirely on the user's settings ). It is not unreasonable for Microsoft or product manufacturers to say so. More vulnerabilities, security risks, and unpredictable errors may exist in a cut-down and optimized DIY non-genuine system.

PS: in many cases, administrators or maintenance personnel say that this is probably because the client system is pirated, and it is not for no reason, this is probably the reason!

This article from "communication, my favorite" blog, please be sure to keep this source http://dgd2010.blog.51cto.com/1539422/835765