I'm running SETI@home/BOINC on five computers. Four of these computers are running fine. One gives me an error message, "Can't resolve host name setiathome.berkeley.edu" when I attempt to attach to the host. I have tried to shut down BOINC and restart it with the same result. I have tried to uninstall BOINC (erasing the entire directory after uninstalling) and then reinstalling it. I still get the same result. The computer is running Windows ME and has plenty of memory and speed.
Hughes Glantzberg
The PC Help Desk

Can you ping that address? If not, then that machine for some reason really can't see that web address. From a command line type "ping setiathome.berkeley.edu".

Are you absoloutely certain that you have typed the address in perfectly? I know that I have made typing mistakes when typing, and I get the same problem.
jm7

> Can you ping that address? If not, then that machine for some reason really
> can't see that web address. From a command line type "ping
> setiathome.berkeley.edu".
>
> Are you absoloutely certain that you have typed the address in perfectly? I
> know that I have made typing mistakes when typing, and I get the same problem.
>
> jm7
>
I'm fairly certain that I typed the address correctly. I've done it about fifteen times and have always gotten the same results. If I were typing it wrong, I would assume at least once I would get it right. I have also typed the address into my browser and have gotten to the website without any problem. I'll give the ping a try and see what happens.

Thanks.
Hughes Glantzberg
The PC Help Desk

Ping of http://setiathome.berkeley.edu or just setiathome.berkeley.edu give a negative result. Hmmmm.... Ideas?
Hughes Glantzberg
The PC Help Desk

> Can you ping that address? If not, then that machine for some reason really
> can't see that web address. From a command line type "ping
> setiathome.berkeley.edu".
>
> Are you absoloutely certain that you have typed the address in perfectly? I
> know that I have made typing mistakes when typing, and I get the same problem.
>
> jm7
>

I am having the exact same problem. Does not work with:

http://setiathome.berkeley.edu
or
http://setiboinc.ssl.berkeley.edu/sah

Cannot ping either site, though the browser has no problem resolving the IP.

Is there a firewall or proxy in the way that could be doing this? Usually when I can't ping, nothing about the site works. If there is no firewall or proxy that you know about, is it possible that your ISP is blocking access? At this point, I am clearly grasping at straws.
jm7

> Is there a firewall or proxy in the way that could be doing this? Usually
> when I can't ping, nothing about the site works. If there is no firewall or
> proxy that you know about, is it possible that your ISP is blocking access?
> At this point, I am clearly grasping at straws.
> jm7
>

Found the culprit. After running "netsh diag gui" (XP only, does not work on ME, Hughes) saw that no pings were going through. Decided to uninstall Zone Alarm, even though I had it disabled. That did the trick... no problems now that I can see.

Hughes, make sure there is no instance of a firewall on your system, that may work...

Cheers!

I used to have Zone Alarm on this system, but don't have it any longer. I removed it some time ago - before I tried to get BOINC working. I actually thought about this last night and double checked to make sure I didn't have anything else running.

I doubt if my ISP is blocking the site since my browser can access the site without any problem. I even tried to ping my own website and couldn't ping that either so I'm sure it has nothing to do with BOINC. The question is what is blocking access.
Hughes Glantzberg
The PC Help Desk

It's interesting to see how a ping goes through and how not. Btw, look at the actual address being resolved in the ping:

C:Documents and SettingsJorden>ping setiathome.berkeley.edu

Pinging setiathome.SSL.berkeley.edu [128.32.18.151] with 32 bytes of data:

Reply from 128.32.18.151: bytes=32 time=187ms TTL=240
Reply from 128.32.18.151: bytes=32 time=172ms TTL=240
Reply from 128.32.18.151: bytes=32 time=172ms TTL=240
Reply from 128.32.18.151: bytes=32 time=157ms TTL=240

Ping statistics for 128.32.18.151:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 157ms, Maximum = 187ms, Average = 172ms

C:Documents and SettingsJorden>ping http://setiathome.berkeley.edu
Unknown host http://setiathome.berkeley.edu.

If I ping at the http address the host is unknown. Without http address it points to the old address. Weird. ;)

@Hughes, I doubt that your ISP blocks pings, but what you can try is the following: Start->Run, type command {hit enter}
type Netstat -s {hit Enter}

Can you then copy & paste the results of that window here?

----------------------
Jordâ„¢
[url=http://www.boinc.dk/index.php?page=user_statistics&userid=41965]

As I said when I started this thread, I have five computers running BOINC. Four of them connect just fine. There is only one that cannot connect. All five computers connect through the same ISP. Two are connecting via DSL and two are connecting via dialup. The one that does not connect is on a wireless connection to DSL. Today I'm going to try hooking it up to dialup and see if it connects that way.
Hughes Glantzberg
The PC Help Desk

I finally found the solution to my problem. Although I didn't see Zone Alarm running, it was still installed on the system and evidently enough of it was still loading to interfere with my connection. I uninstalled Zone Alarm and SETI@home/BOINC is now running fine.

Thanks for all the help from everyone.
Hughes Glantzberg