SAMBA error "sytem not accessible / The remote procedure call fai led"

MCCALL,DON (HP-USA,ex1) don_mccall at
Mon Jan 29 22:36:49 GMT 2001

Hi Eric,
We're about to gr the 2.0.7 version of Samba/iX here at HP for MPE/iX
version 6.5; I have tested this and don't have this problem there.  But if
you'de like to set your log level = 10 in smb.conf and try again (with
\\servername) from your nt client, I'd be glad to take a look at the logfile
and see if I can see what the problem is.
Hope this helps,

-----Original Message-----
From: Jansen, Eric [mailto:Eric_Jansen at]
Sent: Monday, January 29, 2001 12:16
To: 'samba at'; 'HP3000-L at RAVEN.UTC.EDU'
Subject: SAMBA error "sytem not accessible / The remote procedure call
fai led"

Hi all,

I have setup Samba 2.0.3 on my HP3000 system running MPE version 6.0.
I used to have 1.9.16p9.

Ever since I upgraded to 2.0.3 I cannot see the list of available shares
from my NT workstation using \\cditest or clicking on the system in Network
I tried with different usernames: MANAGER.SYS, ERIC.SAMBA, MGR.SAMBA

I am able to connect to the shares seperately by mapping them.

Here are my config files:
ERIC.SAMBA = ejansen

global part of smb.conf:

# you MUST supply IP address and subnet mask of your 3000 here

  interfaces =

  time offset = -300

# config file and log file used by smbd and nmbd are typically
# specified as command line options, unless you are using macros
# like eg %S or %m to get different files for each service or
# client machine, which allows very sophisticated (albeit complex)
# configurations (also see "include" directive and smb.conf doc)

 config file = /usr/local/samba/lib/smb.conf

# We set a separate log file for each machine that connects
 log file = /usr/local/samba/var/log.%m

# fix for smbstatus error
 log level = 3
 max log size = 100000

# mapping of incoming usernames is possible and may e.g. be used
# to allow clients using Unix or PC style names like root or lappel
# instead of MPE style names like manager.sys or lars.appel

# multiple alias names are possible e.g. lars.appel = lappel lars
# security = share is needed to be able to see the shares allowed
# when logged on the system directly

  security = share
  username map = /usr/local/samba/lib/
  unix password sync = false
  browse list = yes
# nt support =yes will samba make to act as old version
#  nt smb support = yes
  null passwords = yes

# printcap file lists printer names for use by [printers] section

  printcap name = /usr/local/samba/lib/printcap

# how much detail you want in the logfile (try 3 or 5 or higher)
  debug level = 5

# can use a shell script if system does not supply statfs() routine

  dfree command = /usr/local/samba/lib/myfree

# used in conjunction with printcap file and [printers] section

  load printers = yes

# the workgroup that your server belongs to

  workgroup = CDILLC

# these can be used e.g. to create logon/logoff like console messages

  preexec =  /usr/local/samba/lib/tellop tcon %S %u %m %I
  postexec =  /usr/local/samba/lib/tellop tdis %S %u %m %I

# Deal "gracefully" with long file names

   mangled names =yes

# Do not force downshift of all upper-case filenames to lower case
# else, copying directories fails ( looks for upper case names)
   preserve case = yes
# Preserve case, even for 8.3 files
   short preserve case = yes

# shares may be configured to accept connections without a validated
# user id and password (similar to anonymous ftp) and then assume the
# guest logon identity for accessing files and printers

  guest account = %S

  admin users = MANAGER.SYS

# ---------------------------------------------------------------------


Does anybody know how to resolve this issue, what the settings are?


Eric Jansen

More information about the samba mailing list