Questions and Answers :
Web site :
503 error message even to web site
Message board moderation
Author | Message |
---|---|
msetzerii Send message Joined: 28 Mar 00 Posts: 7 Credit: 110,890,892 RAC: 5 |
Since about February 13th have not been able to connect to either seti or rosetta sites for uploading or downloading units, or even looking at web pages from my college. Works fine from home systems. The 503 service unavailable error comes up with no details. The ABC and Einstein projects connect fine. College has IPs in the range of 203.215.52.0/22 Home machine is in my ISPs range that includes 202.128.80.x I was even able to bounce thru my home squid server to upload units that had been downloaded before and completed, but was to slow to be usable to download units from all projects. Any way to find out what is causing the problem? Our MIS department doesn't seem to see any problem? Both seti and rosetta are in the 128.x.x.x blocks, so wondering if some weird routing problem? |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
|
msetzerii Send message Joined: 28 Mar 00 Posts: 7 Credit: 110,890,892 RAC: 5 |
Trace from school traceroute to setiathome.berkeley.edu (128.32.18.150), 30 hops max, 60 byte packets 1 192.168.50.1 (192.168.50.1) 1.396 ms 1.519 ms 2.049 ms 2 172.16.3.1 (172.16.3.1) 0.786 ms 0.810 ms 0.797 ms 3 203-215-52-1.guamcc.edu (203.215.52.1) 1.641 ms 1.782 ms 1.867 ms 4 202.128.17.166 (202.128.17.166) 1.534 ms 1.540 ms 1.546 ms 5 * * * 6 198.81.233.238.guam.net (198.81.233.238) 131.468 ms 139.998 ms 140.314 ms 7 64.129.197.73 (64.129.197.73) 146.906 ms 131.156 ms 147.112 ms 8 pao1-pr1-xe-1-3-0-0.us.twtelecom.net (66.192.243.98) 172.189 ms 124.055 ms 172.195 ms 9 dc-oak-core1--paix-px1-ge.cenic.net (137.164.47.175) 157.319 ms 157.319 ms 157.313 ms 10 dc-oak-agg1--oak-core1-10ge.cenic.net (137.164.47.112) 130.457 ms 146.277 ms 147.243 ms 11 137.164.50.31 (137.164.50.31) 137.784 ms 148.409 ms 148.409 ms 12 t2-3.inr-201-sut.Berkeley.EDU (128.32.0.37) 158.155 ms 158.158 ms 142.968 ms 13 * * * No further responses. Trace from Home traceroute to setiathome.berkeley.edu (128.32.18.150), 30 hops max, 60 byte packets 1 * * * 2 202.128.2.49 (202.128.2.49) 877.647 ms 877.849 ms 878.115 ms 3 gw5-sw2.guam.net (202.128.2.9) 876.974 ms 877.224 ms 878.831 ms 4 gw6-gw5.guam.net (202.128.2.2) 945.169 ms * * 5 * * * 6 * * 64.129.197.73 (64.129.197.73) 242.301 ms 7 pao1-pr1-xe-1-3-0-0.us.twtelecom.net (66.192.243.98) 244.727 ms 244.936 ms 244.770 ms 8 dc-oak-core1--paix-px1-ge.cenic.net (137.164.47.175) 243.100 ms 207.650 ms 191.488 ms 9 dc-oak-agg1--oak-core1-10ge.cenic.net (137.164.47.112) 190.661 ms 190.656 ms 189.444 ms 10 137.164.50.31 (137.164.50.31) 191.322 ms 293.678 ms 536.849 ms 11 t2-3.inr-201-sut.Berkeley.EDU (128.32.0.37) 536.690 ms 536.679 ms 532.719 ms 12 g5-1.inr-204-sut.Berkeley.EDU (128.32.255.105) 700.391 ms 1032.764 ms 997.624 ms 13 * * * 14 thinman.ssl.berkeley.edu (128.32.18.150) 829.216 ms 373.993 ms 151.958 ms |
BilBg Send message Joined: 27 May 07 Posts: 3720 Credit: 9,385,827 RAC: 0 |
Try also these: SETI@home Servers 208.68.240.13 download 208.68.240.16 upload 208.68.240.18 download 208.68.240.20 scheduler  - ALF - "Find out what you don't do well ..... then don't do it!" :)  |
msetzerii Send message Joined: 28 Mar 00 Posts: 7 Credit: 110,890,892 RAC: 5 |
I can traceroute to all those addresses from the college sites, but the address returned by setiathome.berkeley.edu (128.32.18.150) still does not work from the college? |
msetzerii Send message Joined: 28 Mar 00 Posts: 7 Credit: 110,890,892 RAC: 5 |
Did some testing with wireshark and when going thru my home proxy I see traffic on ports in the range of 40249 thru 40258 during 3 test, while going directly give no traffic and then gets the 503 error. The info I got from our MIS on the firewall setup for my systems seems restrictive. Info from our MIS Department? The following outbound ports are enabled specifically for IP addresses. TCP 3128 4040 587 5900-5999 8080 UDP (linux traceroute) 33434-33534  Inbound ports allowed to the external IP’s are: TCP 135 37 5900-5999 21 80 22  -Joel |
msetzerii Send message Joined: 28 Mar 00 Posts: 7 Credit: 110,890,892 RAC: 5 |
Still getting same error messages. Traceroutes fail from the college using its newer 203.215.52.x addresses, but using the older ISP addresses work fine 202.128.72.x? Traceroute using college IP stops at 128.32.0.37. First 3 hops are internal college. hop 4 is our router connected to ISP. traceroute to setiathome.berkeley.edu (128.32.18.150), 30 hops max, 60 byte packets 1 192.168.7.1 (192.168.7.1) 2 192.168.50.1 (192.168.50.1) 3 172.16.3.1 (172.16.3.1) 4 203-215-52-1.guamcc.edu (203.215.52.1) 5 202.128.17.166 (202.128.17.166) 6 202.128.5.145.guam.net (202.128.5.145) 7 198.81.233.238.guam.net (198.81.233.238) 8 64.129.197.73 (64.129.197.73) 9 pao1-pr1-xe-0-3-0-0.us.twtelecom.net (66.192.253.26) 10 dc-oak-core1--paix-px1-ge.cenic.net (137.164.47.19) 11 dc-oak-agg1--oak-core1-10ge.cenic.net (137.164.47.112) 12 137.164.50.31 (137.164.50.31) 13 t2-3.inr-201-sut.Berkeley.EDU (128.32.0.37) No further responses Traceroute from my home system using same ISP. Takes same basic path and gets to 128.32.0.37, but then continues on and gets to the 128.32.18.150? traceroute to setiathome.berkeley.edu (128.32.18.150), 30 hops max, 60 byte packets 1 * * * 2 202.128.2.49 (202.128.2.49) 3 gw5-sw2.guam.net (202.128.2.9) 4 * * * 5 * * * 6 * 64.129.197.73 (64.129.197.73) 7 pao1-pr1-xe-0-3-0-0.us.twtelecom.net (66.192.253.26) 8 dc-oak-core1--paix-px1-ge.cenic.net (137.164.47.175) 9 dc-oak-agg1--oak-core1-10ge.cenic.net (137.164.47.112) 10 137.164.50.31 (137.164.50.31) 11 t2-3.inr-201-sut.Berkeley.EDU (128.32.0.37) 12 g5-1.inr-204-sut.Berkeley.EDU (128.32.255.105) 13 * * * 14 thinman.ssl.berkeley.edu (128.32.18.150) Wireshark doesn't show any errors, just no responses, so it appears it is dropping into a black hole? This also happens with rosetta site, and just noticed it happens with tinyurl site. ABC and Eienstein have no problem? |
BilBg Send message Joined: 27 May 07 Posts: 3720 Credit: 9,385,827 RAC: 0 |
This also happens with Rosetta site, and just noticed it happens with tinyurl site. ABC and Einstein have no problem? This only shows that your college is implementing some block-filter based on IP ranges. (or you use software like PeerBlock with unneeded IP ranges added to block list) There is nothing SETI, Rosetta, tinyurl, ... (you will find more sites to add here) can do about it. You have to investigate what is the difference (maybe router) between "its newer 203.215.52.x addresses" (blocks) and "the older ISP addresses 202.128.72.x" (work fine) Yell at your college net admins that you are blocked to access sites that you need "for science" Â - ALF - "Find out what you don't do well ..... then don't do it!" :) Â |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.