Hi,
I tried attaching to predictor@home, but it looks like I can't connect to any server within the scripps.edu domain. I tried using visualroute from any public servers on the net (Italy, where I live, The US and others) but looks like San Diego Supercomputer Center is blcoking all traffic to www.scripps.edu, regardless where it comes from.
This is happening since months, so I'm wonderingf who's taking part in Predictor@home and how they could do it (and how could I possibly...)
.

Bye

darkpella

---

I just tried www.scripps.edu and got through. The PAH website URL(for attachment) is http://predictor.scripps.edu, and I also can get through with that address.

I don't know what to say. except to try the URL I'm providing.

tony

---

Boinc Wiki

Sometimes I hate my Bob Newhart style of humor.

I just tried www.scripps.edu and got through. The PAH website URL(for attachment) is http://predictor.scripps.edu, and I also can get through with that address.

I don't know what to say. except to try the URL I'm providing.

tony

Tried again, both with boinc manager, Firfox, ping and tracert, but the connection times out.

Could be that scrpps is somehow restrcited to US resident IPs due to federal regulations (I live in Italy)?

darkpella

---

I've just looked at the main page and message boards, and see no other reports of this. I don't know how to help you. Perhaps your backbone provider stopped peering with whomever predictor uses?? I don't know.

tony

---

Boinc Wiki

Sometimes I hate my Bob Newhart style of humor.

I just tried www.scripps.edu and got through. The PAH website URL(for attachment) is http://predictor.scripps.edu, and I also can get through with that address.

I don't know what to say. except to try the URL I'm providing.

tony

Tried again, both with boinc manager, Firfox, ping and tracert, but the connection times out.

Could be that scrpps is somehow restrcited to US resident IPs due to federal regulations (I live in Italy)?

darkpella

I'm not currently attached to Predictor, but in the past I had no problems and I'm in South Korea.

---

Kathryn :o)

I just tried www.scripps.edu and got through. The PAH website URL(for attachment) is http://predictor.scripps.edu, and I also can get through with that address.

I don't know what to say. except to try the URL I'm providing.

tony

Tried again, both with boinc manager, Firfox, ping and tracert, but the connection times out.

Could be that scrpps is somehow restrcited to US resident IPs due to federal regulations (I live in Italy)?

darkpella

I'm not currently attached to Predictor, but in the past I had no problems and I'm in South Korea.

Well, could anyoneplease provide me with an e-mail address of predictor's hos administrator, if it can be found on predictor's web page, or with the adiministrator of scripps web page so that i may contact her/him and ask?

Thanks

darkpella

---

boinc@scripps.edu

---

Boinc Wiki

Sometimes I hate my Bob Newhart style of humor.

boinc@scripps.edu

Thanks Tony

---

Hi,
I tried attaching to predictor@home, but it looks like I can't connect to any server within the scripps.edu domain. I tried using visualroute from any public servers on the net (Italy, where I live, The US and others) but looks like San Diego Supercomputer Center is blcoking all traffic to www.scripps.edu, regardless where it comes from.
This is happening since months, so I'm wonderingf who's taking part in Predictor@home and how they could do it (and how could I possibly...)

Can you copy here the results of "TRACERT predictor.scripps.edu" command ? (or "traceroute predictor.scripps.edu" under Linux)

Does predictor.scripps.edu have an IP of 137.131.252.96 ?

Because I suspect the problem is due to "DNS poisoning", as I've noticed the same issue in the past.

---

How-To: Join Distributed Computing projects that benefit humanity

Hi,
I tried attaching to predictor@home, but it looks like I can't connect to any server within the scripps.edu domain. I tried using visualroute from any public servers on the net (Italy, where I live, The US and others) but looks like San Diego Supercomputer Center is blcoking all traffic to www.scripps.edu, regardless where it comes from.
This is happening since months, so I'm wonderingf who's taking part in Predictor@home and how they could do it (and how could I possibly...)

Can you copy here the results of "TRACERT predictor.scripps.edu" command ? (or "traceroute predictor.scripps.edu" under Linux)

Does predictor.scripps.edu have an IP of 137.131.252.96 ?

Because I suspect the problem is due to "DNS poisoning", as I've noticed the same issue in the past.

Hi dhatz,

looks like the IP is right; the tracert reports are below. Please notice that the IP (wahoo.sdsc.edu) it can't go past is the same even tracert-ing from a VisualRoute server and from other online tracert servers.

Thanks for assisting.

darkpella

TRACERT log from my PC:
C:\\Documents and Settings\\Riccardo>tracert predictor.scripps.edu

Rilevazione instradamento verso predictor1.scripps.edu [137.131.252.96]
su un massimo di 30 punti di passaggio:

