with proxy settings set and Seti Gui Client locked in behind a firewall,
Issue resolved.  SetiGate is now successfully passing Cached WU to the
Client.

  Fingers crossed that all runs well.

Thank you.

D.


"Olivier" <obietzer_at_chez_dot_com@pas_de_spam_svp.com> wrote in message
news:40309491$0$28123$636a15ce@news.free.fr...

Have you added the proxy settings to your GUI ?

ObiWan



D. a �crit :

Just added SetiGate to my computer and I guess I missed something in the

set

up.

 I'm running the SETI 3.08 Gui client and holding three days worth of

Work

Units in the SetiGate Cache.

  If I am disconnected from the net my Seti Client completes a WU and
SetiGate fails to transfer a new work unit to the Client.  If I am

online

when the WU completes then my seti Client bypasses SetiGate and sends

the

completed unit to Berkley and automatically retrieves a new WU

completely

ignoring the Cached WU's.

Despite the two programs seemingly being unable to see each other

SetGate

has no problem acessing Berkley to get Stats or WU's.

I've even moved all the SETI@Home and SetiGate files into the same

folder to

no avail.

  Can anyone out there tell me what I might have missed here?

Any and all help appreciated.

D.