I use SetiQueue, but instead of the words "localhost" I have to put in
the actual name or IP address of the machine with the Queue.
In my case I use Seti2 and port 5517. As long as the machines all say
the same port and you are not blocking any ports 5001 should work for
you.
Just an idea.

On Thu, 29 Jan 2004 18:56:35 -0000, "Cambridge Computer Recycling"
<sales@cambridge-computer-recycling.co.uk> wrote:

"el_tel" <terry@tel928.fsnet.co.uk> wrote in message
news:bv9o99$a1p$1@news8.svr.pol.co.uk...

I am wanting to use setigate on a single pc with a dial up connection.

I have set up as far as I can, using the readme file. I have cached WU's

and

am ready for processing. Problem is I cannot get the WU into seti.

"Appendix A" of setup instructions states that seti's socks proxy address
should be set to 'localhost' and the port set to the same as setigates

local

port, '5001'.

No matter what I do I get a error message "cannot connect to internet;

error

??????? cannot find socks server".

I know this is going to be one of those "Doh" moments but can anyone help
me?


I have the same problem.  Setigate download the cache quite happily.  I am

running the command line and have it pointed at -proxy localhost:5001 but it
tells me it cannot find the server.

Chris