Very Computer

I'm logged into both systems as a user with the same name (Norm) and the
same password (none).
I've set the regedit key at
/HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/VxD/VNETSUP...
EnablePlainTextPassword  to  1

I can mount all of the directories from Win system #1 on the Linux machine
with no problem.  

I can't mount any of the directories from Win system #2 (diagnostic is
"invalid argument" with the additional error message:
"smb_dont_catch_keepalive: server->data_ready == NULL"  but I can ping Win
system #2 from the Linux machine by name successfully and the IP address is
correct.

From Win system #1, when I try to "map network drive" in explorer, I'm
asked for a password and nothing I say is acceptable.  I haven't tried it
from Win system # 2 yet.

What am I doing wrong?

Thanks for all suggestions.
        Norm D.

        The common user on both computers had no password.  It was necessary to
tell Samba
        null password = yes
before it would allow computer #1 access.

(Of course, the Linux box and computer #2 still refuse to acknowledge each
other's presence.  Ah, well ...)

        Norm D.

Quote:> Linux System is a Pentium running Redhat 5.0
> Two Windoze systems.  #1 is running Win95 (Original release) with service
> pack 1 installed.
> #2 is running Win95 OSR 2.

> I'm logged into both systems as a user with the same name (Norm) and the
> same password (none).
> I've set the regedit key at
> /HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/VxD/VNETSUP...
> EnablePlainTextPassword  to  1

> I can mount all of the directories from Win system #1 on the Linux
machine
> with no problem.  

> I can't mount any of the directories from Win system #2 (diagnostic is
> "invalid argument" with the additional error message:
> "smb_dont_catch_keepalive: server->data_ready == NULL"  but I can ping
Win
> system #2 from the Linux machine by name successfully and the IP address
is
> correct.

> From Win system #1, when I try to "map network drive" in explorer, I'm
> asked for a password and nothing I say is acceptable.  I haven't tried it
> from Win system # 2 yet.

> What am I doing wrong?

> Thanks for all suggestions.
>    Norm D.

As for your windows box #2, i suspect it's a "netbios over tcp"
problem. With some versions of windows, you'll have to enable
this for *all* tcp->interface bindings (not only tcp->ethernet
but also tcp->modem & tcp->what_so_ever, including even tcp->AOL,
if you happen to have that), or else it won't work. Very annoying -
took me quite some time to figure that out.

For security reasons, you'll probably want to remove all service
bindings for tcp->modem etc. Check those after any change you make
in the windows network config, since windows tends to turn these
bindings back on if you change the network setup.

Hope this helps