I’m losing valuable crunching time - whenever SETI starts up (i’m unsing 3.08 CLI, setidriver, and setiqueue) i get the following msg as it tries to transmit:
Using proxy server 192.168.123.160:5517
Sending result - connecting to server.
recv fd=68 n=0, errno=2
Can’t connect to server, will retry in an hour
W00T the f00 is g00ing on?
if i try and send the w00 straight back to b0rkley by setting setidrivers proxy to off, i just get
Sending result - connecting to server.
and no other messages.
I have tried re-downloading the seti client, to no avail.
I can’t help with your connection problems but I can say you shouldn’t be using 3.08. 3.08 is a security improved version which runs slower than the 3.03. The security concern is minimal. There are a number of places where it is available, I’m sure someone here will post a link. I know TeamStarfire posts a link on their sticky.
Originally posted by Kwazy_Wabbit
[B]is setiqueue running on the same machine??
if not can you ping the queue machine and can the queue machine ping the client?
have you filled out the server settings pages in setiqueue? I leave all the top part blank except for the port.
can you connect to the web admin page of the queue? [/B]
They are both running on the same machine. They have both been running flawlessly since about february. The web admin all works fine. Pinging the server PC from the other on my network works fine. The server settings are configured to use port 5517, any IP on submask 255.255.255.0.
Have you tired creating a new directory and popping a ‘clean’ version of the client and setidriver in there (the one form m@tts link) and seeing if that will download a unit??
Originally posted by Kwazy_Wabbit
[B]ok silly question time…
Have you installed any firewall software?
Have you tired setting the subnet mask to 0.0.0.0
Have you tired creating a new directory and popping a ‘clean’ version of the client and setidriver in there (the one form m@tts link) and seeing if that will download a unit?? [/B]
Just tried your “option 3”, and it works again! yay! must have had a crash or something that upset the installation of setidriver and/or one of the clients data files.
Thanx for the excellent rapid response guys, TPR rox
Originally posted by sp00n
[B]Just tried your “option 3”, and it works again! yay! must have had a crash or something that upset the installation of setidriver and/or one of the clients data files.
Thanx for the excellent rapid response guys, TPR rox [/B]
I’ve had that happen to me before
if you’ve still got the ‘old’ directory you could try deleting the user.sah and the version.sah and see if it will return your completed unit… I’ve no idea if that will work or if the problem is within the unit/ result.sah but it’s got to be worth a try, as not to waste a completed unit