Re: [Bacula-users] Windows XP networking dies
On Mon, Dec 01, 2008 at 03:10:36PM -0500, Jason Dixon wrote: On Mon, Nov 24, 2008 at 01:21:00PM -0500, Josh Fisher wrote: 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. The new driver didn't help. Installed an Intel card, we'll see how that goes. We've gone through 4 nights of incrementals and our regularly scheduled full backup this evening without any problems. The Friday night full backups were always the trigger event previously. It appears that the nvidia ethernet chipset was the culprit. Thanks, -- Jason Dixon OmniTI Computer Consulting, Inc. [EMAIL PROTECTED] 443.325.1357 x.241 -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Windows XP networking dies
On Mon, Nov 24, 2008 at 01:21:00PM -0500, Josh Fisher wrote: 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. The new driver didn't help. Installed an Intel card, we'll see how that goes. -- Jason Dixon OmniTI Computer Consulting, Inc. [EMAIL PROTECTED] 443.325.1357 x.241 - 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=100url=/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Windows XP networking dies
On Mon, 24 Nov 2008, Josh Fisher wrote: 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. Not just Windows. We found that 3com Torando/Vortex/Boomerang family cards will start barfing all over the network(*) under high loads under Linux (especially on older(**) boxes with high NFS traffic) This also happened (but nowhere near as badly) with cheap and nasty 1Gb/s NE2k NICs (realtek R8193) I dropped in as replacements. (*) Not jabbering, but traffic from the NIC starts appearing on all network ports, somehow becoming unswitchable. This appears to be a Linux networking stack issue. (**) P3-600-1Ghz and early P4s - 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=100url=/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Windows XP networking dies
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? Thanks, -- Jason Dixon OmniTI Computer Consulting, Inc. [EMAIL PROTECTED] 443.325.1357 x.241 - 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=100url=/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Windows XP networking dies
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. 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=100url=/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Windows XP networking dies
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. Thanks, -- Jason Dixon OmniTI Computer Consulting, Inc. [EMAIL PROTECTED] 443.325.1357 x.241 - 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=100url=/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Windows XP networking dies
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=100url=/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
