Samba common troubleshooting

Samba common troubleshooting-Linux Enterprise Application-Linux server application information. For details, refer to the following section. 1. Actions on the SMB server

1) run the following command to check whether the configuration is incorrect. /Usr/bin/testparm/etc/smb. conf

2). Run the ping command on the server and the client to check whether the TCP/IP works properly.

3). Use the/usr/bin/smbclient-L SMBserver command on the SMB server to get a shared list.

If the error message appears, check the settings of parameters related to the server, such as "hosts allow", "hosts deny", "valid users", and "invlid users. If "connection refused" is displayed, check whether the Samba server process is started. If Samba runs as a daemon, run the "netstat-a" command to check whether the port is in the listening status.

4) if the command "/usr/bin/nmblookup SMBserver" is run, the IP address of the SMB server is returned. Otherwise, nmbd does not run correctly.

5) run the "/usr/bin/nmblookup-d 2 '*'" command. The host running NetBIOS/TCPIP In the subnet will respond. Otherwise, nmblookup cannot obtain the broadcast address correctly. You can use the interfaces parameter in the smb. conf file to manually set the IP address, broadcast address, and subnet mask.

6 ). run the "/usr/bin/smbclient \ SMBserver \ homes" command. Enter the user password of the customer on the SMB server, and a prompt similar to "smb>" appears. In this case, you can use the dir command to browse the files in the account directory of the SMB server, and use the help command to get help from other commands. If a prompt similar to "smb>" cannot appear and there is an "invalidnetwork name" error message, it is possible that the homes sharing is not properly set; or "Bad password ", check
Check the settings of "shadow password", "password encryption", and "valid users" and "path.

2. Operations on SMB clients

1) run the "net view \ SMBserver" command to list shares on the SMB server.

If an error similar to "network name not found" occurs, check the DNS or WINS settings on the client. If an error "Invalid network name" or "bad password error" occurs, follow the troubleshooting methods described in the preceding "smbclient-L" command. Note that the client will connect to the SMB server with the username/password used when the client is registered. Therefore, it is best to have the same username/password on the SMB server.

2 ). run the "net use x; \ SMBserver \ homes" command to map the customer home directory on the SMB server to the client "x:" disk, "x: "It should be an unused disk number on the client. In this way, the shared directory can be viewed as an "x:" disk on the client. The normal information is "command complete successfully ".

If you want to stop using the "x:" disk, you can use the "net use x:/delete" command. If the customer's home directory cannot be mapped to an "x:" disk, check the configuration of parameters such as "hosts allow" on the SMB server. If the user name on the client cannot match
If the user name on the server matches, try to use the "username map" option.

3) If "encrypted passwords" is not used on the SMB server, allow a password in the Registry in the "quot; plain text" format on the client.