other folks have posted about this issue - I don't recall what the fix was. Seemed to be some sort of network collision (but maybe that was something else..)