The Same Problem here also.

C:\Users\Administrator>tracert -h 15 208.68.240.13

Traceren van de route naar boinc2.ssl.berkeley.edu [208.68.240.13]
via maximaal 15 hops:

1 <1 ms <1 ms <1 ms ACA8000A.ipt.aol.com [172.168.0.10]
2 * * * Time-out bij opdracht.
3 10 ms 8 ms 9 ms p5001.net.upc.nl [212.142.5.1]
4 107 ms 94 ms 92 ms 84.116.245.170
5 95 ms 100 ms 96 ms nl-ams05a-rd2-xe-2-1-2-2364.aorta.net [84.116.24
4.57]
6 93 ms 98 ms 107 ms us-nyc01b-rd1-gi-2-0-0.aorta.net [84.116.130.26]

7 93 ms 93 ms 92 ms us-nyc01b-ri1-xe-3-1-0.aorta.net [213.46.190.94]

8 105 ms 99 ms 100 ms core1.nyc4.he.net [198.32.118.57]
9 164 ms 169 ms 174 ms 10gigabitethernet10-2.core1.sjc2.he.net [184.105
.213.197]
10 176 ms 171 ms 174 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
11 * * * Time-out bij opdracht.
12 * * * Time-out bij opdracht.
13 * * * Time-out bij opdracht.
14 * * * Time-out bij opdracht.
15 * * * Time-out bij opdracht.

De trace is voltooid.

I'm not able to reach any of the servers, this has been going on since one or two days ago (september 21st, 22nd)
Location: Leiden, the Netherlands
ISP: Telfort


Pinging 208.68.240.13 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 208.68.240.13:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Pinging 208.68.240.16 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 208.68.240.16:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Pinging 208.68.240.18 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 208.68.240.18:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Pinging 208.68.240.20 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 208.68.240.20:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Tracing route to boinc2.ssl.berkeley.edu [208.68.240.13]
over a maximum of 30 hops:

1 2 ms 4 ms 2 ms 192.168.1.254
2 36 ms 18 ms 17 ms 82-169-11-254.ip.telfort.nl [82.169.11.254]
3 18 ms 19 ms 20 ms 20gigabitethernet1-3.core1.ams1.he.net [195.69.145.150]
4 28 ms 30 ms 29 ms 10gigabitethernet2-1.core1.par2.he.net [184.105.213.102]
5 157 ms 111 ms 107 ms 10gigabitethernet7-1.core1.ash1.he.net [184.105.213.93]
6 185 ms 180 ms 180 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Tracing route to setiboincdata.ssl.berkeley.edu [208.68.240.16]
over a maximum of 30 hops:

1 2 ms 3 ms 3 ms 192.168.1.254
2 19 ms 17 ms 17 ms 82-169-11-254.ip.telfort.nl [82.169.11.254]
3 31 ms 19 ms 23 ms 20gigabitethernet1-3.core1.ams1.he.net [195.69.145.150]
4 30 ms 29 ms 30 ms 10gigabitethernet2-1.core1.par2.he.net [184.105.213.102]
5 107 ms 109 ms 109 ms 10gigabitethernet7-1.core1.ash1.he.net [184.105.213.93]
6 177 ms 178 ms 185 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Tracing route to boinc2.ssl.berkeley.edu [208.68.240.18]
over a maximum of 30 hops:

1 3 ms 5 ms 2 ms 192.168.1.254
2 18 ms 18 ms 18 ms 82-169-11-254.ip.telfort.nl [82.169.11.254]
3 22 ms 21 ms 25 ms 20gigabitethernet1-3.core1.ams1.he.net [195.69.145.150]
4 28 ms 28 ms 28 ms 10gigabitethernet2-1.core1.par2.he.net [184.105.213.102]
5 107 ms 112 ms 107 ms 10gigabitethernet7-1.core1.ash1.he.net [184.105.213.93]
6 183 ms 179 ms 179 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Tracing route to setiboinc.ssl.berkeley.edu [208.68.240.20]
over a maximum of 30 hops:

