Subject: Re: SetiDriver unable to connect
From: gheston@hiwaay.net (Gary Heston)
Date: 07/07/2003, 04:11
Newsgroups: alt.sci.seti

In article <3F08D45C.5050905@home.net>, Darren  <iam@home.net> wrote:
I have been using SetiDriver for about two weeks but over the weekend 
the my wu cache was completed and not returned. Now when I try to force 
a return using SetiDriver it states that it is unable to connect.

Is the seti server accepting returns or am I the one with a problem (I 
haven't made any changes to cause one though.)

My SETI Queue has been busily returning results all evening, so it's 
either a problem between you and the server, or there was an unexpected
side effect from a change you made that you didn't think would affect
this.

Can you ping or traceroute to shserver2.ssl.berkeley.edu (66.28.250.122)?


Gary

-- Gary Heston gheston@hiwaay.net PHB: "That's the sort of leadership that will turn this company around." Wally: "Were we doing well?" Dilbert, 5/23/3