Configuring and Managing MPE/iX Internet Services (August 2002)

Chapter 7
Samba for MPE/iX Services
Troubleshooting Samba for MPE/iX Server
113
Troubleshooting Procedures
Please follow these tests for diagnosing your Samba for MPE/iX server.
TEST 1:
In the directory in which you store your smb.conf file, run the command testparm smb.conf.
If it reports any errors, your smb.conf configuration file is faulty.
TEST 2:
On the client side; open MS-DOS prompt and run “ping SAMBAIXSERVER” from the PC and “ping
CLIENTPC” from the HP e3000 system. If you don’t get a valid response, your TCP/IP software is not
correctly installed.
If you get a message saying “host not found” or similar, your DNS software or hostname is not correctly set up.
Ping might fail, if your host is running firewall software. You will need to relax the rules to let in the
workstation in question, perhaps by allowing access from another subnet.
TEST 3:
Run the command “smbclient -L SAMBAIXSERVER” on the HP e3000 system. You should get a list of
available shares back.
If you get a “connection refused” response, then the SMBD server could not be running.
If you get a “session request failed,” the server refused the connection to SMBD. Check your config file
(smb.conf) for syntax errors with “testparm” as well as the various directories where Samba for MPE/iX
keeps its log and lock files.
Another common cause of these two errors is having something already running on port 139 (as in the case of
NBMON/NBDAEMON) or SMBD already running under INETD.
And yet another possible cause for failure of TEST 3 is when the subnet mask and/or broadcast address
settings are incorrect. Check to see whether the network interface IP Address/Broadcast Address/Subnet
Mask settings are correct and Samba for MPE/iX has correctly noted these settings in the log.nmb file.
TEST 4:
Run the command “nmblookup -B SAMBAIXSERVER __SAMBA__” on the HP e3000. You should get the IP
address of your Samba for MPE/iX server.
If you don’t get the IP address, NMBD is incorrectly installed. Check your INETD, if you run it from there, or
check to see whether the daemon is running and listening to UDP port 137.
Check your INETD entries related to nmbd, as discussed earlier.
TEST 5:
Run the command “nmblookup -B CLIENTPC '*'” on the HP e3000.
You should get the PCs IP address. If you don’t get the PCs IP address, the client software on the PC is not
installed correctly, the PC is not started, or you have the name of the PC wrong.
TEST 6:
Run the command “nmblookup -d 2 '*'” on the HP e3000.