smbd serves connects only when ran in interactive mode (-i)
John Santos
john.santos at post.harvard.edu
Mon Sep 13 00:16:36 GMT 2004
At 10:08 PM 9/11/2004 +0000, you wrote:
>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
I have similar problems with my hobbyist VAX at home, but can't find any
significant differences with
my Alpha at work which works fine. I haven't tried running it in
interactive mode, though.
My VAX is configured like yours. From W2K DOS prompt, net view \\VAX gets
System error 53 has occurred.
The network path was not found.
This seems to be a generic error because I get the same thing from
misspelling the hostname
or by trying to view the W98 PC when it is down, though the error response
seems to happen much
quicker when I use an invalid hostname.
I've always felt it was just too slow and the clients (Win98SE PC and W2K
PC) were just timing out.
I don't know why it would work interactively, but maybe you're right, and
it is some quota issue.
I think (in very brief testing) it worked okay using a Mac Powerbook as the
client, but I didn't
test it much at all. Maybe the Mac just has longer timeouts?
Anyway, if you come up with anything, please send to the mailing list as I
would like to know, too.
John Santos
More information about the samba-vms
mailing list