John Korb <[log in to unmask]> says...

> Thanks Joe.  What I'm experiencing a "now you see it (Samba), now you
> don't" where Network Neighborhood sees Samba one minute, then the PC
locks
> up, then after the PC reboots, it doesn't see Samba, then later it
> does...
> Oh what a mess...  I suspect some sort of conflict either in the client
> software or a problem with the configuration of the routers between the
PC
> and the HP 3000.  I strongly suspect the client (or ethernet card)
> because
> I'm now experiencing a large number of PC lockups.  Knowing that what
> I'm
> trying to do should work frees me to look in other directions.
>
>
The appearance of your 3000 is the job of NMB - which advertises the
computer name.  I assume you have it running since you can see it.  Here's
something to try...  Set the NMB listener job to run in the CS Subqueue as
opposed to DS.  If the system is loaded, your rebooted system may take
awhile to see the 3000 because NMB is not broadcasting as fast as it
should.

If NMB is running in the CS queue - it gets a higher priority and will
broadcast its name in a more timely fashion, when your PC sends the
NetBEUI packet to collect computer names.

Hope this helps!

Joe