-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Hoogendyk wrote:
>
>
> Ryan Novosielski wrote:
>> Chris Hoogendyk wrote:
>>
>>> Ryan Novosielski wrote:
>>>
I send this note every once in awhile, since I know around my workplace
there is a lot of confusion over it.
B
Ryan Novosielski wrote:
> Chris Hoogendyk wrote:
>
>> Ryan Novosielski wrote:
>>
>>> I send this note every once in awhile, since I know around my workplace
>>> there is a lot of confusion over it.
>>>
>>> Both ends of a network connection must be either hard-coded to the same
>>> speed a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Hoogendyk wrote:
>
> Ryan Novosielski wrote:
>> I send this note every once in awhile, since I know around my workplace
>> there is a lot of confusion over it.
>>
>> Both ends of a network connection must be either hard-coded to the same
>> spee
Ryan Novosielski wrote:
> I send this note every once in awhile, since I know around my workplace
> there is a lot of confusion over it.
>
> Both ends of a network connection must be either hard-coded to the same
> speed and duplex, or set to auto/auto. Any other combination will result
> in the
duplex was not matched.
>
> - Original Message -
> From: "Robert LeBlanc" <[EMAIL PROTECTED]>
> To: "Philip W. Dalrymple III" <[EMAIL PROTECTED]>
> Sent: Wednesday, January 23, 2008 9:58:50 AM (GMT-0500) America/New_York
> Subject: RE: [B
alrymple III" <[EMAIL PROTECTED]>
Sent: Wednesday, January 23, 2008 9:58:50 AM (GMT-0500) America/New_York
Subject: RE: [Bacula-users] Getting an error on many Win32 Backups
I saw this same problem. It seemed to happen pretty frequently on the
first handful of Windows machines of the day (the
We are getting a common error on a number of backups from
Windows clients, the Linux ones work without problems.
We are running 2.0.3 director from the fedora repros
The storage demon is 2.0.2 (not updated)
the fault will happen on Full, Inc. and Diff backups.
It does not happen at the same numbe
