I've seen what you describe when I was trying to login(with a new machine) and connect to a SetiQueue instead of directly to Berkeley. 😉
In those instances, I simply connected to Berkeley, got the unit, let it crunch a moment or two, then stopped the client, and restarted with the "-proxy" settings for whatever queue it was going to crunch to.