It turns out my cubes did not like being pointed at the same proxy.  This morning I did some more testing and put them both back on single proxies (like I had been running) and that appears to have solved the hashing problems I was having.  Doesn't make much sense to me given how fast a machine the single proxy was running on (dual quad core desktop).  Putting a second proxy on an old slow dual core laptop seems to do the trick.  I'm guessing my internal network or traffic could have something to do with it.

One of the boards still is not hashing at full capacity so I'm going to start up a proxy on a 3rd machine and try point that cube at the new proxy.

I did try the -nm option when I was running only 1 proxy and that didn't help (the work difficulty dropped to a 1 from around 22).

=====

Just started up a new proxy on a 3rd computer and pointed my slower cube at it and that seems to have resolved the problem.  I'm not sure what is going on since prior to last night I was running both cubes through the same switch to two different proxies on two different machines.  I put pointed both cubes at my desktop so I could take my laptop with me for the holidays.  Now both proxies are on different computers routed through different switches to my cable modem and both are hashing as expected.  I've got no more time for investigating right now.

thegoldbug