Hello knreed
Reference: knreed [Jul 25, 2012 10:02:44 PM] post

So what do we crunchers do for the meantime: limit our sync-to-WCG to once every 24hrs? That would seem to be a direct solution to regulate the traffic and thereby help ease congestion. Or, do we crunchers have to play it by ear?
;

@knreed
Thank you for the problem update.
I don't know if it could help, but many years ago, I experienced a strong network problem with a network adapter (NIC) malfunction which caused an overflow of the address cache by the network switch.

We discovered (after many hours/days of investigation) that, under particular condition, the NIC changed spontaneously its MAC-address.
Finally we replaced the NIC, assuming that there was a hardware failure.

The effect of this MAC-address corruption was an cache overflow by the switch which caused loss of packet and connexion.

Yves
---
Edited: PS: the problem was critical because it was a server NIC (not by a workstation).

Somehow, that option didn't present itself to me. Nor was I looking for it. Anyways, I'll take your 'wait' suggestion to mean doing a sync by ear.
;

I just finished completing all my uploads and reporting all the ready to report WUs. For the uploads, I had to go to Transfers, highlight the first item in the list, and do a Retry Now.

Sigh, the most productive host I have, has so many waiting to report that it gets a timeout trying to report them, and it's been this way since last night. It can upload, sometimes, but since it can't report it won't download. Other hosts are doing what everyone else's are doing -- communicating well at times, not at others, but this one will run dry before too long.

It sounds like a nasty problem to troubleshoot, I don't envy the techs but good luck to them.