Well, I'm floored. Even though I didn't believe it would be the cause, I finally snagged a crossover cable from the closet-of-goodies and re-imaged my client. Eliminating variables is what we sysadmins just gotta do. Even when it feels stupid.
Worked. (Insert deer in headlights look here) OK, so it seems that in one way or another, rsync is causing the switch to choke. I buy that, since I just saw that with a direct crossover, it works. What I don't get is, why does rsync _NOT_ have any issues when I do stuff like build the golden client image etc, and I only see this behavior after net-booting? It's the same freaking set of files.... "when is rsync not really rsync"? If any of you net gurus out there have an explanation- I'm all ears. Not to mention any ideas on a switch/port setting that might make my HP procurve switch play nice? What a long day. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
