OK,
  I just removed all of the networking configs from my Win 95 laptop,
rebooted then put the pieces in one at a time to verify what the "minimum"
configuration to get at Samba as a client really was.  Here you go:

1.  Client for Microsoft Networks (type = client)
2.  A network adapter of some type (type = adapter)
3.  TCP/IP (type = protocol)

  That's it.  Now if you also want to use smbclient on the 3000 to access
printers or shares on your WIN95 system, you need to add:

4.  File and Print Sharing for Microsoft Networks (type = service)

  Denys Beauchemin from HiComp has excellent information on Windows 95
network configuration for accessing the HP3000.  His main point is to get
access for a terminal emulator, but he shows the setup for my steps 1-3
above as well.  You can view this info at (I hope you don't mind Denys :)
"http://www.hicomp.com/hicomp/win95tnt.htm"

  The main thing to take away with you from the above is that the file
and print sharing client only uses TCP/IP as its protocol, so that's what
you need to concern yourself with for Samba.  You may need NETBUEI
or IPX/SPX for other things (I needed to load IPX/SPX so I could use
my LaserJet IIIP connected to a JetDirect EX Plus box, but I did that
after I verified that the Samba access didn't need it).

Regards,
Michael L Gueterman
Easy Does It Technologies
email: [log in to unmask]
http://www.editcorp.com
voice: (509) 943-5108
fax:   (509) 946-1170

----------
From:  Jeff Kell[SMTP:[log in to unmask]]
Sent:  Wednesday, March 12, 1997 11:41 AM
To:  [log in to unmask]
Subject:  Re: [HP3000-L] Samba/iX and Windows 95 (works for me)

Lars Appel wrote:

> The Network Neighbourhood Properties shows...
>
> a. Client for Microsoft Networks
> b. AMD PCNET Family Ethernet Adapter
> c. IPX/SPX-compatible Protocol
> d. NetBEUI
> e. TCP/IP

NetBEUI?  I don't have that.  What does it bind to (what properties
need be defined?)

Jeff