I got it. This maybe something with my hardware/software setup.
I turned off the firewall that came with Windows XP Home SP2.
I then followed your original instructions. IT WORKED! [jumps for
joy!]
I am turning on my firewall and crossing my fingers that it still
works. If it don't, I will be able to handle it from here.

Thanks again! [dances in the streets!]

:)

blackwolfstanding@hotmail.com (Black Wolf Standing) wrote in message news:<ff5e274.0410221847.6a3f0df5@posting.google.com>...

Thanks for your help.
But this didn't solve my problem. I followed your sets twice just to
make sure. As a hunch, I set ask s@h to ask before connecting. When I
told it to connect, it replied, "Can't establish a network socket."
(Or something very close to that.) I re-read the setup directions to
make sure my setup was correct. It is correct as far as I can tell.
Could this problem be related to the firewall that is built into
Windows XP Home SP2? I'm disabling the firewall for now to see.
Any other help would be appreciated.

"Lambchop" <holy_saiyan1@_(REMOVETHIS)_hotmail.com> wrote in message news:<2trb8vF22t34uU1@uni-berlin.de>...

I had this problem for months... it's rather simple to correct, really.

When you are letting SETI@Home work while you are away, go to Control Panel,
Internet Settings, click the "Connections" tab, and set it to "Never dial a
connection."  Before you let the screensaver do its thing, open SetiGate and
make sure that SETI@Home is set to "Automatically connect."  After you get
home, and it's already cached the result, just close SetiGate, and go back
into Internet Settings and reset the Connections panel to "Always dial a
connection."  It's not pretty but it works.

Does this help any?