Setispy/driver can't connect error

[killem1x1]

I have seti configured so it will cache 10 before it upload/dload because I was on the road last week (dial-up), when I returned home, I didn't change anything. I noticed this morning that seti "can't connect", and will "retry in 1 hour", I tried restarting, etc.... If anyone else has had this problem please advise. Also I don't want to lose the results that I haven't sent in. If I need to "reload" setispy and driver, what files do I need to save so I don't lose the "untransmitted" results?
Thanks!

[[Oc]acaridans]

Ive been experienceing problems...just read the WU trouble thread...

[Basher]

Originally posted by killem1x1
I have seti configured so it will cache 10 before it upload/dload because I was on the road last week (dial-up), when I returned home, I didn't change anything. I noticed this morning that seti "can't connect", and will "retry in 1 hour", I tried restarting, etc.... If anyone else has had this problem please advise. Also I don't want to lose the results that I haven't sent in. If I need to "reload" setispy and driver, what files do I need to save so I don't lose the "untransmitted" results?
Thanks!

Problem is on seti's end not yours we all are having problems transmitting WU's :(

[!-=sky=-!]

true........"sometimes" the server works but not all

[chawken]

Berkeley was down for a portion of this weekend. As is the case, most of the time, when the are back on line - there are thousands upon thousands of work units to be uploaded/downloaded. Just keep a good amount of WU's in cache - as it can take a few days for Berkeley to get caught up. I noticed, even today, that there were times that my machines could not transmit.