1 1 ms <10 ms <10 ms 192.168.7.254
2 192 ms 85 ms 57 ms 37.253.124.1
3 21 ms 22 ms 21 ms 10.3.7.194
4 21 ms 21 ms 22 ms 10.254.1.189
5 23 ms 23 ms 22 ms 10.254.0.102
6 27 ms 47 ms 26 ms 10.254.1.69
7 * * * Richiesta scaduta.
8 * * * Richiesta scaduta.
9 * * * Richiesta scaduta.
10 835 ms 661 ms 1281 ms 83-103-100-222.ip.fastwebnet.it [83.103.100.222]

11 1984 ms 1992 ms 2013 ms gi-6-3.rom20.ip.tiscali.net [213.200.68.213]
12 2215 ms 2197 ms 711 ms so-2-0-0.sjc10.ip.tiscali.net [213.200.81.153]
13 779 ms 798 ms 794 ms ge-6-8.car4.SanJose1.Level3.net [4.68.111.165]
14 818 ms 810 ms 808 ms ae-31-51.ebr1.SanJose1.Level3.net [4.68.123.30]

15 849 ms 862 ms 882 ms ae-2.ebr1.LosAngeles1.Level3.net [4.69.132.10]
16 876 ms 857 ms 864 ms ge-0-0-0-55.gar1.LosAngeles1.Level3.net [4.68.10
2.144]
17 906 ms 896 ms 581 ms CENIC.gar1.Level3.net [64.156.191.10]
18 451 ms 470 ms 349 ms inet-sdsc-sdsc2--lax-isp-ge.cenic.net [137.164.2
4.206]
19 397 ms 363 ms 300 ms wahoo.sdsc.edu [198.17.46.12]
20 * * * Richiesta scaduta.
21 * * * Richiesta scaduta.
22 * * * Richiesta scaduta.
23 * * * Richiesta scaduta.
24 * * * Richiesta scaduta.
25 * * * Richiesta scaduta.
26 * * * Richiesta scaduta.
27 * * * Richiesta scaduta.
28 * * * Richiesta scaduta.
29 * * * Richiesta scaduta.
30 * * * Richiesta scaduta.

Rilevazione completata.

TRACERT log from www.subnetonline.com
Input Query: predictor.scripps.edu
Started at: 09:14:28
Stopped at: 09:18:19

1 hosted.by.i-s-e.nl (83.172.128.67) 0.073 ms 0.061 ms 0.040 ms
2 ge-1-3-0-1.cr1.rb2f.nl.proserve.nl (80.84.254.1) 0.397 ms 0.347 ms 0.484 ms
3 gsr12416.ams.he.net (195.69.145.150) 2.984 ms 1.887 ms 1.233 ms
4 pos0-0.gsr12416.lon.he.net (216.66.24.157) 9.488 ms 8.752 ms 8.857 ms
5 pos4-1.gsr12416.nyc.he.net (216.218.200.101) 78.827 ms 78.927 ms 78.915 ms
6 pos7-0.gsr12012.sjc.he.net (216.218.254.153) 155.372 ms 155.319 ms 155.389 ms
7 pos11-3.gsr12416.pao.he.net (216.218.214.245) 160.618 ms 160.575 ms 160.748 ms
8 paix-px1--hurricane-ge.cenic.net (198.32.251.69) 157.358 ms 155.313 ms 155.819 ms
9 dc-oak-dc2--oak-dc1-p2p-2.cenic.net (137.164.22.195) 155.529 ms 155.600 ms 157.134 ms
10 dc-csac-dc1--oak-dc2-ge.cenic.net (137.164.22.111) 163.596 ms 163.749 ms 163.600 ms
11 dc-lax-dc1--sac-dc1-pos.cenic.net (137.164.22.126) 163.229 ms 163.045 ms 163.236 ms
12 hpr-lax-hpr--dc-lax-dc2-ge--2.cenic.net (137.164.22.21) 163.779 ms 163.531 ms 163.594 ms
13 dc-tus-dc1--lax-dc2-pos.cenic.net (137.164.22.43) 156.625 ms 156.260 ms 156.240 ms
14 dc-sdsc-sdsc2--tus-dc1-ge.cenic.net (137.164.24.174) 167.101 ms 166.722 ms 166.990 ms
15 wahoo.sdsc.edu (198.17.46.12) 167.742 ms 167.205 ms 167.381 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

TRACERT log from centralops.net
Tracing route to predictor.scripps.edu [137.131.252.96]...
hop rtt rtt rtt ip address domain name
1 0 0 0 63.134.215.1
2 0 0 0 216.197.122.81 dr-ded1-ge-1-6.crystaltech.com
3 0 0 0 216.197.122.65 cr-edge1-ge-5-0.crystaltech.com
4 0 0 0 67.131.24.221 phv-edge-01.inet.qwest.net
5 1 1 1 205.171.129.85 tmp-core-01.inet.qwest.net
6 11 11 12 67.14.10.6 bur-core-01.inet.qwest.net
7 12 12 11 205.171.213.106 lap-brdr-01.inet.qwest.net
8 11 11 12 64.200.249.165
9 22 22 22 64.200.200.50 lsanca3lcx1-ceic-14-0.wcg.net
10 14 13 14 137.164.24.206 inet-sdsc-sdsc2--lax-isp-ge.cenic.net
11 14 14 14 198.17.46.12 wahoo.sdsc.edu
12 * * *
13 * * *
14 * * *
15 * * *

