Similarly, you can create separate logs for each Samba user:įollow these steps to check Samba configuration:Ĭheck the registered users and accounts in the Samba server user database with the pdbedit command:Ĭheck the shares with the smbtree command: Now create a new configuration file for a specific client: First, set the following options under smb.conf to enable client-specific configuration: Increase the log level to get more debugging information:Įnable logging for a specific client with client-specific configuration. This will list all filesystem activities by smbd process:Ĭheck Samba log files for any warning or errors. Use strace to view the Samba process logs. Look for the process name, smbd, in the output of the following command: Use netstat to check the Samba daemon is listening on the network: Use nmblookup to test netbios name resolution for Windows systems.įollow these steps to check Samba service:Ĭheck whether the Samba service has started properly: This may identify the problems with the TCP stack. Try connecting to FTP or a similar TCP service on the Samba server. If the firewall is on, make sure you have allowed the Samba ports as follows: If so, check the allowed ports on your firewall. $ sudo tcpdump -s 0 -w tcpdumps host client_IPĬonnect to the Samba process with telnet:Ĭheck whether your Samba server uses a firewall. If you know the client IP address, you can filter tcpdumps with the following command: $ sudo tcpdump -p -s 0 -w tcpdumps port 445 or port 139 All packets will be logged in a file named tcpdump in the current directory: Start tcpdump as follows and let it run for some time while accessing the Samba server from clients. Use tcpdump to check Samba network communication. Windows uses netbios for name resolution:Ĭheck the Samba configuration for network restrictions. Send ping requests to the Samba server to check network connectivity:Ĭheck name resolution. As a first step for troubleshooting, let's start with network testing.įollow these steps to check network connectivity: We will go through each of them step by step. Samba troubleshooting can be separated in to three parts: network connectivity, Samba process issues, and Samba configuration issues. In this recipe, we will look at the various tools available for troubleshooting Samba shares.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |