Verizon is also my ISP but I'm still unable to reach Lunatics from South-Eastern Pennsylvania. I hit a brick wall after going through 64.209.102.222. This seems to be the pattern.

@Joker, do you have trouble receiving email from Lunatics? Verizon seems to block them for me.

No problems at all here.....
I have DSL service from AT&T............

---

"Time is simply the mechanism that keeps everything from happening all at once."

Verizon is also my ISP but I'm still unable to reach Lunatics from South-Eastern Pennsylvania. I hit a brick wall after going through 64.209.102.222. This seems to be the pattern.

@Joker, do you have trouble receiving email from Lunatics? Verizon seems to block them for me.

No idea really, As I haven't logged into lunatics in a long time, Besides I don't use Verizons email at all(Hint: It ain't yahoo either). :D

K . . Tks

If Mark has no problems with AT&T DSL, my problem must be with Road Runner. I still get hung up on the same address.


Tracing route to lunatics.kwsn.net [206.132.254.42]
over a maximum of 30 hops:
0 [192.168.0.100]
1 192.168.0.1
2 76.51.128.1
3 gig-5-0.gnbywi2-rtr1.new.rr.com [24.164.241.17]
4 so0-1-1.cgchill3-rtr1.kc.rr.com [24.94.160.29]
5 ae-5-0.cr0.chi30.tbone.rr.com [66.109.6.112]
6 ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
7 66.109.9.202
8 64.209.102.222<--------This one here
9 * * *

---

Clk2HlpSetiCty:::PayIt4ward

Here's My trace of the lunatics website from Verizon territory:

Tracing route to lunatics.kwsn.net [206.132.254.42]
over a maximum of 30 hops:

  1    26 ms    27 ms    26 ms  L100.DSL-35.LSANCA.verizon-gni.net [71.105.32.1]
  2    27 ms    26 ms    26 ms  G9-0-2035.LCR-10.LSANCA.verizon-gni.net [130.81.136.16]
  3    29 ms    28 ms    32 ms  P15-3.LCR-01.TAMPFL.verizon-gni.net [130.81.28.74]
  4    31 ms    30 ms    32 ms  0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
  5    30 ms    34 ms    30 ms  0.so-6-3-0.XT2.LAX7.ALTER.NET [152.63.112.69]
  6    98 ms    33 ms    32 ms  0.so-7-0-0.BR1.LAX7.ALTER.NET [152.63.112.153]
  7     *       33 ms    39 ms  204.255.169.70
  8    94 ms    93 ms    93 ms  cr2-pos-0-0-0-0.Atlanta.savvis.net [204.70.192.69]
  9    96 ms    96 ms    96 ms  msr1-te-0-0-0-0.atlantapaix.savvis.net [204.70.200.1]
 10    93 ms    93 ms    93 ms  204.70.203.94
 11    92 ms    92 ms    93 ms  216.89.82.78
 12    92 ms    93 ms    94 ms  xconn.core2-edge1.atl.oneringnetworks.net [66.187.176.5]
 13    93 ms    93 ms    93 ms  xconn.dktc-56m.atl.oneringnetworks.net [66.187.178.58]
 14    93 ms    93 ms    94 ms  beat42.gzz.cyb.cream.spectacularrebeats.net [206.132.254.42]

Trace complete.

What would I type in my RUN box to do a trace from here?

---

Official Abuser of Boinc Buttons...
And no good credit hound!

What would I type in my RUN box to do a trace from here?

tracert lunatics.kwsn.net

Type

cmd

in the run box, to get a command window. Then type what he said, at the command prompt.

Otherwise the output disappears before you get a chance to read it.

I am able to access the site
Location: Suburb of Milwaukee, Wisconsin (most speed test sites even say my location is Milwaukee!)
ISP: SBC (now ATT)
Traceroute:
traceroute to lunatics.kwsn.net (206.132.254.42) ,30 hops max,40 byte packet
1 69.210.111.254 (69.210.111.254) 10. 0 ms <10.0 ms <10.0 ms
2 65.43.19.226 (65.43.19.226) 10. 0 ms 10. 0 ms 10. 0 ms
3 151.164.190.98 (151.164.190.98) 10. 0 ms 10. 0 ms <10.0 ms
4 151.164.42.149 (151.164.42.149) 10. 0 ms 10. 0 ms 10. 0 ms
5 151.164.251.90 (151.164.251.90) 10. 0 ms 10. 0 ms 10. 0 ms
6 204.70.196.21 (204.70.196.21) 10. 0 ms 10. 0 ms 10. 0 ms
7 204.70.195.113 (204.70.195.113) 20. 0 ms * 10. 0 ms
8 204.70.192.61 (204.70.192.61) 40. 0 ms 40. 0 ms 40. 0 ms
9 204.70.200.1 (204.70.200.1) 50. 0 ms 50. 0 ms 50. 0 ms
10 204.70.203.98 (204.70.203.98) 50. 0 ms 40. 0 ms 40. 0 ms
11 216.89.82.78 (216.89.82.78) 40. 0 ms 40. 0 ms 40. 0 ms
12 66.187.176.5 (66.187.176.5) 40. 0 ms 40. 0 ms 40. 0 ms
13 66.187.178.58 (66.187.178.58) 40. 0 ms 40. 0 ms 40. 0 ms
14 206.132.254.42 (206.132.254.42) 40. 0 ms 50. 0 ms 40. 0 ms
Traceroute Complete.

---

I'm a Prefectionist ;)

If Mark has no problems with AT&T DSL, my problem must be with Road Runner. I still get hung up on the same address.

Tracing route to lunatics.kwsn.net [206.132.254.42]
over a maximum of 30 hops:
0 [192.168.0.100]
1 192.168.0.1
2 76.51.128.1
3 gig-5-0.gnbywi2-rtr1.new.rr.com [24.164.241.17]
4 so0-1-1.cgchill3-rtr1.kc.rr.com [24.94.160.29]
5 ae-5-0.cr0.chi30.tbone.rr.com [66.109.6.112]
6 ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
7 66.109.9.202
8 64.209.102.222<--------This one here
9 * * *
Can You get to My website that's in My sig John?

Yes, I can, but still can't get to any part of the lunatics of kwsn site.

---

Clk2HlpSetiCty:::PayIt4ward

traceroute to lunatics.kwsn.net (206.132.254.42), 64 hops max, 40 byte packets
1 192.168.254.254 (192.168.254.254) 14.444 ms * *
2 74-47-96-1.dr02.kgmn.az.frontiernet.net (74.47.96.1) 30.031 ms 11.754 ms 14.854 ms
3 74.40.5.1 (74.40.5.1) 23.583 ms * *
4 * so-0-0-0--0.cr02.plal.ca.frontiernet.net (74.40.4.9) 57.856 ms 42.187 ms
5 so-7-0-0--0.br01.plal.ca.frontiernet.net (74.40.3.170) 43.244 ms 41.583 ms 47.854 ms
6 208.49.158.141 (208.49.158.141) 42.864 ms 42.789 ms 42.311 ms
7 64.209.99.54 (64.209.99.54) 102.851 ms * 101.399 ms
8 xconn.core2-edge1.atl.oneringnetworks.net (66.187.176.5) 103.986 ms 100.114 ms 104.124 ms
9 xconn.dktc-56m.atl.oneringnetworks.net (66.187.178.58) 101.963 ms 101.261 ms 110.885 ms
10 beat42.gzz.cyb.cream.spectacularrebeats.net (206.132.254.42) 102.778 ms 105.284 ms 109.238 ms

---

It's not a permanent solution, but if you really need your lunatics fix, you might try using Tor. http://www.torproject.org/ It'll be slow, but it should get you around the bad route.

---

Well my bet is still on Global Crossing being at fault. It looks like everyone who CAN get to the site does not go through any Global Crossing IPs. There is nothing you can do about this. It just depends on who your ISP peers with and how routes are decided. Proxies or tor will be the only way to get to lunatics until GC notices and fixes their problem. I tried sending them an email but of course they only read email that is part of an existing helpdesk ticket so that went nowhere.

---

A member of The Knights Who Say NI!
For rankings, history graphs and more, check out:
My BOINC stats site

Well my bet is still on Global Crossing being at fault. It looks like everyone who CAN get to the site does not go through any Global Crossing IPs. There is nothing you can do about this. It just depends on who your ISP peers with and how routes are decided. Proxies or tor will be the only way to get to lunatics until GC notices and fixes their problem. I tried sending them an email but of course they only read email that is part of an existing helpdesk ticket so that went nowhere.

I didn't know how to copy my trace but from Seattle I did not go thru Global Crossing.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Well my bet is still on Global Crossing being at fault. It looks like everyone who CAN get to the site does not go through any Global Crossing IPs. There is nothing you can do about this. It just depends on who your ISP peers with and how routes are decided. Proxies or tor will be the only way to get to lunatics until GC notices and fixes their problem. I tried sending them an email but of course they only read email that is part of an existing helpdesk ticket so that went nowhere.

I didn't know how to copy my trace but from Seattle I did not go thru Global Crossing.

Assuming you're in Windows, right click in the command prompt window where you did the trace and click "Mark." Then use your mouse to highlight the trace. While the text is still highlighted, hit the enter key. That will put the trace into you clipboard, which you can then paste here.

---

that worked...

Tracing route to lunatics.kwsn.net [206.132.254.42]
over a maximum of 30 hops:

1 * * * Request timed out.
2 43 ms 42 ms 42 ms tukw-dsl-gw24-216.tukw.qwest.net [63.231.10.216]

3 42 ms 41 ms 42 ms tukw-agw1.inet.qwest.net [71.217.184.185]
4 42 ms 42 ms 41 ms sea-core-01.inet.qwest.net [67.14.1.194]
5 42 ms 42 ms 42 ms sea-brdr-01.inet.qwest.net [205.171.26.82]
6 43 ms 43 ms 43 ms bpr3-so-2-0-0.seattleswitchdesign.savvis.net [20
8.173.49.1]
7 45 ms 49 ms 51 ms cr1-pos-0-3-0-1.Seattle.savvis.net [208.172.83.6
2]
8 120 ms 120 ms 119 ms cr2-pos-0-0-0-0.Atlanta.savvis.net [204.70.192.6
9]
9 122 ms 126 ms 122 ms msr1-te-0-0-0-0.atlantapaix.savvis.net [204.70.2
00.1]
10 119 ms 119 ms 119 ms 204.70.203.98
11 121 ms 120 ms 121 ms 216.89.82.78
12 119 ms 119 ms 119 ms xconn.core2-edge1.atl.oneringnetworks.net [66.18
7.176.5]
13 121 ms 122 ms 121 ms xconn.dktc-56m.atl.oneringnetworks.net [66.187.1
78.58]
14 120 ms 120 ms 120 ms beat42.gzz.cyb.cream.spectacularrebeats.net [206
.132.254.42]

Trace complete.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

that worked...

Tracing route to lunatics.kwsn.net [206.132.254.42]
over a maximum of 30 hops:

1 * * * Request timed out.
2 43 ms 42 ms 42 ms tukw-dsl-gw24-216.tukw.qwest.net [63.231.10.216]

3 42 ms 41 ms 42 ms tukw-agw1.inet.qwest.net [71.217.184.185]
4 42 ms 42 ms 41 ms sea-core-01.inet.qwest.net [67.14.1.194]
5 42 ms 42 ms 42 ms sea-brdr-01.inet.qwest.net [205.171.26.82]
6 43 ms 43 ms 43 ms bpr3-so-2-0-0.seattleswitchdesign.savvis.net [20
8.173.49.1]
7 45 ms 49 ms 51 ms cr1-pos-0-3-0-1.Seattle.savvis.net [208.172.83.6
2]
8 120 ms 120 ms 119 ms cr2-pos-0-0-0-0.Atlanta.savvis.net [204.70.192.6
9]
9 122 ms 126 ms 122 ms msr1-te-0-0-0-0.atlantapaix.savvis.net [204.70.2
00.1]
10 119 ms 119 ms 119 ms 204.70.203.98
11 121 ms 120 ms 121 ms 216.89.82.78
12 119 ms 119 ms 119 ms xconn.core2-edge1.atl.oneringnetworks.net [66.18
7.176.5]
13 121 ms 122 ms 121 ms xconn.dktc-56m.atl.oneringnetworks.net [66.187.1
78.58]
14 120 ms 120 ms 120 ms beat42.gzz.cyb.cream.spectacularrebeats.net [206
.132.254.42]

Trace complete.

So you're having no trouble getting to lunatics?

---

that worked...

Tracing route to lunatics.kwsn.net [206.132.254.42]
over a maximum of 30 hops:

1 * * * Request timed out.
2 43 ms 42 ms 42 ms tukw-dsl-gw24-216.tukw.qwest.net [63.231.10.216]

3 42 ms 41 ms 42 ms tukw-agw1.inet.qwest.net [71.217.184.185]
4 42 ms 42 ms 41 ms sea-core-01.inet.qwest.net [67.14.1.194]
5 42 ms 42 ms 42 ms sea-brdr-01.inet.qwest.net [205.171.26.82]
6 43 ms 43 ms 43 ms bpr3-so-2-0-0.seattleswitchdesign.savvis.net [20
8.173.49.1]
7 45 ms 49 ms 51 ms cr1-pos-0-3-0-1.Seattle.savvis.net [208.172.83.6
2]
8 120 ms 120 ms 119 ms cr2-pos-0-0-0-0.Atlanta.savvis.net [204.70.192.6
9]
9 122 ms 126 ms 122 ms msr1-te-0-0-0-0.atlantapaix.savvis.net [204.70.2
00.1]
10 119 ms 119 ms 119 ms 204.70.203.98
11 121 ms 120 ms 121 ms 216.89.82.78
12 119 ms 119 ms 119 ms xconn.core2-edge1.atl.oneringnetworks.net [66.18
7.176.5]
13 121 ms 122 ms 121 ms xconn.dktc-56m.atl.oneringnetworks.net [66.187.1
78.58]
14 120 ms 120 ms 120 ms beat42.gzz.cyb.cream.spectacularrebeats.net [206
.132.254.42]

Trace complete.

So you're having no trouble getting to lunatics?

None at all, have been all around the site to see.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

I'm having trouble getting to the site too.

Ever since May 1st, I havent been able to connect.

Being part of the prerelease testing community, this is annoying to say the least, would like to take part in the testing of SSE2 and so on.

Tracert:

Sporer rute til lunatics.kwsn.net [206.132.254.42]
over et maksimum af 30 hop:

1 1 ms <1 ms <1 ms 172.26.1.1
2 18 ms * * loop0.mxc1-kolx.ip.cybercity.dk [212.242.2.164]
3 19 ms 20 ms 19 ms ge-0-1-6-10.mcr1-arhx.ip.cybercity.dk [212.242.8.53]
4 21 ms 21 ms 47 ms ge-0-0-0.mcr1-aalx.ip.cybercity.dk [212.242.6.13]
5 26 ms 52 ms 26 ms ge-1-0-0.mcr1-soex.ip.cybercity.dk [212.242.6.17]
6 26 ms 26 ms 26 ms ge-0-0-0.br1-soex.ip.cybercity.dk [212.242.6.30]
7 205 ms 220 ms 207 ms te1-3.ar3.CPH1.gblx.net [64.215.27.125]
8 121 ms 121 ms 124 ms 64.209.102.222
9 * * * Anmodning fik timeout.

Looks like it dies at 64.209.102.222, as someone else have pointed out.

---

@Any who want to reach Lunatics but cannot:
You should be able to bypass your ISP by using an anonymous proxy server. Simply create and use a shortcut/favorite using the
following URL:

https://proxify.com/u?lunatics.kwsn.net/index.php

This is a free web-based proxy service. There are many other servers you could use but this one works for me albeit s.l.o.w.l.y and with advertisements added for flavor. But it does work.

Much more info on proxies can be found at http://proxy.org

[EDIT] OOPS, well it does work for reading the site but I now find that I cannot login unless I buy the service. Darn, back to square one. [/EDIT]

[EDIT2] DO NOT use the link I provided earlier. I now find that I cannot ping ANY server, even microsoft.com, even after booting. I'm still investigating. FREE means you get what you pay for.[EDIT]

[FINAL UPDATE] This may be a Verizon thing. Other computers on my lan cannot ping any outside server either although they can ping each other. Using the proxy does work for reaching Lunatics for reading only unless you want to pay $40 for a 6 month subscription in which case you should be able to logon too. No thanks. It works but use with caution.

OK.

Using freeproxyserver.net, I have been able to get to lunatics, and even log in.

It runs fairly quick, so this solution will have to do for now.

---

. .. had a 'single' problem yesterday geting there - but no problems lately

> using TW/RR - used trace (idserve) earlier:

Apache/1.3.34 Ben-SSL/1.57(Unix) PHP/4.4.3 - lunatics.kwsn.net - 206.132.254.42

---

BOINC Wiki . . .

Science Status Page . . .