SAMBA problem

[Michael Short/Towers Perrin]

I thought it might more productive to ask the question here due to the scope of
the probable audience.

I have installed SAMBA 2.0.5a from an RPM which part of the LINUX/390 2.2.15
maintained at Marist.edu.

When I start SAMBA start it says both smbd & nmbd are running ( doing a SAMBA
status gives the same thing). However when I bring up SWAT and ask for status it
says that both are not running. I can't check with SMBCLIENT because it gives:

[root at vmlnx001 /etc]# smbclient -L vmlnx001
Added interface ip=158.82.172.131 bcast=158.82.255.255 nmask=255.255.0.0
error connecting to 158.82.172.131:139 (No buffer space available)
Connection to vmlnx001 failed

NMBLOOKUP gives a comparable response:

  [root at vmlnx001 sbin]# nmblookup -B vmlnx001 __SAMBA__
Sending queries to 158.82.172.131
Packet send failed to 158.82.172.131(137) ERRNO=No buffer space available
name_query failed to find name __SAMBA__

SWAT can do the configuration part and knows about the lock file so there is
connectivity, but it can't do the status portion.

>From the diagnostics test,

Test 1    Works
Test 2    Work
Test 3    Fails     See above

A NETSTAT -a shows the proper listen
Both smbd and nmbd are running as deamons verified by a PS.

An SMBSTATUS gives the following:

 [root at vmlnx001 sbin]# smbstatus -L vmlnx001

No locked files

Share mode memory usage (bytes):
   1048464(99%) free + 56(0%) used + 56(0%) overhead = 1048576(100%) total

It would seem that the "No buffer space available" message is the key but right
off hand I dont have a way of verifying that or correcting it if it is the
problem.

Any help would be greatly appreciated.