1 3 ms 8 ms 3 ms 192.168.1.254
2 19 ms 17 ms 18 ms 82-169-11-254.ip.telfort.nl [82.169.11.254]
3 30 ms 19 ms 20 ms 20gigabitethernet1-3.core1.ams1.he.net [195.69.145.150]
4 30 ms 30 ms 30 ms 10gigabitethernet2-1.core1.par2.he.net [184.105.213.102]
5 107 ms 106 ms 115 ms 10gigabitethernet7-1.core1.ash1.he.net [184.105.213.93]
6 178 ms 178 ms 185 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Server: UnKnown
Address: 192.168.1.254

Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.13

Server: UnKnown
Address: 192.168.1.254

Name: setiboincdata.ssl.berkeley.edu
Address: 208.68.240.16

Server: UnKnown
Address: 192.168.1.254

Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.18

Server: UnKnown
Address: 192.168.1.254

Name: setiboinc.ssl.berkeley.edu
Address: 208.68.240.20

---

Hi there,

will it there be a problem with OPENDNS in HE side? please read

I am located in Florida and I am having the same problem, I can not pass HE router, here is the traceroute to the 4 ip addresses

C:\Users\Administrator>tracert 208.68.240.13

Tracing route to boinc2.ssl.berkeley.edu [208.68.240.13]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 13 ms 10 ms 11 ms 205.197.200.1
3 13 ms 13 ms 12 ms ip65-47-56-161.z56-47-65.customer.algx.net [65.47.56.161]
4 39 ms 16 ms 24 ms 216.156.15.25.ptr.us.xo.net [216.156.15.25]
5 44 ms 42 ms 43 ms vb1901.rar3.atlanta-ga.us.xo.net [216.156.0.229]
6 40 ms 46 ms 47 ms te-11-0-0.rar3.washington-dc.us.xo.net [207.88.12.10]
7 40 ms 41 ms 65 ms 207.88.14.161.ptr.us.xo.net [207.88.14.161]
8 40 ms 41 ms 44 ms 206.111.7.94.ptr.us.xo.net [206.111.7.94]
9 111 ms 99 ms 101 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
10 * * * Request timed out.
11 * * * Request timed out.
12 ^C
C:\Users\Administrator>tracert 208.68.240.16

Tracing route to setiboincdata.ssl.berkeley.edu [208.68.240.16]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 13 ms 23 ms 205.197.200.1
3 15 ms 13 ms 12 ms ip65-47-56-161.z56-47-65.customer.algx.net [65.47.56.161]
4 25 ms 13 ms 18 ms 216.156.15.29.ptr.us.xo.net [216.156.15.29]
5 41 ms 44 ms 46 ms vb1901.rar3.atlanta-ga.us.xo.net [216.156.0.229]
6 41 ms 41 ms 50 ms te-11-0-0.rar3.washington-dc.us.xo.net [207.88.12.10]
7 * * * Request timed out.
8 46 ms 54 ms 44 ms 206.111.7.94.ptr.us.xo.net [206.111.7.94]
9 97 ms 97 ms 97 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
10 * * * Request timed out.
11 * * * Request timed out.
12 ^C
C:\Users\Administrator>tracert 208.68.240.18

Tracing route to boinc2.ssl.berkeley.edu [208.68.240.18]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 14 ms 23 ms 11 ms 205.197.200.1
3 14 ms 12 ms 11 ms ip65-47-56-161.z56-47-65.customer.algx.net [65.47.56.161]
4 13 ms 13 ms 21 ms 216.156.15.29.ptr.us.xo.net [216.156.15.29]
5 46 ms 67 ms 47 ms vb1901.rar3.atlanta-ga.us.xo.net [216.156.0.229]
6 41 ms 47 ms 47 ms te-11-0-0.rar3.washington-dc.us.xo.net [207.88.12.10]
7 * * * Request timed out.
8 43 ms 50 ms 47 ms 206.111.7.94.ptr.us.xo.net [206.111.7.94]
9 98 ms 99 ms 101 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
10 * * * Request timed out.
11 * * * Request timed out.
12 ^C
C:\Users\Administrator>tracert 208.68.240.20

Tracing route to setiboinc.ssl.berkeley.edu [208.68.240.20]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 12 ms 10 ms 11 ms 205.197.200.1
3 17 ms 12 ms 13 ms ip65-47-56-161.z56-47-65.customer.algx.net [65.47.56.161]
4 26 ms 12 ms 14 ms 216.156.15.29.ptr.us.xo.net [216.156.15.29]
5 43 ms 42 ms 44 ms vb1901.rar3.atlanta-ga.us.xo.net [216.156.0.229]
6 59 ms 56 ms 68 ms te-11-0-0.rar3.washington-dc.us.xo.net [207.88.12.10]
7 42 ms * 45 ms 207.88.14.161.ptr.us.xo.net [207.88.14.161]
8 53 ms 47 ms 49 ms 206.111.7.94.ptr.us.xo.net [206.111.7.94]
9 105 ms 99 ms 99 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
10 * * * Request timed out.
11 * * * Request timed out.

I can not pass the HE routers.

Then, I made an nslookup to the 4 ip addresses from my computer and they resolve correctly to the above mentioned ips using my default dns settings from my ISP (dns: 65.106.1.196)

If I made the same nslookup to the 4 ip addresses but this time using OPENDNS settings (dns: 208.67.222.222) they all return error, as is they don't exist.

I hope this helps somebody.

Cheers

---

Yes, After reading the answers to my post I did uninstall Boinc.

I'm sorry to hear that. If I stopped doing things every time someone made me mad or offended me, I wouldn't be doing anything at all.

Good luck to you in whatever it is you decide to do.

I would like to have my system but more then not there seems to be no way to get or send finished work

If it was true how then you can have 86 Valid tasks?:
Valid tasks for computer 6075732
http://setiathome.berkeley.edu/results.php?hostid=6075732&offset=0&show_names=0&state=3&appid=

(obviously you were able to get tasks and send finished work (= you were able to connect OK to at least 3 SETI servers))

Yes, After reading the answers to my post I did uninstall Boinc.

If you think that the uninstall of BOINC will remove all the files you are very wrong.
Where to go to delete the remaining files - find by yourself (in many other threads on the forum you can find clues).

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

PS: My machines still can't connect without proxy... thanks for listening to the unimportant part of the cruncher community

---

A tracert to boinc2.ssl.berkeley.edu now seems to be working and my client can now connect (at least for me). [:o)

---

