Solaris Troubleshooting : Samba
Below instruction help you to understand, analyse and troubleshoot the problems with Samba service
Step1. Ensure Basic Connectivity
1.) Try pinging your Samba server from itself using localhost, the actual IP address, and DNS name of the samba server.
2.) Try pinging the samba server from one of the windows clients by IP address and DNS name.
3.) Verify that a firewall is not blocking any traffic from the windows clients for ports 135/udp, 137/udp, 138/udp, 139/udp, 445/tcp
4.) Verify that a firewall is not blocking any icmp traffic from the windows clients for types 0, 3, 4, 8, 11, and 12.
Step2. Verify for Proper Samba Configuration
1.) Verify that /etc/samba/smb.conf exists and run testparm to validate the syntax.
2.) Verify that all the required Daemons are running file on host1
2. 1. Verify that smbd is running using
# ps aux
2.2. Verify that nmdb is running using
# ps aux
Step3. Verify for NetBIOS Name Resolution
1.) From the host1 , verify that the nmbd server can be queried for its own NetBIOS name.
# nmblookup -B example-server _SAMBA_
2.) From the host1, verify that the nmbd server can be queried for any
# NetBIOS client name.
# nmblookup -B example-client ‘*’
3.) From the host1, verify that the subnet can be queried for any NetBIOS client name.
# nmblookup -d 2 ‘*’
Step4. Verify for Listing Network Shares
1.) From the host1, try to generate a list of valid shares
# smbclient -L example-server
2.) From a windows client, try to generate a list of valid shares
# NET VIEW \example-server
3.) From the host1, verify that the Domain Master Browser can be queried for the host1’s IP address
# nmblookup -M example-wkgrp
4.) From the windows client, verify that the list of available shares can be viewed from Network Neighborhood.
Step5. Verify by establishing a Session
1.) From the host1, try to connect to one of its own shares.
# smbclient //example-server/tmp -Uusername
2.) From a windows client, try to connect to one of the shares
# NET USE X: \example-servertmp