...
@ Dr. CETI: I think they were looking for successful trace routes to the Coop. ;-)

Alinator

Actually, I read it as a request for trace routes to the two e-commerce sites in the top line of the quote.

Which is very odd. Neither site was accessible two days ago, but I can view them fine in my browser now. Tracert dies, having crossed the atlantic and then come back again:

Tracing route to axpertec.com [216.59.158.180]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  my.router [www.xxx.yyy.zzz]
  2    20 ms    20 ms    20 ms  esr9.manchester6.broadband.bt.net [217.47.158.140]
  3    29 ms    21 ms    23 ms  217.47.158.13
  4    21 ms    22 ms    21 ms  212.140.206.9
  5    22 ms    20 ms    20 ms  217.41.173.114
  6    22 ms    20 ms    22 ms  217.41.173.42
  7    21 ms    21 ms    20 ms  217.47.204.177
  8    21 ms    21 ms    20 ms  core2-pos3-1.manchester.ukcore.bt.net [194.72.2.241]
  9    28 ms    26 ms    26 ms  core2-pos3-1.manchester.ukcore.bt.net [62.6.200.105]
 10    26 ms    26 ms    25 ms  core2-pos3-1.manchester.ukcore.bt.net [62.6.200.106]
 11    26 ms    25 ms    26 ms  t2c1-ge8-0-0.uk-eal.eu.bt.net [166.49.168.17]
 12    26 ms    27 ms    26 ms  t2c2-p3-1.uk-lon1.eu.bt.net [166.49.208.110]
 13    25 ms    37 ms    27 ms  t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.110]
 14    28 ms    26 ms    27 ms  195.66.224.130
 15    28 ms    27 ms    27 ms  core2-pos3-1.manchester.ukcore.bt.net [71.5.174.133]
 16   100 ms   100 ms   101 ms  p1-0-0d0.rar1.nyc-ny.us.xo.net [65.106.0.118]
 17   125 ms   135 ms   153 ms  p6-0-0.rar2.chicago-il.us.xo.net [65.106.0.29]
 18   152 ms   151 ms   151 ms  p1-0-0.RAR1.Dallas-TX.us.xo.net [65.106.0.34]
 19   178 ms   178 ms   178 ms  p6-0-0.rar2.la-ca.us.xo.net [65.106.0.14]
 20   184 ms   184 ms   185 ms  p0-0-0.MAR2.LA-CA.us.xo.net [65.106.5.10]
 21   177 ms   177 ms   178 ms  core2-pos3-1.manchester.ukcore.bt.net [207.88.81.170]
 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.

and

Tracing route to xionusa.com [216.59.158.181]
over a maximum of 30 hops:

  1    20 ms    <1 ms    <1 ms  my.router [www.xxx.yyy.zzz]
  2    20 ms    20 ms    21 ms  esr9.manchester6.broadband.bt.net [217.47.158.140]
  3    21 ms    20 ms    21 ms  217.47.158.13
  4    21 ms    20 ms    21 ms  212.140.206.9
  5    22 ms    21 ms    21 ms  217.41.173.114
  6    21 ms    21 ms    20 ms  212.140.206.42
  7    23 ms    20 ms    21 ms  217.47.158.35
  8    22 ms    20 ms    21 ms  core2-pos3-1.manchester.ukcore.bt.net [194.72.2.45]
  9    28 ms    27 ms    27 ms  core2-pos3-1.manchester.ukcore.bt.net [194.72.17.121]
 10    26 ms    27 ms    27 ms  core2-pos3-1.manchester.ukcore.bt.net [194.72.17.122]
 11    25 ms    26 ms    27 ms  t2c1-ge14-0-0.uk-eal.eu.bt.net [166.49.168.25]
 12    26 ms    26 ms    27 ms  t2c2-p3-2.uk-lon1.eu.bt.net [166.49.164.138]
 13    26 ms    28 ms    27 ms  t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.110]
 14    27 ms    27 ms    27 ms  195.66.224.130
 15    32 ms    28 ms    29 ms  core2-pos3-1.manchester.ukcore.bt.net [71.5.174.133]
 16   101 ms   100 ms   126 ms  p1-0-0d0.rar1.nyc-ny.us.xo.net [65.106.0.118]
 17   126 ms   126 ms   125 ms  p6-0-0.rar2.chicago-il.us.xo.net [65.106.0.29]
 18   153 ms   152 ms   152 ms  p1-0-0.RAR1.Dallas-TX.us.xo.net [65.106.0.34]
 19   179 ms   179 ms   180 ms  p6-0-0.rar2.la-ca.us.xo.net [65.106.0.14]
 20   183 ms   185 ms   185 ms  p0-0-0.MAR2.LA-CA.us.xo.net [65.106.5.10]
 21   178 ms   180 ms   178 ms  core2-pos3-1.manchester.ukcore.bt.net [207.88.81.170]
 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.

...
@ Dr. CETI: I think they were looking for successful trace routes to the Coop. ;-)

Alinator

Actually, I read it as a request for trace routes to the two e-commerce sites in the top line of the quote.

Which is very odd. Neither site was accessible two days ago, but I can view them fine in my browser now. Tracert dies, having crossed the atlantic and then come back again:

<snip trace route>

Yep, I suppose that's one way to look at the request. However neither of those sites route through GC from my end. So I wasn't too surprised they went through for me since they are hosted on GUS Networks.

Another point here which is germane is it looks to me that GUS is a Tier 3 provider. So even thought they are dropping ICMP at the border (Which is a really poor policy for any ISP, IMHO) I suppose I can understand it since they have to pay for transit on all traffic.

GC, OTOH is a Tier 1 so they don't have that excuse.

So relating that to the case of the case of the Coop's problems, failure to hit them was probably coincidence. The part I don't really understand is that when I do a DNS lookup for the Coop I get a GC IP address, but when I do a RDNS lookup of the Coop's IP (or KWSN for that matter) I'm getting a non valid domain name returned.

Alinator

Hi,
thank's for your help. The two sites www.xionusa.com and www.axpertec.com are accessible for me now.
But lunatics http://lunatics.kwsn.net/index.php is still always dead...;-(

heinz

no problems reaching lunatics here in germany.

tracert lunatics.kwsn.net
traceroute to lunatics.kwsn.net (206.132.254.42), 30 hops max, 40 byte packets
 1  192.168.16.254 (192.168.16.254)  0.559 ms  0.844 ms *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * ffm-bb2-link.telia.net (80.91.251.158)  48.329 ms ffm-bb1-link.telia.net (80.91.254.162)  50.948 ms
 7  prs-bb1-link.telia.net (80.91.254.205)  98.806 ms prs-bb1-link.telia.net (80.91.248.69)  101.220 ms prs-bb1-link.telia.net (80.91.254.205)  104.087 ms
 8  ash-bb1-link.telia.net (80.91.251.98)  186.127 ms ash-bb1-link.telia.net (80.91.252.36)  157.358 ms ash-bb2-link.telia.net (80.91.251.102)  160.665 ms
 9  atl-bb1-link.telia.net (213.248.80.142)  175.425 ms atl-bb1-link.telia.net (80.91.252.122)  180.545 ms *
10  * * *
11  * * xconn.core2-edge1.atl.oneringnetworks.net (66.187.176.5)  150.931 ms
12  xconn.dktc-56m.atl.oneringnetworks.net (66.187.178.58)  153.860 ms  152.404 ms  152.339 ms
13  beat42.gzz.cyb.cream.spectacularrebeats.net (206.132.254.42)  153.377 ms  155.923 ms  160.528 ms

---

mic.

Anyone been able to access Lunatics today?
Servers down?

I'm getting a server connection error.

---

Anyone been able to access Lunatics today?
Servers down?

I'm getting a server connection error.

Just checked and it worked for me...

---

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

Anyone been able to access Lunatics today?
Servers down?

I'm getting a server connection error.

Earlier today I received 5 update notifications for the same update to the Windows thread and assumed something was bouncing. I can reach them now however.
[edit]. . .however I still have to use the $&#@$* proxy method to do so.[/edit]

Anyone been able to access Lunatics today?
Servers down?

I'm getting a server connection error.

Earlier today I received 5 update notifications for the same update to the Windows thread and assumed something was bouncing. I can reach them now however.
[edit]. . .however I still have to use the $&#@$* proxy method to do so.[/edit]

No trouble logging in @ 'Lunatics', as i speak.
Holland, a very little town, Zutphen.

---

I still can't reach the site directly, though I can via proxy.
Strange.

Pings & tracert don't complete.

Everything was groovy until this AM.

ISP (sprint) says they don't block & they are at a loss as well.

---

Works nicely from Telia ISP in Sweden, but not from tmnet..

Telia:

1 1 ms <10 ms <10 ms 192.168.1.1
2 7 ms 6 ms 6 ms gw1-no126.tbcn.telia.com [90.228.224.1]
3 56 ms 8 ms 9 ms s-bb2-link.telia.net [80.91.254.114]
4 18 ms 18 ms 24 ms kbn-bb2-pos0-0-0.telia.net [213.248.65.29]
5 97 ms 97 ms 97 ms nyk-bb2-link.telia.net [213.248.82.101]
6 104 ms 104 ms 103 ms ash-bb1-link.telia.net [80.91.250.17]
7 123 ms 118 ms 117 ms atl-bb1-link.telia.net [80.91.248.137]
8 118 ms 117 ms 116 ms wbs-116420-atl-bb1.c.telia.net [213.248.90.106]

9 124 ms 124 ms 124 ms xconn.core2-edge1.atl.oneringnetworks.net [66.18
7.176.5]
10 123 ms 116 ms 117 ms xconn.dktc-56m.atl.oneringnetworks.net [66.187.1
78.58]
11 120 ms 134 ms 120 ms beat42.gzz.cyb.cream.spectacularrebeats.net [206
.132.254.42]

Trace Complete

Tmnet:

1 <10 ms <10 ms <10 ms 192.168.0.51
2 1 ms 2 ms 1 ms tmnet.se [84.243.52.250]
3 11 ms 11 ms 12 ms crtr-7801-labs2-lin.tmnet.se [84.243.30.157]
4 11 ms 12 ms 11 ms ertr-limhamn.Labs2.se [84.243.30.130]
5 19 ms 18 ms 19 ms cr-se-sto-ksg23-1-vl1001-10ge.skycom.se [82.209.
176.38]
6 23 ms 22 ms 23 ms 64.210.13.73
7 114 ms 115 ms 114 ms 64.209.102.222
8 * * * Begäran gjorde timeout.
9 * * * Begäran gjorde timeout.
10 * * * Begäran gjorde timeout.
11 * * * Begäran gjorde timeout.
12 * * * Begäran gjorde timeout.
13 * * * Begäran gjorde timeout.

Wonder if some isp's have their routes shutdown to that ISP?

Kind Regards
Vyper

---

_________________________________________________________________________
Addicted to SETI crunching!
Founder of GPU Users Group

Wonder if some isp's have their routes shutdown to that ISP?

Kind Regards
Vyper

Do I recall from a long time ago...Simon having said something about the site being hacked/attacked and being shut down as a spammer?
Might this have something to do with it?
Might check for it on spamlists.........just a thought.

---

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

Wonder if some isp's have their routes shutdown to that ISP?

Kind Regards
Vyper

Do I recall from a long time ago...Simon having said something about the site being hacked/attacked and being shut down as a spammer?
Might this have something to do with it?
Might check for it on spamlists.........just a thought.

I called Road Runner here in Green Bay, and they told me to contact Global Crossing, since the problem is off of RR's network. This is the response I got from GC:

Looks like we hand that off to WBS directly off ar3.dca3. (Noting that the IP before the last hop is our router: " te1-1-10g.ar3.DCA3.gblx.net (67.17.108.134)". The next one, while assigned to us at the top level, has been assigned by us to our customer, WBS.) He should contact them, though we can't give out our customer contact info.



Also note that it does work when connecting via Phoenix (which routes through ar1.ATL2 rather than ar3.DCA3).

I asked if this is WBS Connect and the reponse was this:

I asked Security, and this is what they said “possibly. it's going to be whoever their (kwsn.net's) hosting provider is

he should work his way up the chain from there.”

Toby...I had PMed you from Rosetta about this yesterday. Maybe this will help tracking down the offending router that is blocking access. I think I have done all that I can for now...

---

Clk2HlpSetiCty:::PayIt4ward

Hi all,
http://lunatics.kwsn.net/index.php
is from France(Strasbourg) not connectable since I opened this thread,
slowly I believe that it will never came back, because the providers are in a struggle with each other...

heinz

Hi all,
http://lunatics.kwsn.net/index.php
is from France(Strasbourg) not connectable since I opened this thread,
slowly I believe that it will never came back, because the providers are in a struggle with each other...

heinz

Heinz...do a tracert from your location, if you haven't, and post the results. Does it fail at the same IP that everyone else that is having problems with?

Jon

---

Clk2HlpSetiCty:::PayIt4ward

Hi, here is the tracert
------------------------------
C:\\Dokumente und Einstellungen\\heinz>tracert lunatics.kwsn.net

