Martin <ml_news@nnooospam_ml1_nospam.co.uk> wrote in message news:<3F11F430.2070204@nnooospam_ml1_nospam.co.uk>...

Tony C wrote:

I've got Seti@home running on Red Hat 7.1, in the background.
When it completes a data packet, the Seti client is never able to
connect to the server to upload the results, unless I kill and restart
that process, or reboot the machine.

This has been happening for over a year- so I'm pretty sure it's not
that the server is too busy. I also run setiathome on many windows
machines where I work, and they have no problem connecting to the
server, and uploading the results.

Can anyone give me a clue as to what the problem is ?

Wild guess of a firewall or proxy in the way?
Can you ping the s@h server?

Sorry, a few more clues required...

Would you tell me What kind of clues do you want ?
My post states that if I kill the seti process or reboot the machine,
then the client connects and gets a new packet, so the firewall
doesn't seem to be a problem then.