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
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
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
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
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.
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
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
