Error accessing http://setiathome.ssl.berkeley.edu/ [128.32.18.151]
Robi
Am I the only one having trouble accessing the SETI @ Home website
http://setiathome.ssl.berkeley.edu/ [128.32.18.151]?
--- reading URL http://setiathome.ssl.berkeley.edu/
--- contacting host setiathome.ssl.berkeley.edu [128.32.18.151] on port 80
--- error: timed out
$ ping setiathome.ssl.berkeley.edu
Pinging setiathome.ssl.berkeley.edu [128.32.18.151] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 128.32.18.151:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
--- traceroute to setiathome.ssl.berkeley.edu [128.32.18.151],
30 hops max, 18 byte packets
[...]
7 [ 12.123.9.85] ggr2-p390.wswdc.ip.att.net 109 ms
8 [209.244.219.141] so-2-0-0.edge1.Washington1.Level3.net 41 ms
9 [ 209.244.11.13] so-5-0-0.gar2.Washington1.Level3.net 41 ms
10 [ 64.159.1.157] so-0-0-0.bbr1.LosAngeles1.level3.net 109 ms
11 [ 209.247.9.142] unknown.Level3.net 96 ms
12 [ 209.244.10.254] gigabitethernet4-2.ipcolo1.LosAngeles1.Level3.net 83 ms
13 [ 64.156.191.10] unknown.Level3.net 83 ms
14 [ 137.164.24.142] inet-ucb--lax-isp.cenic.net 96 ms
15 [ 128.32.0.251] vlan194.inr-202-doecev.Berkeley.EDU 82 ms
16. *
[...]
30. *
--- host unreachable
--- traceroute statistics for setiathome.ssl.berkeley.edu
30 packets transmitted, 15 received
round-trip time (ms) min 41, avg 92, max 178
--
Robi
(2.9#@ 2.77 yrs)
David H. Lipman
I acn't access it either. It appears to be down :-(
Dave
"Robi" <m...@privacy.net> wrote in message
news:bp6qa1$1la51e$1...@ID-211961.news.uni-berlin.de...
Robi
> Robi:
>
> I acn't access it either. It appears to be down :-(
>
> Dave
[...]
phew, I was scared that I was the only one.
BTW, there was this message about some virus/worm installing S@h
anybody got a copy of the message?
It seems to be recent.
--
robi
David H. Lipman
downloaded the client from SETI and not a third party.
Dave
"Robi" <m...@privacy.net> wrote in message
news:bp6t26$1k5j7f$1...@ID-211961.news.uni-berlin.de...
Phil Earnhardt
>>> Am I the only one having trouble accessing the SETI @ Home website
>>> http://setiathome.ssl.berkeley.edu/ [128.32.18.151]?
>>
>> I acn't access it either. It appears to be down :-(
>>
>> Dave
>
>phew, I was scared that I was the only one.
You never really need to have that worry. To coin a phrase: you are
not alone. ;-)
All you need to do to get another data point is to access a proxy
browsing service. The anonymizer.com is as good a service as any to
use. Just put in the URL
http://anon.free.anonymizer.com/http://setiathome.ssl.berkeley.edu
and that will attempt to connect to the setiathome site through
anonymizer.com's services. The Anonymizer will then blast the page
back to you -- presuming the website is up.
>BTW, there was this message about some virus/worm installing S@h
>anybody got a copy of the message?
If you go to symantec.com's website and key in set, you'll see a
report about something doing that:
>> W32.Hyd@mm
>> Category2
>> Discovered on: June 07, 2001
>> Last Updated on: April 15, 2002 05:07:24 PM
>>
>> W32.Hyd@mm is a retro mass-mailing worm that spreads
>> using Microsoft Outlook. When run, it downloads and
>> installs the SETI @ Home program and sets it up to
>> perform calculations on the account of the virus writer.
>>
>> Also Known As: SETI@Home worm
>> Type: Worm
>> Infection Length: 12249
>It seems to be recent.
If you go to www.deja.com and do a search on
seti@home worm
and sort the results by date, you'll see some recent entries at the
top of the list. They mention
http://setiathome.ssl.berkeley.edu/virus.html
Which, apparently, is a writeup about the current worm. But the
website is down right now.
--phil
Bill Barto
the lines going into them. The first one is for the data server and the
second is the line to the home page. Looks like berkeley fell into the
pacific.
http://cricket.berkeley.edu:8885/inr-668-interfaces.html
http://cricket.berkeley.edu:8885/inr-60-interfaces.html
"Robi" <m...@privacy.net> wrote in message
news:bp6qa1$1la51e$1...@ID-211961.news.uni-berlin.de...
ComputerDoctor
> Looks like berkeley fell into the pacific.
BTW is the SETI project able to withstand earthquakes at the server end?
It would be a shame to lose all that processed data, not to mention the
people.
David H. Lipman
McAfee calls the original infector: W32/Hadra@M
And it started 6/01.
Oh and the site is back up !
Dave
"Phil Earnhardt" <p...@dim.com> wrote in message
news:bludrvo7hhnabvajk...@4ax.com...
Michael Sinatra
On Sun, 16 Nov 2003, David H. Lipman wrote:
> Thanx Phil this is news ! Updated on 11/14.
>
> McAfee calls the original infector: W32/Hadra@M
>
> And it started 6/01.
>
> Oh and the site is back up !
Wow you're quick. I just got it back--a media converter power supply went
bad. I had to improvise to get it working again (fortunately these
"proprietary" media converters are actually standards-based and I was able
to swap in another one). I can shut it back down again if you want...
Gotta run, time for beer.
michael
Michael Sinatra
On Sun, 16 Nov 2003, Bill Barto wrote:
> It appears berkeley is off the air. These two links show the data rates on
> the lines going into them. The first one is for the data server and the
> second is the line to the home page. Looks like berkeley fell into the
> pacific.
>
> http://cricket.berkeley.edu:8885/inr-668-interfaces.html
>
> http://cricket.berkeley.edu:8885/inr-60-interfaces.html
Now, if Berkeley fell into the pacific, how would you be able to access
http://cricket.BERKELEY.EDU???
Sheesh, no wonder the aliens keep breaking those media converters.
michael
Robi
Thanks alot for the quick fix Michael.
Michael, the better-quicker-fixer-upper ;o)