Configuring and Managing MPE/iX Internet Services (July 2001)

122 Chapter7

Samba for MPE/iX Services

Troubleshooting Samba for MPE/iX Server

This section covers a list of tests you can perform to validate or

diagnose your Samba for MPE/iX server. If your server passes all these

tests, it is probably working ﬁne.

Prerequisites

In all of the tests it is assumed you have a Samba for MPE/iX server

1.19.16p9 or later running on your HP e3000. It is also assumed that

the PC is running Windows for Workgroups, Windows 95 or Windows

NT with a recent copy of the Microsoft TCP/IP stack. All these tests

should be done with Windows for Workgroups (WfW),

Windows 95,Windows 98 and Windows NT clients, as they all use

different SMB’s for ﬁle operations.

You need to have a sample share called “public” for testing purposes.

Check to see if you have “public” share in smb.conf ﬁle:

[public]

comment = files are shared

path = /SAMBA/SHR/public

read only = yes

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 ﬁle, run the

command testparm smb.conf.

If it reports any errors, your smb.conf conﬁguration ﬁle 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 ﬁrewall 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.