Ben,
First off, you really should upgrade to the newest version of SetiQueue, as it is much more stable, and has some really neat features.
Second, once a client tries to connect to your SetiQueue, the program will create a new directory for that client. Then, since your Q can't get the Work Units itself, just move a few from a 'stocked' client directory into the one needing work, and then have that client try and connect again and you should be good to go... (Every new client that connects right now may have problems with its identity since it can't get the info from Berkeley, but will still be cracking with your user ID and the info will be updated the next time they connect after the Berkeley servers are back up.) Just make sure you disable 'Override time for passthrough operations' or your Queue will just keep trying to connect to Berkeley to get your user info for the new clients..