I infer that you are running setigate and seti on the same
computer (not using a home network). We are assuming that
you have already configured Setigate to access the Seti
site, and Setigate contains one or more queued workunits. 

Here are my settings:
Seti: Check the "http proxy" box, then, where it says:
"http://"
put "localhost" (no quotes)
where it says "Port Number:" 
put "5001" (no quotes)
Uncheck the "Socks" box. I think this is what is screwing
you up, because (I assume) you don't have a "socks" proxy
(and I'm not sure what a "socks proxy" is, except I know I
don't have one either). 

In NIS, there is an entry pointing to the setigate program
with a setting of "allow all". I believe this was put there
by NIS when the box came up and I clicked "allow" with
"always use this action" checked.

In setigate, under "edit user" , under "clients", you will
probably want to add the USER NAME under which you are
logged on, and check "active client". 

Remote computers require some additional tricky steps.

macmcd@cix.co.uk (Mac McDonald) wrote:

I have used the default 
options in SetiGate (Seti Port = 80, Seti http Port = 80, Local Port = 
5001) and have tried various options in the Seti@Home proxy server 
settings. What are the correct settings? Do you set the Proxy host to 
"localhost" and Port number "80" as well as setting SOCKS Proxy to 
"localhost" and Port number "5001"?