| Subject: SetiGate Won't work |
| From: macmcd@cix.co.uk (Mac McDonald) |
| Date: 22/02/2005, 18:31 |
Hi,
I'm sure this has been covered innumerate times here but I am new to
Usenet and have only been able to view the last 50 or so headers, so I
apologise in advance for repetition.
I have spent quite a few frustrating hours trying to get SetiGate 1.95 to
pass work units to the gui version of Seti@Home (version 3.08) with
marginal success (one transfer to be exact). 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"?
I seem to remember that these were the settings used when I managed to
transfer my single unit, I hadn't told Seti@Home to connect automatically
and it necessitated me connecting to the internet for it to collect a WU
from SetiGate. I subsequently changed my internet settings to "Never dial
a connection" but have had no look since (even changing it back to "Always
dial my default connection).
I can think of two possible problems: firstly, SetiGate is generally a bit
behind on the "% done" but changing this to a value lower than 100% seems
to have no effect. Secondly, I am using Norton Internet Security 2002 and
presume this could have something to do with it, but to be honest, I don't
want to blithely start changing the settings without understanding what
I'm doing.
Using Windows XP Pro SP2 with Firewall disabled
Can anyone help?
Regards,
Mac.