From Indianapolis, IN, my laptop which is currently connected through at least one extra jump:
Microsoft® Windows DOS
©Copyright Microsoft Corp 1990-2001.
tracert tigereye.ca
Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms home [192.168.1.254]
2 13 ms 13 ms 13 ms adsl-75-2-47-254.dsl.ipltin.sbcglobal.net [75.2.
47.254]
3 13 ms 15 ms 15 ms dist1-vlan50.ipltin.ameritech.net [67.36.128.226
]
4 17 ms 14 ms 15 ms bb1-g8-0.ipltin.sbcglobal.net [151.164.241.196]
5 27 ms 27 ms 29 ms bb1-p6-5.emhril.sbcglobal.net [151.164.93.123]
6 28 ms 27 ms 27 ms bb2-p13-1.emhril.ameritech.net [151.164.191.114]
7 30 ms 29 ms 29 ms 151.164.94.41
8 28 ms 29 ms 29 ms asn6543-teleglobe.eqchil.sbcglobal.net [151.164.
250.18]
9 43 ms 44 ms 45 ms if-1-0.mcore3.TTT-Scarborough.teleglobe.net [66.
110.14.10]
10 44 ms 45 ms 44 ms if-10-0.core2.TTT-Scarborough.Teleglobe.net [207
.45.198.17]
11 43 ms 45 ms 45 ms if-5-0.core1.TNK-Toronto.Teleglobe.net [207.45.1
98.10]
12 45 ms 44 ms 45 ms ix-1-151.core1.TNK-Toronto.teleglobe.net [216.6.
112.22]
13 45 ms 45 ms 45 ms mail.initechcomputers.com [204.14.17.162]
Trace complete.
Possible New (FAST!) Server?
-
Duckwarrior
- Posts: 1967
- Joined: Thu Jul 03, 2003 7:00 am
- Location: la Grande-Bretagne
BV you old scoundrel, I thought you were a mortgage broker and all this time you are Ron Jeremy.BlackViper wrote:QUOTE (BlackViper @ Jan 22 2007, 06:15 PM) Work, wireless network behind a firewall. I will post home later tonight
Code: Select all
Execute Porn -IIa.exe /p
P.S. Do you need a cameraman?
Last edited by Duckwarrior on Mon Jan 22, 2007 7:56 pm, edited 1 time in total.
Those who make peaceful revolution impossible, will make violent revolution inevitable. John F. Kennedy.
CODE>tracert tigereye.ca
Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms we250a.halls.manchester.ac.uk [130.88.183.250]
2 16 ms 16 ms 16 ms gw-uom.mcc.ac.uk [130.88.250.54]
3 23 ms 26 ms 19 ms gw-man.netnw.net.uk [194.66.21.242]
4 9 ms 7 ms 7 ms gw-nnw.core.netnw.net.uk [194.66.25.97]
5 9 ms 7 ms 7 ms gw-man-rh.netnw.net.uk [194.66.25.149]
6 10 ms 10 ms 11 ms so-0-1-0.warr-sbr1.ja.net [146.97.42.169]
7 50 ms 30 ms 24 ms so-0-2-0.read-sbr1.ja.net [146.97.33.109]
8 17 ms 18 ms 18 ms lond-scr3.ja.net [146.97.33.142]
9 19 ms 16 ms 14 ms po1-0.int-gw2.ja.net [146.97.35.138]
10 13 ms 15 ms 16 ms sl-gw11-lon-2-0.sprintlink.net [82.195.189.157]
11 22 ms 19 ms 17 ms sl-bb21-lon-11-0.sprintlink.net [213.206.128.58]
12 18 ms 19 ms 18 ms sl-bb22-lon-3-0.sprintlink.net [213.206.129.153]
13 17 ms 15 ms 17 ms 62.156.139.141
14 106 ms 107 ms * yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201]
15 * 107 ms 122 ms 217.6.24.194
16 107 ms 109 ms 132 ms mail.initechcomputers.com [204.14.17.162]
Trace complete.
>tracert tigereye.ca
Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms we250a.halls.manchester.ac.uk [130.88.183.250]
2 17 ms 16 ms 16 ms gw-uom.mcc.ac.uk [130.88.250.54]
3 12 ms 12 ms 11 ms gw-man.netnw.net.uk [194.66.21.242]
4 14 ms 11 ms 11 ms gw-nnw.core.netnw.net.uk [194.66.25.97]
5 32 ms 36 ms 27 ms gw-man-rh.netnw.net.uk [194.66.25.149]
6 11 ms 10 ms 11 ms so-0-1-0.warr-sbr1.ja.net [146.97.42.169]
7 5 ms 5 ms 5 ms so-0-2-0.read-sbr1.ja.net [146.97.33.109]
8 14 ms 14 ms 15 ms lond-scr3.ja.net [146.97.33.142]
9 12 ms 13 ms 13 ms po1-0.int-gw2.ja.net [146.97.35.138]
10 9 ms 9 ms 10 ms sl-gw11-lon-2-0.sprintlink.net [82.195.189.157]
11 8 ms 6 ms 7 ms sl-bb21-lon-11-0.sprintlink.net [213.206.128.58]
12 7 ms 6 ms 7 ms sl-bb22-lon-3-0.sprintlink.net [213.206.129.153]
13 6 ms 6 ms 6 ms 62.156.139.141
14 109 ms 106 ms 100 ms yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201]
15 105 ms 102 ms 106 ms 217.6.24.194
16 117 ms 110 ms 108 ms mail.initechcomputers.com [204.14.17.162]
Trace complete.
>ping tigereye.ca
Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:
Reply from 204.14.17.162: bytes=32 time=124ms TTL=48
Request timed out.
Reply from 204.14.17.162: bytes=32 time=122ms TTL=48
Reply from 204.14.17.162: bytes=32 time=106ms TTL=48
Ping statistics for 204.14.17.162:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 106ms, Maximum = 124ms, Average = 117ms
>ping tigereye.ca
Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:
Reply from 204.14.17.162: bytes=32 time=103ms TTL=48
Reply from 204.14.17.162: bytes=32 time=114ms TTL=48
Reply from 204.14.17.162: bytes=32 time=96ms TTL=48
Reply from 204.14.17.162: bytes=32 time=115ms TTL=48
Ping statistics for 204.14.17.162:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 96ms, Maximum = 115ms, Average = 107ms
>ping tigereye.ca -n 10
Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:
Reply from 204.14.17.162: bytes=32 time=104ms TTL=48
Reply from 204.14.17.162: bytes=32 time=106ms TTL=48
Reply from 204.14.17.162: bytes=32 time=123ms TTL=48
Reply from 204.14.17.162: bytes=32 time=108ms TTL=48
Reply from 204.14.17.162: bytes=32 time=112ms TTL=48
Reply from 204.14.17.162: bytes=32 time=98ms TTL=48
Reply from 204.14.17.162: bytes=32 time=108ms TTL=48
Reply from 204.14.17.162: bytes=32 time=105ms TTL=48
Reply from 204.14.17.162: bytes=32 time=106ms TTL=48
Reply from 204.14.17.162: bytes=32 time=113ms TTL=48
Ping statistics for 204.14.17.162:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 98ms, Maximum = 123ms, Average = 108ms
>ping tigereye.ca -n 10 -l 1500
Pinging tigereye.ca [204.14.17.162] with 1500 bytes of data:
Reply from 204.14.17.162: bytes=1500 time=116ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=120ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=104ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=111ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=111ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=114ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=112ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=111ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=110ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=117ms TTL=48
Ping statistics for 204.14.17.162:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 104ms, Maximum = 120ms, Average = 112ms
>
my firewall decided to break one of the pings, it decided it was ok for the ping program to send pings after it already had sent a few.
Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms we250a.halls.manchester.ac.uk [130.88.183.250]
2 16 ms 16 ms 16 ms gw-uom.mcc.ac.uk [130.88.250.54]
3 23 ms 26 ms 19 ms gw-man.netnw.net.uk [194.66.21.242]
4 9 ms 7 ms 7 ms gw-nnw.core.netnw.net.uk [194.66.25.97]
5 9 ms 7 ms 7 ms gw-man-rh.netnw.net.uk [194.66.25.149]
6 10 ms 10 ms 11 ms so-0-1-0.warr-sbr1.ja.net [146.97.42.169]
7 50 ms 30 ms 24 ms so-0-2-0.read-sbr1.ja.net [146.97.33.109]
8 17 ms 18 ms 18 ms lond-scr3.ja.net [146.97.33.142]
9 19 ms 16 ms 14 ms po1-0.int-gw2.ja.net [146.97.35.138]
10 13 ms 15 ms 16 ms sl-gw11-lon-2-0.sprintlink.net [82.195.189.157]
11 22 ms 19 ms 17 ms sl-bb21-lon-11-0.sprintlink.net [213.206.128.58]
12 18 ms 19 ms 18 ms sl-bb22-lon-3-0.sprintlink.net [213.206.129.153]
13 17 ms 15 ms 17 ms 62.156.139.141
14 106 ms 107 ms * yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201]
15 * 107 ms 122 ms 217.6.24.194
16 107 ms 109 ms 132 ms mail.initechcomputers.com [204.14.17.162]
Trace complete.
>tracert tigereye.ca
Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms we250a.halls.manchester.ac.uk [130.88.183.250]
2 17 ms 16 ms 16 ms gw-uom.mcc.ac.uk [130.88.250.54]
3 12 ms 12 ms 11 ms gw-man.netnw.net.uk [194.66.21.242]
4 14 ms 11 ms 11 ms gw-nnw.core.netnw.net.uk [194.66.25.97]
5 32 ms 36 ms 27 ms gw-man-rh.netnw.net.uk [194.66.25.149]
6 11 ms 10 ms 11 ms so-0-1-0.warr-sbr1.ja.net [146.97.42.169]
7 5 ms 5 ms 5 ms so-0-2-0.read-sbr1.ja.net [146.97.33.109]
8 14 ms 14 ms 15 ms lond-scr3.ja.net [146.97.33.142]
9 12 ms 13 ms 13 ms po1-0.int-gw2.ja.net [146.97.35.138]
10 9 ms 9 ms 10 ms sl-gw11-lon-2-0.sprintlink.net [82.195.189.157]
11 8 ms 6 ms 7 ms sl-bb21-lon-11-0.sprintlink.net [213.206.128.58]
12 7 ms 6 ms 7 ms sl-bb22-lon-3-0.sprintlink.net [213.206.129.153]
13 6 ms 6 ms 6 ms 62.156.139.141
14 109 ms 106 ms 100 ms yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201]
15 105 ms 102 ms 106 ms 217.6.24.194
16 117 ms 110 ms 108 ms mail.initechcomputers.com [204.14.17.162]
Trace complete.
>ping tigereye.ca
Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:
Reply from 204.14.17.162: bytes=32 time=124ms TTL=48
Request timed out.
Reply from 204.14.17.162: bytes=32 time=122ms TTL=48
Reply from 204.14.17.162: bytes=32 time=106ms TTL=48
Ping statistics for 204.14.17.162:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 106ms, Maximum = 124ms, Average = 117ms
>ping tigereye.ca
Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:
Reply from 204.14.17.162: bytes=32 time=103ms TTL=48
Reply from 204.14.17.162: bytes=32 time=114ms TTL=48
Reply from 204.14.17.162: bytes=32 time=96ms TTL=48
Reply from 204.14.17.162: bytes=32 time=115ms TTL=48
Ping statistics for 204.14.17.162:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 96ms, Maximum = 115ms, Average = 107ms
>ping tigereye.ca -n 10
Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:
Reply from 204.14.17.162: bytes=32 time=104ms TTL=48
Reply from 204.14.17.162: bytes=32 time=106ms TTL=48
Reply from 204.14.17.162: bytes=32 time=123ms TTL=48
Reply from 204.14.17.162: bytes=32 time=108ms TTL=48
Reply from 204.14.17.162: bytes=32 time=112ms TTL=48
Reply from 204.14.17.162: bytes=32 time=98ms TTL=48
Reply from 204.14.17.162: bytes=32 time=108ms TTL=48
Reply from 204.14.17.162: bytes=32 time=105ms TTL=48
Reply from 204.14.17.162: bytes=32 time=106ms TTL=48
Reply from 204.14.17.162: bytes=32 time=113ms TTL=48
Ping statistics for 204.14.17.162:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 98ms, Maximum = 123ms, Average = 108ms
>ping tigereye.ca -n 10 -l 1500
Pinging tigereye.ca [204.14.17.162] with 1500 bytes of data:
Reply from 204.14.17.162: bytes=1500 time=116ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=120ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=104ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=111ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=111ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=114ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=112ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=111ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=110ms TTL=48
Reply from 204.14.17.162: bytes=1500 time=117ms TTL=48
Ping statistics for 204.14.17.162:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 104ms, Maximum = 120ms, Average = 112ms
>
my firewall decided to break one of the pings, it decided it was ok for the ping program to send pings after it already had sent a few.
H:\Documents and Settings\Alleg_X>tracert tigereye.ca
Bezig met het traceren van de route naar tigereye.ca [204.14.17.162]
via maximaal 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.1
2 12 ms 8 ms 10 ms ubr33-bu3.dbsch1.nb.home.nl [10.193.0.1]
3 6 ms 5 ms 8 ms csw1-vlan201.dbsch1.nb.home.nl [213.51.152.193]
4 11 ms 10 ms 6 ms bb1-ge10-0-0.dbsch1.nb.home.nl [213.51.158.92]
5 15 ms 11 ms 8 ms bb2-ge0-1-0-0.amsix-telecity.home.nl [213.51.158
.155]
6 15 ms 11 ms 8 ms Essent.mpr1.if.ge-2-0-1.ams5.above.net [82.98.25
0.185]
7 20 ms 16 ms 15 ms dtag-gw.mpr1.ams5.nl.above.net [62.4.65.26]
8 119 ms 115 ms 125 ms yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201]
9 117 ms 121 ms 117 ms 217.6.24.194
10 123 ms 122 ms 116 ms mail.initechcomputers.com [204.14.17.162]
De trace is voltooid.
Bezig met het traceren van de route naar tigereye.ca [204.14.17.162]
via maximaal 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.1
2 12 ms 8 ms 10 ms ubr33-bu3.dbsch1.nb.home.nl [10.193.0.1]
3 6 ms 5 ms 8 ms csw1-vlan201.dbsch1.nb.home.nl [213.51.152.193]
4 11 ms 10 ms 6 ms bb1-ge10-0-0.dbsch1.nb.home.nl [213.51.158.92]
5 15 ms 11 ms 8 ms bb2-ge0-1-0-0.amsix-telecity.home.nl [213.51.158
.155]
6 15 ms 11 ms 8 ms Essent.mpr1.if.ge-2-0-1.ams5.above.net [82.98.25
0.185]
7 20 ms 16 ms 15 ms dtag-gw.mpr1.ams5.nl.above.net [62.4.65.26]
8 119 ms 115 ms 125 ms yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201]
9 117 ms 121 ms 117 ms 217.6.24.194
10 123 ms 122 ms 116 ms mail.initechcomputers.com [204.14.17.162]
De trace is voltooid.