Trace aborted

-- end --

TRACERT log from cache.online.ee
traceroute to predictor1.scripps.edu (137.131.252.96): 2-20 hops, 38 byte packets
2 194.106.111.17 kjj-igw5.elion.ee 1.89 ms (ttl=254)
3 194.126.115.195 kjj-bb4-ae-3-0.ee.estpak.ee 1.48 ms (ttl=252!)
4 194.126.97.253 kjj-bb2-ae-0-0.ee.estpak.ee 1.53 ms (ttl=251!)
5 194.126.97.206 ldn-bb1-so-1-0-0-0.uk.estpak.ee 44.4 ms (ttl=250!)
6 195.66.226.21 lon.he.net 80.9 ms (ttl=250)
7 216.218.200.101 pos8-0.gsr12416.nyc.he.net 115 ms (ttl=249)
8 216.218.254.153 pos7-0.gsr12012.sjc.he.net 191 ms (ttl=248)
9 216.218.214.245 pos11-3.gsr12416.pao.he.net 197 ms (ttl=248!)
10 198.32.251.69 paix-px1--hurricane-ge.cenic.net 304 ms (ttl=235!)
11 137.164.22.193 dc-oak-dc2--oakk-dc1-p2p-1.cenic.net 303 ms (ttl=234!)
12 137.164.22.111 dc-csac-dc1--oak-dc2-ge.cenic.net 231 ms (ttl=234!)
13 137.164.22.126 dc-lax-dc1--sac-dc1-pos.cenic.net 207 ms (ttl=235!)
14 137.164.22.21 hpr-lax-hpr--dc-lax-dc2-ge--2.cenic.net 207 ms (ttl=235!)
15 137.164.22.43 dc-tus-dc1--lax-dc2-pos.cenic.net 207 ms (ttl=231!)
16 137.164.24.174 dc-sdsc-sdsc2--tus-dc1-ge.cenic.net 328 ms (ttl=234!)
17 198.17.46.12 wahoo.sdsc.edu 211 ms (ttl=234!)
18 *
19 *
20 *

---

darkpella, your traceroute results look fine to me. They're the same as mine and my BOINC connects to Predictor without problems.

Many sites block ICMP (ping/traceroute) traffic nowadays, so you can't ping or traceroute them, but the site itself is reachable via HTTP/HTTPS (web, used also by BOINC etc).

Do you still have problems attaching to the Predictor@home project?

---

How-To: Join Distributed Computing projects that benefit humanity

darkpella, your traceroute results look fine to me. They're the same as mine and my BOINC connects to Predictor without problems.

Many sites block ICMP (ping/traceroute) traffic nowadays, so you can't ping or traceroute them, but the site itself is reachable via HTTP/HTTPS (web, used also by BOINC etc).

Do you still have problems attaching to the Predictor@home project?

Hi dhatz,

did the following
1. Clicked on the Project->Attach to project menu on Boinc manager menu bar
2. Clicked Next on the dialog that opened
3. Entered http://predictor.scripps.edu as project URL and pressed Next on the dialog that opened
4. Waited while it tried connecting
5. Got a "Project temporary unavailable" message.
6. Opened Firefox
7. Entered http://www.scripps.edu as URL
8. Got "Connection timed out" error
9. Entered http://predictor.scripps.edu as URL
10. Got "Connection timed out" error.

HEEEEEEEEEEEEEEELLLLLLLLLPPPPPPPPP!!!!!!!

darkpella

---

Thought I had an idea, but I was wrong

Thought I had an idea, but I was wrong

Thanks for caring, anyway.

darkpella

---

I've created a thread called "Connecting from Italy" and posted this:


I have a user at the Boinc message board. His username is "darkpella" and here is a link to that thread. He can't attach to PPAH, or even get here with a browser. Can someone help him?

tony

over at ppah, There is a link to this thread.

{edit} this was the first post to their boards in 3 days, so I wouldn't expect an immediate response. LOL

I've created a thread called "Connecting from Italy" and posted this:


I have a user at the Boinc message board. His username is "darkpella" and here is a link to that thread. He can't attach to PPAH, or even get here with a browser. Can someone help him?

tony

over at ppah, There is a link to this thread.

{edit} this was the first post to their boards in 3 days, so I wouldn't expect an immediate response. LOL

Hope someone will help.
Another big thank to mmxiastro meanwhile.

darkpella

---