On Sat, 11 Jul 1998 samba@samba.anu.edu.au wrote:
> SAMBA Digest 1743
> From: Carlos Vidal <carlos@tarkus.se>
> To: samba@samba.anu.edu.au
> Subject: Problems accessing a W95 share
> Message-ID: <199807091801.SAA03246@tarkus.se>
>
> Hi!
>
> I'm trying to use a printer connected to a Win95 box from Linux but
when I try
> 'smbclient -L win95_machine' I get the following message:
>
> SMBnegprot failed. myname=TARKUS destname=WIN95 - ERRSRV - 1311
>
> I'm using samba-1.9.18p5. The access in the other way (W95 to Linux
shares)
> works without any problems.
>
> When I set the printer as shared in the W95 box it is possible to add
users,
> but the only way is via a select button that hangs up and after a timeout
says
> that it cannot access the user list. I don't know if these things are
related.
> The network tree in W95 looks OK, both the Linux and W95 shares are there.
>
> carlos@tarkus.se
The Win95 box is using USER mode security, that's why it's looking for a
user list from a PDC (or NW server), however, it cannot locate it. It
may be that such a beast is not available for your use, and SHARE mode
security would be more appropriate. In SHARE mode simply specify a
password and Win95 uses that password alone for authentication, there
is no sense of a user name.
Use the Access Control tab of the Win95 Network Control Panel and select
Share-level access control.
> ------------------------------
>
> Date: Thu, 9 Jul 1998 18:06:44 -0400 (Eastern Daylight Time)
> From: Dan Mandell <dmandell@saintmarys.edu>
> To: Multiple recipients of list <samba@samba.anu.edu.au>
> Subject: Problems creating an msdos Samba Boot disk
> Message-ID:
<Pine.WNT.3.96.980709175507.-394695Q-100000@dmandell.saintmarys.edu>
>
> Last year we made up a Dos disk that connects to our Samba server, to
> permit us to download (using "ghost") a disk image to our Dell
Optiplexes.
> We can seem to get last year's boot disks to load; specifically,
netbind
> complains that it can't bind, hardware failure. This year's Dells
come
> with 3Com 3C905b PCI Etherlink cards...last year's model had the 3C905
> version.
>
> I don't as much as I should about the protocols used in Dos and am at a
> loss where to start. The boot disk appears to be loading NDIS LanManager
> stuff, starting with
> LH net initialize
> netbind.com
> LH umb.com
> LH tcptsr.exe
> LH tinyrfc.exe
> LH nmtsr.exe
> emsbfr.exe
> LH net logon ....
>
> If anyone currently doing this can tell me anything about this process
> I might be able to ask DELL or 3Com about possible card changes.
>
> Thanks,
> Dan
>
This is the Microsoft network client or LanManager client.
These clients use NDIS drivers for DOS which depend on a PROTOCOL.INI
file and a SYSTEM.INI file (usually in a NET subdirectory). Note that
these files are used in MS Client 3.0 setup, if this is an older, or
IBM, LanManager setup they may be different.
You may need a new driver for the network card. A good way to work
through this problem would be to obtain MS CLIENT 3.0 from
ftp.microsoft.com/bussys/client (I think) and run the install program.
There may be an option in the install program to allow you to use the
latest 3COM drivers disk for your card.