Routenverfolgung zu lunatics.kwsn.net [206.132.254.42] über maximal 30 Abschnit
te:

1 3134 ms 1 ms 1 ms 192.168.0.1
2 36 ms 39 ms 39 ms AStrasbourg-156-1-64-1.w81-51.abo.wanadoo.fr [81
.51.87.1]
3 38 ms 35 ms 39 ms 10.224.13.1
4 40 ms 63 ms 39 ms ge-3-2-0-0.nrstr101.Schiltigheim.francetelecom.n
et [193.252.160.78]
5 42 ms 39 ms 39 ms 193.252.100.150
6 39 ms 39 ms 39 ms tengige0-0-0-4.ffttr1.FrankfurtAmMain.opentransi
t.net [193.251.242.190]
7 54 ms 39 ms 47 ms 64.208.110.225
8 132 ms 131 ms 131 ms 64.209.102.222
9 * * * Zeitüberschreitung der Anforderung.
10 * * * Zeitüberschreitung der Anforderung.
11 * * * Zeitüberschreitung der Anforderung.
12 * * * Zeitüberschreitung der Anforderung.
13 * * * Zeitüberschreitung der Anforderung.
14 * * * Zeitüberschreitung der Anforderung.
15 * * * Zeitüberschreitung der Anforderung.
16 * * * Zeitüberschreitung der Anforderung.
17 * * * Zeitüberschreitung der Anforderung.
18 * * * Zeitüberschreitung der Anforderung.
19 * * * Zeitüberschreitung der Anforderung.
20 * * * Zeitüberschreitung der Anforderung.
21 * ^C
C:\\Dokumente und Einstellungen\\heinz>
9 to 20 means timeout

heinz

Hi, here is the tracert
------------------------------
C:\\Dokumente und Einstellungen\\heinz>tracert lunatics.kwsn.net

Routenverfolgung zu lunatics.kwsn.net [206.132.254.42] über maximal 30 Abschnit
te:

1 3134 ms 1 ms 1 ms 192.168.0.1
2 36 ms 39 ms 39 ms AStrasbourg-156-1-64-1.w81-51.abo.wanadoo.fr [81
.51.87.1]
3 38 ms 35 ms 39 ms 10.224.13.1
4 40 ms 63 ms 39 ms ge-3-2-0-0.nrstr101.Schiltigheim.francetelecom.n
et [193.252.160.78]
5 42 ms 39 ms 39 ms 193.252.100.150
6 39 ms 39 ms 39 ms tengige0-0-0-4.ffttr1.FrankfurtAmMain.opentransi
t.net [193.251.242.190]
7 54 ms 39 ms 47 ms 64.208.110.225
8 132 ms 131 ms 131 ms 64.209.102.222
9 * * * Zeitüberschreitung der Anforderung.
10 * * * Zeitüberschreitung der Anforderung.
11 * * * Zeitüberschreitung der Anforderung.
12 * * * Zeitüberschreitung der Anforderung.
13 * * * Zeitüberschreitung der Anforderung.
14 * * * Zeitüberschreitung der Anforderung.
15 * * * Zeitüberschreitung der Anforderung.
16 * * * Zeitüberschreitung der Anforderung.
17 * * * Zeitüberschreitung der Anforderung.
18 * * * Zeitüberschreitung der Anforderung.
19 * * * Zeitüberschreitung der Anforderung.
20 * * * Zeitüberschreitung der Anforderung.
21 * ^C
C:\\Dokumente und Einstellungen\\heinz>
9 to 20 means timeout

heinz

Yep...same IP.

---

Clk2HlpSetiCty:::PayIt4ward

Yep...same IP.

So who the heck controls that IP addy??

64.209.102.222

---

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

Yep...same IP.

So who the heck controls that IP addy??

64.209.102.222

Whois shows:

OrgName: Global Crossing
OrgID: GBLX
Address: 14605 South 50th Street
City: Phoenix
StateProv: AZ
PostalCode: 85044-6471
Country: US

[ ... Global (except Lunatics) Crossing... ? ;D ]

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

BTW @ Heinz .... Building a server aren't you ? run a dns thingamybob on it and you'll probably be able to get to Lunatics again ....

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Yep...same IP.

So who the heck controls that IP addy??

64.209.102.222

As I said before, GC is assigned the IP at the top level, from their customer, WBS. See here.

Toby is going to have to take this up with whomever is hosting the site.

---

Clk2HlpSetiCty:::PayIt4ward