In article <MPG.1a082853efbee2bd9896fe@news.supernews.com>, cj-usenet-01
_SPAM@comcast.net says...

I'm unable to connect to the Seti@home web server or to cricket.berkeley.edu 
this morning, from near Chicago. Connections to the data server are OK.

A traceroute to the web server stop in Los Angeles

Probabily a result of the fires there.

I was just able to connect to the above systems.  :-)

I guess that he backbone people flushed the routing tables.

     ** Info posted on the Seti@home server this morning **

? October 27, 2003 ? 
If you are unable to connect due to "100" errors (or perhaps "41") you may need 
to exit SETI@home, remove the files "result.sah" and "user_info.sah" from your 
system, and then restart SETI@home. This is probably fallout from the user 
database crash a few days ago. Sorry for the inconvenience. 


-- 
Claude