Phil Stracchino wrote:
> I've just updated all the existing clients I currently have running from
> v1.36.0 to v1.36.3, and added one new win32 client. This gives me two
> current win32 clients, both of which are new client installs, one
> because it's a new client, one because it was recently reinstalled after
> Windows shot itself in the head (therefore effectively both new).
>
> Of these two clients, the reinstalled former client is working
> perfectly. The brand-new client will not back up. I've tried both
> 1.36.0 and 1.36.3 on it. In either case, the ClientRunBeforeJob job
> runs fine, the backup starts, and then 10 to 60 seconds later, the
> client simply stops sending data.
Oh, I meant to add this:
The client that is working is an Athlon 1200, PCI/AGP, with ATA disk and
a 3Com 100baseTX interface.
The client that drops its connection is an Athlon64 3000+, PCI-E, with
SATA disk and a Marvell 1000baseTX interface.
Both clients are running Windows 2K Pro, fully patched. Both are
connected to the same 100baseTX switch, and both are one hop away from
the Director/SD machine.
--
Phil Stracchino [EMAIL PROTECTED]
Renaissance Man, Unix generalist, Perl hacker
Mobile: 603-216-7037 Landline: 603-886-3518
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
