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

Chapter 7 117
Samba/iX Services
Troubleshooting Samba/iX Server
Some other tests, along with the ones mentioned previously, might be
useful. These tests can be done to check the behavior of the Samba/iX
server with these security policies:
1. Configure Samba/iX in User security mode:
• map a PC username to a valid MPE/iX username.account with
passwords
• verify file and print access work
• verify files created by PC user are owned by correct MPE/iX
username and account
• verify full file read and create access to the user’s default home
share.
2. Configure Samba/iX in Share security mode, and set passwords on
file shares.
• verify that the file and print access from PC users works.
3. Configure Samba/iX in Server security mode, pointing user
validation to a NT server.
• verify users logged into the Windows NT domain being used as a
validation server have the appropriate access to shares and
printing on Samba/iX.
4. Perform PC connectivity and file/print access tests with SMBD and
NMBD in daemon mode (for example, started from MPE/iX jobs
JSMB and JNMB) as well as started from INETD as services.
5. Verify all functionality works when the daemons or services are
running as the default mgr.samba. If any funtionality does not
work, check if any change needs to be done in the default capabilities
of mgr.samba.
Using Logfiles of Samba/iX
In case of problems, check for the job listings for useful error messages
and also look into the Samba/iX log file
/usr/local/samba/var/log.smb and log.nmb for hints. You can
control amount of log messages with the “debug level” directive inside
the config file smb.conf.
Increasing the log level to 3 or 4 can shed light on the cause of most
problems. This also may lead to a large amount of details to be logged
into these files.
You may have to increase the size of your log file if your debug level is
more than 3.