On Saturday 23 July 2005 22:22, Phil Stracchino wrote: > Kern Sibbald wrote: > > You might make sure you have the latest drivers/firmware for the ethernet > > card in your Windows system that is giving you problems. At least one > > user recently found that this was the cause of his disconnects with a > > Windows machine -- he had a NVidia ethernet card. > > Heh. Funny you should say that -- as I just posted, I just found that > *MY* nVidia gigabit NIC appeared to be causing the problem. When I > switched the machine's connection to its other onboard NIC, which is a > Marvell Yukon PCI-E gigabit NIC, as a test (not expecting it to affect > anything), the problem vanished and the backup is now running perfectly > happily. > > So the FD thought the SD was pulling the plug, and the SD thought the FD > had stopped sending data, and the real cause was that the NIC in between > was dropping the connection....
Hmmm. It looks like NVidia would do better to concentrate on graphics cards and forget trying to network. This is probably the solution to a lot of frustration expressed in the past by quite a number of Bacula users having Windows machines that did not want to communicate correctly. I'll add this to the Windows chapter of the manual ... -- Best regards, Kern ("> /\ V_V ------------------------------------------------------- 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