Has anyone had a problem with Samba looping?  A few minutes ago ALL
activity on the HP LAN segment came to a stop.  The activity and collision
indicators on the hubs were "on" all the time.  The HP 3000 hosting Samba
did respond through the console, but very slowly.  They have GLANCEXL here,
so it was run on the console.  It showed Samba using 64% of the cpu.  We
aborted the Samba job, and within 5 seconds everything was back to normal.

Has anyone had any similar experiences?

Thanks,

John
--------------------------------------------------------------
John Korb                            email: [log in to unmask]
Innovative Software Solutions, Inc.

The thoughts, comments, and opinions expressed herein are mine
and do not reflect those of my employer(s), or anyone else.