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

John Santos john.santos at post.harvard.edu
Tue Sep 14 00:22:49 GMT 2004


At 04:52 AM 9/13/2004 +0000, Ashot Bord wrote:
> >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.
>
>In this case in fact it may point that W2K host doesn't recognize your 
>\\VAX host,
>if you're not running DNS or WINS, in order for WIN hosts to reocognize 
>"other" hosts,
>you may need to add those other hosts into HOSTS (or/and LMHOSTS -- no 
>extension!) files
>either in \windows dir or \windows\system32\etc, you may search for that 
>name in you windir.
>Indication that it does find your non-WIN host is successful eg.:
>PING \\VAX

I have DNS configured on my LAN.  In fact the VAX is the LAN DNS server.

There were both a hosts and lmhosts files in \winnt\system32\drivers\etc
Is this the right place?  Hosts only had 127.0.0.1 in it.  lmhosts had
the w2k and w98 systems listed.  I added the VAX to both.

Is the PING syntax above correct?  PING VAX works fine.  PING \\VAX
produces (after a long timeout) Unknown host \\VAX

>In my case all hosts can see each other, VAX can connect to WIN shares,
>but WIN hosts cannot connect to \\VAX SAMBA-share with error 54.

Well, the W2K PC can see the VAX; it shows up in Windows Explorer
under "computers near me" and under "Entire network\
Microsoft Windows Network\Home", but if I click on it in either place to
expand it,  it says "\\VAX is not accessible.  The network path was not found."

(On the VAX, an SMBD process gets started, grinds for a while, and
disappears.  All it leaves in the log file is a "Started" message.)

>I start thinking it's somehow related to the TCPIP 5.1 ECO 5, I heard 
>there was bug,
>that was causing some racing condition for the socket, and it would lead 
>to application failing
>to obtain the socket -- something I could see from the SMBD_STARTUP-log, 
>while probably
>in interactive mode that condition may favor the application ?? Well, I 
>don't have TCPIP 5.3/4
>to test if SAMBA would work on VAX.

In my case it is definitely not TCPIP 5.1 ECO 5, since I am running
TCPware.  (Just had to change the SAMBA_STARTUP.COM to use the tcpware
syntax for defining a server instead of the UCX syntax.)






>For now search continues. More opinions are needed!
>
>AB



John Santos




More information about the samba-vms mailing list