Did you try with "-proxy 127.0.0.1:5001" ?

Check on SetiGate's options that the "local port" is still set to 5001, or choose the same on both ends...

I have been using SetiGate on winXP for monthes now, without any problem. I have changed the port to 5517 (more SetiQueue like isn't it ?) but cmd line version runs with '127.0.0.1:5517' as a proxy.

Did you download last version of SetiGate (1.95) because a connection problem with XP has been solved between 1.93 and 1.95, if I remember correctly.

Obi Wan
Who will reach 20000 next week !

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