newsreader wrote:

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?

[...]

What else has changed in any way?

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?

If you are playing on windoze, then the error messages can be completely missleading.

Just one thought. I had some very strange wierdness with the s@h GUI screensaver connecting from windoze to a remote SetiQueue. Being lazy, I had entered the numerical IP address for the lan SetiQueue machine as proxy (192.168.xxx.xxx and in the port box: 5517). The connect failed with Error -26. The web server part of the queue was accessible fine with http://192.168.xxx.xxx:5517...

The fix: You must enter the host _name_ that is then looked up with DNS (or WINS, or from a local hosts or lmhosts file)!


SetiSpy should not in any way affect s@h operation unless you get file access permissions strangeness. This may be a problem if you are working across network mounted directories...


Good luck,
Martin