Smokeball - I think in your case, you're running up against the 1500 simultaneous connections limit on the SETI data server. I wouldn't be surprised that if your queue gets a connection and takes say 5 minutes to download 5 WUs, that's considered an "idle" 5 minutes (non-interactive) by the connection monitoring protocols and suddenly, the connection is reset. At that point, your queue is thrown back out there among the masses and must compete again to try to re-establish a connection to get more WUs. I think of it like how some FTP software works when you're downloading a big file. Some client proggies are dumb and after x number of minutes, they don't send some sort of ACK back to the server and then your FTP connection is closed (while you're in the middle of the download! :Q). It seems like this is what is happening. I don't think there's any setting in the queue that would fix that. Either the queue program would need to be rewritten to try to maintain the connection (which I doubt would happen cause we have to share that data pipe and share the connections) or SETI needs to increase the number of simultaneous connections permitted and/or get more data servers.