Question about SetiQueue

[Fardringle]

I have SetiQueue up and running properly on my main computer at home, but for some reason, the two client computers say that they can't see the proxy. All machines are running Win95c and they are all set to use the proper address for the proxy computer (I even have a proxy program on the main system, which is how the other two have received WU's before) and I would like to set it up so that my modem doesn't call out a half dozen times every day. Is there a special command or setting I need to use to get the client (WinNT command line) to receive WU's from a SetiQueue proxy on a different computer.

I know that many of you are using a similar setup, so I'm pretty sure I'm just missing something...

Thanks for the help!

 

[Fardringle]

UPDATE:

Apparently, the GUI client does work on the client computers with my current SetiQ configuration, but I'd really like to get it working with the CL client if possible..

Thanks again.

 

[Assimilator1]

Is it just SETI CLi that can't see the proxxy or is the computeres can't see each other at all?

 

[ColinP]

You running it like this ???

setiathome -proxy IPaddress:5512

think thats how you do it, not used NT cmdline in ages...

cheers,

Col.

 

[Polo]

Do you launch your SETI CLI with a command line like this one :

E:\SETI@home\setiathome-3.0.i386-winnt-cmdline.exe -proxy 192.192.192.1:5512

where 192.192.192.1 is the IP adresse your the SETIQ computer ?

You need the -proxy parameter to enable the CLI to reach the proxy. If not, the CLI will try to contact SETI@Home through the default connection (Lan or modem) and could fail...

Keep us informed. 🙂

 

[Sukhoi]

Yes, what Polo said should work fine.

 

[Fardringle]

That's exactly what I needed, thanks! 🙂