John/Miguel, Thanks for your responses. EqualCostMultiPath seems to be exactly what's causing this behavior.
In theory, it seems EqualCostMultiPath would be ideal behavior to load-balance network traffic between the adapters, which seems like a "good thing". However, I hadn't considered the consequences of out-of-sequence traffic. I'll past the COST0 option to our network folks to see if they want me to implement it. Thanks, Dennis
