On Tue, 16 Sep 2003 17:13:39 GMT, "newsreader"
<newsreader@wyvernhall.com> 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?

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.

I would change the proxy server numbers to the name of the computer.
I have my SetiQueue on a machine I call Seti2, so my settings are
seti2:5517.
That will get around the IP address changing on system/router reboots.
The only other thing would be to ask yourself how do I connect to the
machine that has the Queue on it. Do I have to jump thru hoops or do I
use a password or do I just type in the address and I am there?
Also ask if the 2 machines cann access the other machines on the lan
or are they not there either? If they are visible then the problem isy
our setup, if they are not visible then your problem is not Seti but a
network issue.
I had problems with 2 of my machines that were upgraded to SP4 but
giving my access points their own permanent IP address fixed that
problem. I could see across the wired and even wireless parts of my
lan but not thru the access points with SP4. All other machines could
go thru the APs just fine.
I saw in another message that you do NOT use the auto upgrade features
of Windows. I do and have all along and haven't had any problems until
SP4, and now even they are fixed. I have 14 machines all running Seti,
most full time, and networking has been an experience. I have machines
running mostly win2000 pro, I have 1 running Win98se, 1 running
Win2000 server and 1 running Linux diskless. I use version 3.3.3 of
SetiSpy. I use SetiDriver to start the CLI on each machine, except the
Linux one and have SetiQueue running on one machine.

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.)

-- Have you checked your Smoke Detector...LATELY?