| Subject: Re: Problems with SetiGate |
| From: "Seti Cruncher" <SetiCruncher@"NOSPAM"WildMail.com> |
| Date: 11/04/2004, 03:19 |
Andres,
The Gui Client will work fine with SetiGate, just make sure your Seti Client
is set to connect to Proxy Server 'localhost' on port Number 5001, and that
SetiGate itself is set under 'options' to connect on local port 5001. and
all should work well for you.
(port 5001 is the default port, you can set this to any port you wish)
Hope this helps.
SC
"Andres Dagotto" <dagotto@ar.ibm.com> wrote in message
news:acc17ea0.0404101700.78b925ab@posting.google.com...
I had installed setigate, and there seams to be some conflict with the
graphical seticlient i am using.
Setigate receives WU with no problems, and it even triggers the
seticlient, however, when the seticlient finished the WU, it connects
itself to the server to get a single new WU. So the cached WU in
setigate are never processed.
In the same way, when I am offline, even having several WU cached, the
seticlient stay in "can't connect" mode and does not process anything
from the cache ....
I heard I have to use the "command line seticlient" . Is that correct
? If so, what is that ? I still want to see the fancy graphs and the
screensaver ...
Regards
Andres