I've noticed that two of my machines have been unable to contact SETI Queue
to transfer work ever since I installed the latest version of SETI Spy.  Is
anyone else seeing this?

One machine is the ICS host/SETI Queue server, the other is on the ICS LAN.
Other machines both from on the same LAN and off have been successfully
transfering WUs plus I can access the SETI Queue remote screens from any
machine -- even the ones that won't connect to transfer data.  As nearly as
I can tell so far, only the two machines I installed the latest SETI Spy are
unable to connect.

The problem appears when SETI@home tries to connect to SETI Queue.  The
usual transfer dialogue gets only this far:

Using Proxy server 24.151.90.20:5517
Sending result - connecting to server.
connect: No such file or directory
Can't connect to server; will retry in an hour.

Thoughts anyone?

(As soon as I can dig up a copy of an older version of SETI Spy I'll swap it
in to see if I can confirm whether or not it has anything to do with the
problem.)