Michael,

E-Mail me privately and I'll give you a hand.  I have it running...

Joe
----------------------------------------------------------------------
Joe Geiser
CSI Business Solutions
140 Bristol-Oxford Valley Road, Suite 102
Langhorne, PA 19047-3083
Toll Free (US/Canada): (888) 956-9812
[log in to unmask] (at work)
[log in to unmask] (at play)
----------------------------------------------------------------------

----------
> From: Michael D. Hensley <[log in to unmask]>
> To: [log in to unmask]
> Subject: Win95 and SAMBA: looking for the final solution.
> Date: Thursday, March 13, 1997 6:05 AM
>
> I'm begging for a Win95 networking guru who can help me solve the
> Win95-to-Samba/iX connectivity problem.  In return, I promise to write
up all
> of the details and post them to HP3000-L and submit it to the HP3000
FAQ.
> I've collected every Samba post to HP3000-L, and tried all of the
various
> tips and suggestions.
>
> Any volunteers?  I can be reached by phone at 541/926-3800, or email me!
>
> Thanks in advance!
>
>
> Here, for review, are the symptoms.
>
> First, my network:
>    LEOPARD is an HP3000 running MPE/iX 5.5 (power patch 1)
>    BOBCAT is an NT 3.51 server
>    FELIX is an NT 4.0 workstation
>    MICHAELH is a Win95 PC
>    We are using a DNS server, but copies of a complete HOSTS file exist
on
>       all systems, too (don't ask).
>    There are no longer an Novell systems anywhere on my network.
>
> Next, a description of MICHAELH:
>    Services
>       Client for Microsoft Networks, which logs on to the NT domain
"LPS"
>       Reflection NFS client (added by Reflection X installation?)
>       File and Printer Sharing for Microsoft Networks
>    Adapters
>       AOL Adapter (a figment of my PC's imagination)
>       Realtek RTL8019 PnP Lan adapter or compatible
>    Protocols
>       NetBEUI -> Realtek RTL8019 PnP Lan adapter or compatible
>       TCP/IP  -> AOL Adapter
>       TCP/IP  -> Realtek RTL8019 PnP Lan adapter or compatible
>       (I'm using the Microsoft TCP/IP stack)
>
> Here's what works:
>    LEOPARD shows up in the Network Neighbourhood on FELIX and MICHAELH
>    FELIX can "see" the shares on LEOPARD (guest1 and guest2)
>    FELIX can create files on LEOPARD
>
> Here's what fails:
>
>    On MICHAELH, if I double-click on LEOPARD in the Network
Neighbourhood, I
> get the following message (after about a 10-second wait):
>    \\Leopard is not accessible.
>    The network is busy.
>
>    It takes more than 10 seconds after double-clicking on LEOPARD in the
> Network Neighbourhood on FELIX to get the list of directories (shares).
>
>
> ---
> Michael D. Hensley             |
> Software Development Manager   | mailto:[log in to unmask]
> Lund Performance Solutions     | http://www.lund.com