>So Retrospect reports errors that it finds in the network setup that
>doesn't affect ANYTHING else? If these errors existed then why does
>nothing else complain?
Yet.
>I copy large files from one machine to another, but that never fails
Yet.
> If it is a SCSI problem, then shouldn't
>Ret
> So Retrospect reports errors that it finds in the network setup that
> doesn't affect ANYTHING else? If these errors existed then why does
> nothing else complain? I'm sure that it does hit the network hard,
> but IMO it should be written to cope with that. It should not the
> task of the custom
on 11/23/00 2:09 PM, Ken Gillett at [EMAIL PROTECTED] wrote:
> So Retrospect reports errors that it finds in the network setup that
> doesn't affect ANYTHING else? If these errors existed then why does
> nothing else complain? I'm sure that it does hit the network hard,
> but IMO it should be wri
Adrian.
The termination problem was on the client, which is an ASIP server. It just
took out that particular client. However, if there is a termination problem
on the Retrospect 'server' then I guess you could see 519 errors.
It sounds like you need to talk with the folks at Retrospect in perso
Oh, BTW - Asante's first 10/100 PCI cards (rev A) sucked big time.
They worked fine in a PC, but in the Mac they were flakey, specially
when connected to non-asante switches. In particular, Cisco switches.
--
--
To subscribe:[EMAIL
I usually disable the Apple Enet when using third party cards anyway.
The other two should have no effect on the NIC operation.
I'm wondering if the NIC was also flakey. One problem I've found
with Asante and Farallon is the 1 in 20 failure rates. Both have
lifetime warranties, so it's not t