So it seems like if I were to host an Allegiance server at this datacenter, it'd have some pretty good pingtimes from around the globe.
To be honest I was half-hoping the pingtimes would suck so that it would be a no-brainer: it's useless to pay for something that sucks.
But since it seems to be pretty good for everyone, I'll look into it.
Now I just need to do some financial shuffling to see if I can afford it for a length of time - it's not cheap. It is possible for me to get a "deal" if I can get a few more people to host servers at this center along with me - bulk rate... but I need to find them /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />
Out of curiosity - *IF* I were to ask a few people to donate every once and a while ($20 this month, $20 a few months from now, etc), how many people would be willing to do this?
In the end I may not need this - I may be able to do it on my own but I'm not sure. If at least 10 people are willing to pass me some cash over the next year, then I know I'll be able to do it for sure without juggling things.
If you haven't already, please post your PING and TRACERT results here so I can confirm that this is as good as it appears from the first batch of replies.
Also include if it's "better" "same" or "worse" than our current servers.
--TE
To be honest I was half-hoping the pingtimes would suck so that it would be a no-brainer: it's useless to pay for something that sucks.
But since it seems to be pretty good for everyone, I'll look into it.
Now I just need to do some financial shuffling to see if I can afford it for a length of time - it's not cheap. It is possible for me to get a "deal" if I can get a few more people to host servers at this center along with me - bulk rate... but I need to find them /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />
Out of curiosity - *IF* I were to ask a few people to donate every once and a while ($20 this month, $20 a few months from now, etc), how many people would be willing to do this?
In the end I may not need this - I may be able to do it on my own but I'm not sure. If at least 10 people are willing to pass me some cash over the next year, then I know I'll be able to do it for sure without juggling things.
If you haven't already, please post your PING and TRACERT results here so I can confirm that this is as good as it appears from the first batch of replies.
Also include if it's "better" "same" or "worse" than our current servers.
--TE
The Allegiance community currently hates their sysadmin because he is doing: [Too Much] [____________|] [Too Little]
Current reason: Removing the PayPal contribute page. Send Bitcoin instead: 1EccFi98tR5S9BYLuB61sFfxKqqgSKK8Yz. This scale updates regularly.
-
Elephanthead
- Posts: 211
- Joined: Sat Jul 05, 2003 7:00 am
Do we really need more servers? No reason to have 5 different people paying for 5 different servers when we only really use one or two. I am all for tiger spending money to provided me with free servers, but I might prefer he use it to buy software to make high res stuff I can run on the servers we already have, or bank the money and buy servers when the ones we have now disappear.
-
BlackViper
- Posts: 6993
- Joined: Thu Aug 07, 2003 7:00 am
- Location: Green Bay, WI
Just was wondering who would be the first to spot that /mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" /> Bored today, waiting on lender approvals for several appraisals.Duckwarrior wrote:QUOTE (Duckwarrior @ Jan 22 2007, 01:56 PM) BV you old scoundrel, I thought you were a mortgage broker and all this time you are Ron Jeremy.
P.S. Do you need a cameraman?
TE >$ here /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />
Always in the Shadows...
I'm just investigating here, I haven't made any decisions.Elephanthead wrote:QUOTE (Elephanthead @ Jan 22 2007, 03:58 PM) Do we really need more servers? No reason to have 5 different people paying for 5 different servers when we only really use one or two. I am all for tiger spending money to provided me with free servers, but I might prefer he use it to buy software to make high res stuff I can run on the servers we already have, or bank the money and buy servers when the ones we have now disappear.
The main reason why I'm investigating is because many have complained recently about lag/pingtimes/routes to the current servers. I regularly hear people say "I don't want to play on ThalServ - I lag there"
or: "I don't want to move to Planet - I lag there"
I'm investigating a new server to see if people will lag on a hypothetical TigerServ since a few friends of mine recently hooked up a VERY sweet 'net connection and I have the opportunity to host a 1U server there for ~$100CAD a month depending on bandwidth (if I buy/provide the server).
It may be too expensive to do, but it's an option. I threw up this topic to see if it'd even be worthwhile investigating - maybe it was just-as-fast as the current servers. From people's responses it appears to be faster, so I'm continuing my investigation.
--TE
The Allegiance community currently hates their sysadmin because he is doing: [Too Much] [____________|] [Too Little]
Current reason: Removing the PayPal contribute page. Send Bitcoin instead: 1EccFi98tR5S9BYLuB61sFfxKqqgSKK8Yz. This scale updates regularly.
-
Bunnywabbit
- Posts: 965
- Joined: Sun May 15, 2005 7:00 am
- Location: Amsterdam, the Netherlands
from Amsterdam, the Netherlands
Pingen naar tigereye.ca [204.14.17.162] met 32 byte gegevens:
Antwoord van 204.14.17.162: bytes=32 tijd=122 ms TTL=57
Antwoord van 204.14.17.162: bytes=32 tijd=123 ms TTL=57
Antwoord van 204.14.17.162: bytes=32 tijd=122 ms TTL=57
Antwoord van 204.14.17.162: bytes=32 tijd=122 ms TTL=57
Ping-statistieken voor 204.14.17.162:
Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
(0% verlies).De gemiddelde tijd voor het uitvoeren van één bewerking in mill
iseconden:
Minimum = 122ms, Maximum = 123ms, Gemiddelde = 122ms
Bezig met het traceren van de route naar tigereye.ca [204.14.17.162]
via maximaal 30 hops:
1 14 ms 13 ms 13 ms 3E3313FE.dslaccess.aol.com [62.51.19.254]
2 14 ms 14 ms 14 ms bb1-ams-G4-3-0.atdn.net [66.185.134.93]
3 14 ms 13 ms 13 ms bb1-ams-G4-3-0.atdn.net [66.185.134.93]
4 21 ms 21 ms * bb2-frr-S1-3-0.atdn.net [66.185.152.191]
5 21 ms 20 ms 21 ms pop1-frr-S1-1-0.atdn.net [66.185.139.15]
6 20 ms 21 ms 20 ms DTAG-FRR.atdn.net [66.185.147.98]
7 123 ms 123 ms 123 ms yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201]
8 122 ms 123 ms 123 ms 217.6.24.194
9 123 ms 123 ms 123 ms mail.initechcomputers.com [204.14.17.162]
De trace is voltooid.
Pingen naar tigereye.ca [204.14.17.162] met 32 byte gegevens:
Antwoord van 204.14.17.162: bytes=32 tijd=122 ms TTL=57
Antwoord van 204.14.17.162: bytes=32 tijd=123 ms TTL=57
Antwoord van 204.14.17.162: bytes=32 tijd=122 ms TTL=57
Antwoord van 204.14.17.162: bytes=32 tijd=122 ms TTL=57
Ping-statistieken voor 204.14.17.162:
Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
(0% verlies).De gemiddelde tijd voor het uitvoeren van één bewerking in mill
iseconden:
Minimum = 122ms, Maximum = 123ms, Gemiddelde = 122ms
Bezig met het traceren van de route naar tigereye.ca [204.14.17.162]
via maximaal 30 hops:
1 14 ms 13 ms 13 ms 3E3313FE.dslaccess.aol.com [62.51.19.254]
2 14 ms 14 ms 14 ms bb1-ams-G4-3-0.atdn.net [66.185.134.93]
3 14 ms 13 ms 13 ms bb1-ams-G4-3-0.atdn.net [66.185.134.93]
4 21 ms 21 ms * bb2-frr-S1-3-0.atdn.net [66.185.152.191]
5 21 ms 20 ms 21 ms pop1-frr-S1-1-0.atdn.net [66.185.139.15]
6 20 ms 21 ms 20 ms DTAG-FRR.atdn.net [66.185.147.98]
7 123 ms 123 ms 123 ms yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201]
8 122 ms 123 ms 123 ms 217.6.24.194
9 123 ms 123 ms 123 ms mail.initechcomputers.com [204.14.17.162]
De trace is voltooid.

current version r158 new beta as of jan 23 2012I'd throw some cash your way El Tigre
I'm sorry I don't remember any of it. For you the day spideycw graced your squad with utter destruction was the most important day of your life. But for me, it was Sunday
Idanmel wrote:QUOTE (Idanmel @ Mar 19 2012, 05:54 AM) I am ashamed for all the drama I caused, I have much to learn on how to behave when things don't go my way.
My apologies.



