Martin wrote:

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

Hi Martin thanx for bearing with me.

I know it is something wrong with this machine which is a home built athlon
2800+ ( build them for a living ) call it (A)

The other (B) is a thrown together bitza box functioning as firewall and
router feeding this machine and one in the office which is not on all the
time ( but does not do seti ), they are all linked through a 10/100 5 port
switch, the network has been functioning fine for months.

Both A and B are on 24/7 and have been like that for approx 1 month, down time
was due to a long power outage which my ups could not handle.

I am using Suse 8.1 on both machines that run seti nothing has been installed
or deleted for at least 1 week, I know this for sure as I am the only person
on them ( no-body else can access them, or would now what to do )

The networking is fine, otherwise I would not be able to post this message :)
on machine A the Ksetspy will connect to Seti@home and try to send but it
just sits there waiting for upload but while it is waiting for the upload it
will d/load new units for the cache so the communication is fine it just will
not send.

If I d/load a new client unpack into own ( new ) dir and launch from cli it
will connect ask for e-mail and get a unit, so it communicates fine but when
the unit is finished it just waits at :-

<<----snip--->>

Platform: i686-pc-linux-gnu
Version: 3.08

SETI@home is sponsored by individual donors around the world.
If you'd like to contribute to the project,
please visit the SETI@home web site at
http://setiathome.ssl.berkeley.edu.
The project is also sponsored by the Planetary Society,
the University of California, Sun Microsystems, Paramount Pictures,
Fujifilm Computer Products, Informix, Engineering Design Team Inc,
The Santa Cruz Operation (SCO), Intel, Quantum Corporation,
and the SETI Institute.

SETI@home was developed by David Gedye (Founder),
David Anderson (Director), Dan Werthimer (Chief Scientist),
Leonard Chung, Hiram Clawson, Jeff Cobb, Charles Congdon, Charlie Fenton,
Kyle Granger, Eric Heien, Mike Hill, Michael Kang, Eric Korpela,
Matt Lebofsky, Peter Leiser, Brad Silen, Woody Sullivan, and Adam Wight.

Sending result - connecting to server.

<<<end snip>>>>

And that is it, no errors and will sit there for hours.

Putting a sniffer on the firewall when I try and connect using cli, ksetispy
or ksetiwatch from machine A I can see the packets going through machine B
to:-

shserver2.SSL.Berkely.EDU.www-http

and see the ACK coming back.

but that is it, I see no errors or routing probs in the firwall log all looks
normal.

All machines on the network communicate fine internal and external, this only
started after the seti@home prob with the data base, which might just be a
coincinence, I am willing to admit it could be this machine but am just
confused what it is ( have been running seti for 5 years minus 1 month on
linux so do have a resonable knowledge of the o/s :)

I will try some other things today, like make a new user account and see if
seti will run from there just in case it is my main account that has
something wrong with the permissions, or heaven forbid I might d/load a new
client and run it from root :).

I have got win2k on a seperate hard drive here so I could even boot into that
and install seti and see if that sends units, but will not have the time till
Sunday to mess with winblows :)

Please do not waste too many brain cycles on this prob, I can still zip the
cache and move to machine B and send from there as I have done this morning
so I am no longer losing the results, just a bit of a pain in the butt.

This machine will be formatted next week to put the new Suse 9 on so hope to
sort it before then just for the satisfaction of finding out what has caused
the problem.


Thanx for you time....


-- 
Mark
Twixt hill and high water.
N.Wales, UK.
Email is spam trap try baskitcaise at gmx dot co dot uk