It's not necessarily network hw or sw that's at fault. I once had a similar problem caused by the (3rd party) driver of the onboard "RAID" controller. Newer driver version fixed it.
Fri Jul 27 15:19:42 UTC 2012
Lars Hecking <lhecking at users.sourceforge.net>
It's not necessarily network hw or sw that's at fault. I once had a similar problem caused by the (3rd party) driver of the onboard "RAID" controller. Newer driver version fixed it.