Common Errors During SAMBA connection

Article Title: Common Errors During SAMBA connection. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.

Using SAMBA, you can make the Linux server a member of the Windows domain, or allow the Windows client to access the Linux server through network neighbors. However, Windows and Linux are two different operating systems. Even if the SAMBA server provides a platform for both parties to communicate, some problems still occur during the online process. I will explain these common problems today and provide some solutions. We hope this content can help the system administrator solve the problems encountered in daily work.

　　1. The XP client can log on, but the 2000 client cannot.

When I first started using the SAMBA server, I encountered a strange problem. At that time, clients in the enterprise were not completely unified, mainly including 2000 clients and XP clients. When deploying the SAMBA application, we found a strange problem. Only the XP client can access the Linux server through network neighbors, but not other client segments. After a series of measures, I finally found the problem.

This is mainly because the Windows and Linux operating systems have different password processing mechanisms. Currently, mainstream Windows operating systems use encryption to send passwords. On the SAMBA server, the system administrator can determine whether to specify whether the user password must be sent to the SAMBA server in encrypted form and determined by the encrypt passwords option. If this option is set to NO, all Windows clients cannot log on to the Linux server. Therefore, after setting this option to YES, the user password must be encrypted and sent to the SAMBA server. Then all Windows clients can log on to the Linux Server normally.

So why can't I log on to the XP client and the 2000 client? After finding relevant information and testing, we found that if you set the above option to NO, you must modify the client configuration. Copy a file from the SAMBA server package to the client. The Windows client can connect to the Linux Server normally only when encrypt passwords is not enabled.

As shown in, there is a Registry folder under the SAMBA installation directory. Some password processing files are stored in this file. If you set encrypt passwords to NO, you need to copy these files to the corresponding Windows client. Otherwise, you will not be able to log on normally. Copy the Win2000 registry file to the 2000 client and double-click it to directly import the registry value to the Registry. After the client is restarted, the 2000 system will be able to access the Linux Server smoothly.

Therefore, I think the encrypt passwords option is set to YES in most cases. If you have special requirements (for example, for access control purposes), you can set this option to No. Copy these registry files to the corresponding client to ensure that the client segment to be accessed can be normally connected to the Linux server.

[1] [2] [3] [4] Next page