Still dead here :-(

Some results of traceroute:

10gigabitethernet1-1.core1.pao1.he.net = ok
10gigabitethernet3-2.core1.pao1.he.net = no reply
10gigabitethernet7-4.core1.pao1.he.net = no reply

Looks like some routers at HE are ok, and others are black holes.

Anyone else?

Unfortunately, my experience wasn't as clear-cut as that. I had a bout of connection problems from the UK in the early hours of Friday morning. Here are the gigabit sections of four separate traces to 208.68.240.16 (file upload server) made over an interval of less than an hour, rebooting my home ADSL router between each trace.

 11    27 ms    37 ms    29 ms  10gigabitethernet1-1.core1.lon1.he.net [195.66.224.21]
 12   115 ms   111 ms   112 ms  apiicqnetstg-mtc-a.evip.aol.com [72.52.92.137]
 13   184 ms   187 ms   185 ms  10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
 14     *        *        *     Request timed out.

 11    38 ms    38 ms    29 ms  10gigabitethernet1-1.core1.lon1.he.net [195.66.224.21]
 12   112 ms   121 ms   113 ms  10gigabitethernet6-3.core1.ash1.he.net [72.52.92.137]
 13   189 ms   182 ms   191 ms  10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
 14   182 ms   181 ms   182 ms  10gigabitethernet6-3.core1.ash1.he.net [64.71.140.42]
 15   222 ms   222 ms   221 ms  208.68.243.254
 16   244 ms   227 ms   226 ms  setiboincdata.ssl.berkeley.edu [208.68.240.16]

 11    27 ms    42 ms    29 ms  10gigabitethernet1-1.core1.lon1.he.net [195.66.224.21]
 12   113 ms   113 ms   112 ms  10gigabitethernet6-3.core1.ash1.he.net [72.52.92.137]
 13   181 ms   180 ms   191 ms  10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
 14     *        *        *     Request timed out.

 11    30 ms    36 ms    30 ms  10gigabitethernet1-1.core1.lon1.he.net [195.66.224.21]
 12   120 ms   124 ms   112 ms  10gigabitethernet6-3.core1.ash1.he.net [72.52.92.137]
 13   184 ms   183 ms   189 ms  10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
 14   185 ms   185 ms   204 ms  64.71.140.42
 15   224 ms     *      223 ms  208.68.243.254
 16   227 ms   226 ms   226 ms  setiboincdata.ssl.berkeley.edu [208.68.240.16]

The first two attempts gave me DNS errors as well, part of the trouble I've been having with my ISP. It was only the fourth connection which allowed me to both find, and talk to, the file upload server.

Can´t get any wu´s too. I tried a project reset and could download the folowing:

26.09.2011 04:14:23 | SETI@home | Resetting project
26.09.2011 04:14:27 | SETI@home | Sending scheduler request: To fetch work.
26.09.2011 04:14:27 | SETI@home | Requesting new tasks for NVIDIA GPU
26.09.2011 04:14:30 | SETI@home | Scheduler request completed: got 0 new tasks
26.09.2011 04:14:30 | SETI@home | Project has no tasks available
26.09.2011 04:14:32 | SETI@home | Started download of arecibo_181.png
26.09.2011 04:14:32 | SETI@home | Started download of sah_40.png
26.09.2011 04:14:34 | SETI@home | Finished download of sah_40.png
26.09.2011 04:14:34 | SETI@home | Started download of sah_banner_290.png
26.09.2011 04:14:36 | SETI@home | Finished download of arecibo_181.png
26.09.2011 04:14:36 | SETI@home | Finished download of sah_banner_290.png
26.09.2011 04:14:36 | SETI@home | Started download of sah_ss_290.png
26.09.2011 04:14:39 | SETI@home | Finished download of sah_ss_290.png
26.09.2011 04:19:37 | SETI@home | Sending scheduler request: To fetch work.
26.09.2011 04:19:37 | SETI@home | Requesting new tasks for CPU
26.09.2011 04:19:39 | SETI@home | Scheduler request completed: got 1 new tasks
26.09.2011 04:19:39 | SETI@home | Resent lost task ap_27jn11aa_B6_P0_00114_20110919_19912.wu_1
26.09.2011 04:19:39 | SETI@home | Project has no tasks available
26.09.2011 04:19:41 | SETI@home | Started download of astropulse_5.05_windows_intelx86.exe
26.09.2011 04:19:41 | SETI@home | Started download of astropulse_5.05_AUTHORS
26.09.2011 04:19:42 | SETI@home | Temporarily failed download of astropulse_5.05_windows_intelx86.exe: HTTP error
26.09.2011 04:19:42 | SETI@home | Backing off 13 min 14 sec on download of astropulse_5.05_windows_intelx86.exe
26.09.2011 04:19:42 | SETI@home | Finished download of astropulse_5.05_AUTHORS
26.09.2011 04:19:42 | SETI@home | Started download of astropulse_5.05_COPYING
26.09.2011 04:19:42 | SETI@home | Started download of astropulse_5.05_COPYRIGHT
26.09.2011 04:19:43 | SETI@home | Finished download of astropulse_5.05_COPYING
26.09.2011 04:19:43 | SETI@home | Finished download of astropulse_5.05_COPYRIGHT
26.09.2011 04:19:43 | SETI@home | Started download of ap_graphics_5.05_windows_intelx86.exe
26.09.2011 04:19:43 | SETI@home | Started download of libfftw3f-3-1-1a_upx.dll
26.09.2011 04:19:48 | SETI@home | Finished download of ap_graphics_5.05_windows_intelx86.exe
26.09.2011 04:19:48 | SETI@home | Finished download of libfftw3f-3-1-1a_upx.dll
26.09.2011 04:19:48 | SETI@home | Started download of ap405.jpg
26.09.2011 04:19:48 | SETI@home | Started download of ap_27jn11aa_B6_P0_00114_20110919_19912.wu
26.09.2011 04:19:50 | SETI@home | Finished download of ap405.jpg
26.09.2011 04:20:00 | SETI@home | Finished download of ap_27jn11aa_B6_P0_00114_20110919_19912.wu

26.09.2011 04:32:57 | SETI@home | Started download of astropulse_5.05_windows_intelx86.exe
26.09.2011 04:32:58 | SETI@home | Temporarily failed download of astropulse_5.05_windows_intelx86.exe: HTTP error
26.09.2011 04:32:58 | SETI@home | Backing off 32 min 30 sec on download of astropulse_5.05_windows_intelx86.exe


The download of the .exe reaches 0,77% and stops

It seem´s to me that there is a problem with the astropulse_5.05_windows_intelx86.exe. Maybe that´s a new version and perhaps it´s dad linked or named in the database?

now i deleted the astropulse WU and did a project reset -and all of a sudden - i´m gettin SetiHome Enhanced WU´s en mass. no probs with up- or downloads.

Happy crunching

Now it seems this proxy has gone bad:
9/26/2011 4:39:30 PM | | Using HTTP proxy 72.52.96.30:80
9/26/2011 4:39:32 PM | SETI@home | update requested by user
9/26/2011 4:39:33 PM | SETI@home | Sending scheduler request: Requested by user.
9/26/2011 4:39:33 PM | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
9/26/2011 4:39:34 PM | SETI@home | Scheduler request failed: Error 403

and without the proxy:
9/26/2011 4:46:36 PM | | Not using a proxy
9/26/2011 4:49:05 PM | SETI@home | update requested by user
9/26/2011 4:49:06 PM | SETI@home | Sending scheduler request: Requested by user.
9/26/2011 4:49:06 PM | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
9/26/2011 4:49:27 PM | | Project communication failed: attempting access to reference site
9/26/2011 4:49:27 PM | SETI@home | Scheduler request failed: Couldn't connect to server
9/26/2011 4:49:30 PM | | Internet access OK - project servers may be temporarily down.

---

This Proxy works for the moment 184.72.223.0:80

why do we all need to send here these (important) information about ping, traceroute and nslookup?
i see 1 problem here
AND this is NOT our network settings

why do we all need to send here these (important) information about ping, traceroute and nslookup?
i see 1 problem here
AND this is NOT our network settings

A brief answer to each of the 7 questions in the original post by Matt Lebofsky would be adequate now. It didn't really ask for full postings of the output from ping, traceroute, and nslookup, but many users are not familiar enough with those tools to confidently give a brief answer.

The issue isn't only whether what you send reaches the servers, it's also whether the servers can reply. That's why knowing details of both ends of the attempted connection is important.

                                                                  Joe

1. Are you able to reach ANY of the upload, download, or scheduling servers? no
2. When did you start having this problem? 9/21
3. What is your ISP? Time Warner
4. What is your geographic location? NYC
5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20? 5 packets transmitted, 0 packets received, 100% packet loss
6. How about traceroutes of the above four addresses?
9 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 90.306 ms 93.928 ms 86.407 ms

10 * * * Request timed out.

7. Or nslookups of the above four addresses? DNS query for setiathome.berkeley.edu failed: Timed out

Additionally, I cannot connect via cellphone tether although said tethering allows me to visit other sites just fine.

---

Lately I think I might do as well with an Abacus as with a 4 core computer, since I get very little data to keep the thing occupied.
I don't mind doing the Greenhouse thing, but my interest is Seti and only Seti.
how do I get enough data to run 4 cores 24/7 without constant attempts to get data into the box.
Cheers MaxG.

---

And the Network is UP!!!
I'm now able to get through without a proxy. Not getting a lot of work due to the logjam but when I do the downloads "hoot", peak speeds of up to 30KBs, this is about 10 times faster than what I was getting before this problem went terminal.

Hopefully the fix is in.