Configuring and Managing MPE/iX Internet Services (MPE/iX 6.5)

Chapter 7 111
Samba/iX Services
Troubleshooting Samba/iX Server
If you get a “connection refused” response, then the SMBD server could
not be running.
If you get a “session request failed” then 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/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. Please check that
the network interface IP Address/Broadcast Address/Subnet Mask
settings are correct and that Samba/iX has correctly noted these in the
log.nmb file.
TEST 4: Run the command “nmblookup -B SAMBAIXSERVER __SAMBA__” on the
HP 3000. You should get the IP address of your Samba/iX server.
If you don’t get the IP address, then NMBD is incorrectly installed.
Check your INETD, if you run it from there, or that 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 3000.
You should get the PCs IP address. If you don’t get the PCs IP address,
then 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 3000.
This time try the same as the previous test but, try it via a broadcast to
the default broadcast address. A number of NetBIOS/TCPIP hosts on
the network should respond, although Samba/iX may not catch all of
the responses in the short time it listens. You should see “got a positive
name query response” messages from several hosts.
If this doesn’t give a similar result to the previous test, then nmblookup
isn’t correctly getting your broadcast address through its automatic
mechanism. In this case you should experiment using the “interfaces”
option in smb.conf to manually configure your IP address, broadcast
and netmask.
If your PC, and server aren’t on the same subnet, then you will need to
use the -B option to set the broadcast address to that of the PC’s subnet.
This test will probably fail if your subnet mask and broadcast address
are not correct. (Refer to TEST 3 notes).