smbd serves connects only when ran in interactive mode (-i)

Ashot Bord abord at chek.com
Sat Sep 11 22:08:42 GMT 2004


I recently installed the newly released vms samba 2.2.8 build 20040908 (openVMS 7.3/TCPIP 5.1).

After simple configuration (public share, map to guest etc.). I was able to connect successfully with SMBCLIENT to the VAX share from VAX _itself, and it also appeared in the Network Neighborhood and I was able to connect _from VAX to WIN98 shares. However the other way around from WIN98 _to VAX share results in WIN ERROR 54: network busy, or insuficient resources.

After long and painstaking insvestigation and numerous RFMs, I didn't find any inconsistency in the config and general settings.  The logs suggest that when receiving external (WIN98) request smbd fails to obtain socket (claming 0 is the last call before socket mess), and subsequently fails to serve the request.

Finally I tried to start smbd in interactive mode (-i) (well, after disabling its service from tcpip, defining tmp and tempdir as in smbd_startup.com) from the SYSTEM account:
$ MC SAMBA_EXE:SMBD "-id5"

and  miraculously I was able to connect from WIN98 _to the VAX share and use it successfully, well dramatically slower than FTP, still functional).

However it would still not serve the connects when ran as an tcpip service.

Does anybody have ideas what could be the obstacle/difference in this case. I tried to look into quota and priority settings, but can't understand what to tweak if it uses the same SYSTEM account in both modes).

BTW: the system is vanilla vms7.3 install, so the original quotas etc. are at their defaults.

I would appreciate all relevant opinions.

AB






More information about the samba-vms mailing list