Jason Dixon wrote: > On Mon, Nov 24, 2008 at 12:50:15PM -0500, Josh Fisher wrote: > >> Jason Dixon wrote: >> >>> We have three XP SP2 workstations that all have scheduled Bacula jobs. >>> Two of them run fine. The third one "loses networking" every Friday >>> during the FULL backup job. When it enters this state you can no longer >>> ping the box or perform any networking functionality. >>> Disabling/re-enabling the interface doesn't help. The only remedy is to >>> reboot the box. >>> >>> Has anyone encountered this with XP before? Is it possibly a >>> combination of software that is causing the issue (e.g. AVG)? Any known >>> workarounds? >>> >> This is almost certainly either a buggy NIC driver or a hardware >> (NIC/switch/cable) problem. If all three XP machines have the same NIC and >> driver version, then it's probably hardware. Otherwise, my guess is the NIC >> driver. During a full backup, Bacula, naturally, places a heavy load on the >> NIC, and so Bacula will definitely reveal any underlying network problems. >> I ran into this with a couple of Vista laptops, and also with a nForce430 >> chipset XP machine. I have found it is not uncommon for Windows NIC drivers >> to be buggy. >> > > Someone else suggested that offlist. There was a driver update for the > onboard > nforce ethernet, so I applied that and we'll see how that goes. >
Also, you could try disabling checksum offload and/or segmentation offload in the NIC's advanced settings. > Thanks, > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users