SetiQ Help also please

[SilverBack]

Ok I have tried to set this up with no luck at all.
"Someone throw me a figgin bone will ya, what have you got?"
Here's what I have done, please someone point out what I have done wrong....
I have 4 machines... My pc is going to be the server
Downloaded the SetiQ compatible with the 2.0 versions of Seti.
Unzipped the files to c:\program files\seti@home\setiq
I copied the Wsockhk.dll to c:\program files\seti@home\
I renamed the same file to Wsk2hk.dll and copied it to the same directory
c:\program files\seti@home\
I copied Wsockhk.txt to c:\program files\seti@home\
I edited the above file :
qseti_server=198.162.0.2 //this is my real IP, behind an RT314
saved the file left the rest intact.
I patched the seti@home.exe setipatc "\program files\seti@home\seti@home.exe"
This did work.. As acknowledged in the dos box.
( yes seti was off at the time )
I started SETIQ.exe in c:\program files\seti@home\setiq
and a dos box started with what looked like the correct information

I Restarted seti and when it tries to connect to receive a WU it gets the error (-20,0)

HELP!!!

 

[Robor]

SilverBack: Not sure if I can help or not but I can tell you my setup which is similar to yours.

4 PC's all behind a Linksys cable/DSL router.

All PC's dynamically assigned non-routable IP's (192.168.1.x I think).

Router has single IP dynamically assigned by my ISP.

SetiQ runs on one of the PC's (192.168.1.100).

Other PC's use address 192.168.1.100 and port 5512 to connect to this PC instead of SETI servers.

I didn't rename any files and the only changes I made are to set the queue to 5 days and number of clients to 4. My router allows me to map ports but I'm not sure if it's necessary. I've got port 5512 mapped to my 192.168.1.100 box just in case.

Rob

 

[Hellburner]

I've never done any patching, I would point any remote machines to 192.168.0.2:5512 and the local machine to 127.0.0.1:5512.

If you are running the CLI on a local NT machine you can point that to 192.168.0.2:5512

 

[Poof]

SilverBack - I may be wrong, but I don't think you need to patch Setiq for your situation. I think that patch is only for PCs without a "real" IP address until they obtain one when they connect to their ISP...

 

[SilverBack]

So I just run the SetiQ on my pc and aim the other pc's at me?
also where does the SetiQ store the requested WU's?

 

[blade47]

SilverBack, in a word yes. Run setiQ on your pc and point the other machines to the ip or name of the computer (I always just use the name) and use port 5512.

Then if you use a proxy to connect to the internet you'd have to enter the settings into the qseti.txt file.

I never patch the client running on the setiQ server. I just enter the proxy settings just like I do for the other machines and haven't had any trouble. Every time I mention doing it this way I get trashed saying it won't work. But it has for me on 3 different setups including one a standalone system. Go figure.

SetiQ stores the wu's in the same folder it's in.

 

[SilverBack]

Cool thanks a million guys.
The P3 just requested WU's and it failed, BUT I stopped the Seti on that machine restarted it and it did in fact download WU's for that machine Cool..
So on my machine you suggest just setting the proxy the same as the others? I'll give that a whirl.
THANKS AGAIN!!!

 

[blade47]

Yeah, you can try it. Many people say they can't get it to work that way but it has for me. If that doesn't work then just delete the proxy settings for that client and then try to patch it. No big deal either way.