baskitcaise wrote:

Martin wrote:

Use ping and trace to check that you have the expected network connectivity.

Note that logrotate can sometimes cause problems when it shuts down some
system stuff while the logs are being rotated. Try restarting the
network services and then restart your firewall.

Also double check your file permissions.

Otherwise, try posting a few more details for more guesses.
(Not got infinite patience to do an infinity of brute force guessing (;-))

And there may be something subtly wrong with the .sah files. Note that
certain files and contents exist only at certain phases of operation...


Let us know what you find.

Good luck,
Martin

(And all's well with s@h winnt cli + SetiSpy + SetiQueue in wine on
Mandrake 9.1 Linux)

Hi Martin here is a cut and paste from another thread where I have tried to
explain what I have done so far, please bear with the long post some exciting
news just in at the bottom :(

[...]

It goes beyond my logic

<<<<<<<<<<<<<<<<<Note This>>>>>>>>>>>>>>>>>

Hang on it has just finished a unit will see what happens now...........

Well same thing happens it will not send the upload, log just hangs at
"Sending result - connecting to server" has been like that for 10 mins with
no net activity and no timeout and no errors, tried with cli and Ksetispy
Seti@home sends a new unit to the cache so I must be sending something out for
them to reply

zip file, move to another machine on same lan unzip to cache dir of kseitspy
pressa da button bada bing bada boom all gone worky nice mister, and this is
using the .sah`s from this bad machine.


Anyone the wiser?

So what OSes are you using and how?

Can you ping and trace through to the s@h servers?

Have you tried directly connecting to the s@h servers rather than using a proxy?

Do you know whether NAT is working ok on your gateway/firewall for your troubled machines?

Have you got DNS working correctly? And good IP addresses for your machines??


Next batch of guesses when you give some useful details of what your troubled machine _is_ and how it is connected.

Note that s@h works fine for millions of others so it is unlikely to be a problem with the client software.


Good luck,
Martin