Aces High Bulletin Board
General Forums => Aces High General Discussion => Topic started by: Duedel on May 04, 2002, 04:23:16 PM
-
Sorry, i know this belongs to the Internet Connectivity Forum but im getting a withdrawal syndrome.
First of all german (european?) players have a problem to get into the MA. Since 2 days I have packet loss about 60% and when I get into MA I get the following message:
Not receiving updates switched to TCP.
All other arenas work very well. I really would appreciate it if someone could explain the cause of this problem! Maybe HT a little statement?
Thx
-
Recently from what I've seen duedal, its only those of us in Germany having the problem. I can't get into the MA at all anymore :(
Must be a Deutsche Telekom problem.
-
LOL, now THAT explains why rooks have been winning last two days - not many german players flying for rooks ;)
-
No Kronos that is not a Telekom problem. We checked that.
It`s a HTC Problem.
And i hope they fix the Problem soon.
Greets,
Alino
-
yes cant be a telekom problem cause CT TA DA H2H work well. Only MA doesnt work.
>LOL, now THAT explains why rooks have been winning last two days
:D
-
LOL Duedel u say it, seems that is the only way for them to win ,-))))))))))))))))
-
Lost package OUCH that's gotta hurt!
-
Happened to me once. I switched from FedEx to UPS, and haven't had any trouble since
-Sikboy
-
What you guys with poor conns need is a protocol Norwegians built some time ago: Protocol RFC1149 (http://dir.salon.com/tech/feature/2001/05/10/pigeons/index.html) :)
More about that protocol in Here (http://www.ietf.org/rfc/rfc1149.txt?number=1149)
-
I presume you have a T-Online account - then it's the same problem I'm having. Some Telekom router went down, pings of 300+ and 75% PL resulting. ATM, I use call2surf, which works fine. Duedel, you might want to check http://www.heise.de and look up the Internettarife.
OT, I got my k/d ratio to > 1.0 :D feeling fine...
-
FedEx P0WNX0RZ UPS, both in prices, delivery time, and they dont play soccer with your packages.
-
I don't have the problems you mention, Duedel. Not even at times when the Main hits 400+ players. 160-170ms ([trace via alter.net] which is damn good for the distance) and fairly stable host queue/ping times. Sometimes I'm glad I'm not a T-Offline user :D ;)
-
Never had a problem with the Telekom. Why MA dont work and all other arenas work well?
Thx for ur suggestion dtx but I'm not willing to pay for other providers when I have a flat rate (not yet, maybe in 2 days :D). Hope to see u soon in MA :)
-
The Main Arena is on a differant server than the CT,TA,DA,SEA etc.
That may go some way toward explaining why the MA is unreachable for you when the rest are fine.
Blue
-
Originally posted by Animal
and they dont play soccer with your packages.
Lol, I got a nice settlement that dissagrees with you :)
-Sikboy
-
Tried Call2Surf (ISDN-Provider) to connect to MA and it's working fine (but it costs money :( )! I don't understand this! Why does T-DSL has Problem only with MA and why does ISDN work? I'm totally confused. Anybody know where I can kill a Telekomiker?
-
Ok friends i tracert the route here is the result:
Routenverfolgung zu 216.234.247.240 über maximal 30 Abschnitte
1 55 ms 55 ms 55 ms 217.5.98.143
2 55 ms 55 ms 55 ms 217.237.156.110
3 151 ms 151 ms 151 ms Vienna-gw12.USA.net.DTAG.DE [62.156.131.182]
4 138 ms 138 ms 138 ms dt-gw.wswdc.ip.att.net [194.25.6.234]
5 137 ms 138 ms 138 ms gbr4-p50.wswdc.ip.att.net [12.123.9.54]
6 151 ms 165 ms 165 ms gbr4-p30.attga.ip.att.net [12.122.2.225]
7 179 ms 178 ms 179 ms gbr3-p20.dlstx.ip.att.net [12.122.2.89]
8 179 ms 178 ms 165 ms gbr5-p60.dlstx.ip.att.net [12.122.5.73]
9 179 ms 178 ms 179 ms gar2-p360.dlstx.ip.att.net [12.123.17.25]
10 165 ms 179 ms 178 ms gar1-p3100.dlrtx.ip.att.net [12.123.196.101]
11 165 ms 165 ms 164 ms 12.119.136.22
12 164 ms 179 ms 179 ms border3.ge3-1-bbnet1.ext1.dal.pnap.net [216.52.
91.22]
13 384 ms 206 ms 206 ms theplanet-2.border3.003.dal.pnap.net [216.52.18
.222]
14 * 370 ms * 216.234.247.240
15 * * * Zeitüberschreitung der Anforderung.
16 357 ms 357 ms 357 ms 216.234.247.240
Ablaufverfolgung beendet.
I talket with t-online, result of tracering the route: It must be Problem of US server.
Greets, Alino
Ps: I begin Download WarBirds to have a look if it can be enjoyeble for me. We hang on for the 3rd day here now and there is now answer from HTC.
I mailt 3times to the supportteam and i get not 1 response. Think that`s not OK.
-
Duedel, all ISDN data traffic is concentrated into 2mbit lines at your local Telekom outlet. From there it will be fed to the ATM Backbone, in about 4 hops. The Telekom ATM backbone has about 100 nodes, and the one carrying the route to the MA seems fuxored. Now if some other provider takes your ISDN data stream off the backbone in another node, and connects it to the MA server via it's own (paid-for) route to the US of A, you just may have better results.
Gonna post some traceroutes l8er.
-
traceroute for call2surf:
(...)
14 164 ms 165 ms 151 ms p4-0-1-0.r80.nwrknj01.us.bb.verio.net [129.250.2
.222]
15 164 ms 165 ms 165 ms p4-1-3-0.r01.nwrknj01.us.bb.verio.net [129.250.5
.41]
16 165 ms 165 ms 165 ms p4-0-1.r01.phlapa01.us.bb.verio.net [129.250.3.1
25]
17 165 ms 165 ms 165 ms p4-1-0-0.r00.phlapa01.us.bb.verio.net [129.250.3
.153]
18 165 ms 165 ms 178 ms p4-6-0-0.r00.stngva01.us.bb.verio.net [129.250.3
.105]
19 206 ms 193 ms 193 ms p16-2-0-0.r02.dllstx01.us.bb.verio.net [129.250.
5.34]
20 206 ms 206 ms 206 ms ge-0-0-0.a11.dllstx01.us.ra.verio.net [129.250.3
1.59]
21 178 ms 192 ms 193 ms so-1-2-0.a11.dllstx01.us.ce.verio.net [157.238.2
27.226]
22 193 ms 192 ms 192 ms border3.ge4-1-bbnet2.ext1.dal.pnap.net [216.52.1
91.83]
23 192 ms 192 ms 192 ms theplanet-2.border3.003.dal.pnap.net [216.52.189
.222]
24 206 ms 220 ms 220 ms 216.234.247.240
There !
Traceroute for Telekom:
1 28 ms 27 ms 28 ms 212.185.250.185
2 28 ms 27 ms 28 ms 212.185.250.182
212.185.250.182 is fuxored. :mad:
-
sorry devious mein english ist nicht gut genug das alles zu übersetzen.
-
Naja für die routre bruche ich dann keine übersetzung ;-((
-
Alino: I begin Download WarBirds to have a look if it can be enjoyeble for me. We hang on for the 3rd day here now and there is now answer from HTC.
LOL after playing in CT yesterday (BTW was fun) I started to play WBIII offline. I really hate the FM!
Calm down alino ;) as dtx posted above (thanks m8) i think it's a problem of our heroic %/!"§$ Telekom so HTC can't do anything.
-
Damn Duedel maybe you are right.
After i transmitted the tracerroute for call2surf to the Terrorkom they said : "oh maybe perhaps we have a little problem there. technik will check it tomorrow."
Grummel grummel ärger hass §$%)($/§"
naja we will see
-
Sorry, Duedel.
I can't share your optimism that the telekom is responsible.
I made several tracert round the globe, but the only server/node with problems is the MA server of Hitech.
But maybe someone of WBIII or WWIIonline bribed the telekom to cut off AH from Germany :rolleyes:
The last "working" Server is theplanet-2.
There is nothing more to say about it :mad:
Tofri
-
Hey ToFri Kuer tried WWiionline same Problem there
-
how many of you are dsl?
im losing 40-60% between the planet and htc all other hops are fine. Im in florida btw and dsl.
I made a post last monday in the internet connect forum.
wwiiol servers suk any way imho so i wouldn't use that as proof of anything.
My traces and connect to the other ht servers are fine.
-
Im DSL here, connected too warbirds, 200 ping no packet loss:confused:
BTW didn't play just connected ;)
-
ADSL here (Terra networks), more than 60% packet lost.
-
Ok,..been reading about the problems from Germany and if I may, I think I can get a handle on this.
When you see a traceroute, each and every 'hop' is a router. The things you do not see are switches. But, I will leave switches to another discussion.
Typically, when you see high pings/packet losses at either the last hop or next to the last hop of a traceroute, it is partly due to an asynchronous route.
Asynchronous routes occur when the data path to your destination is different than the data path from the destination back to you.
In this case, it appears the problem is the return path back to you. Because you cannot see that path, you cannot get a true evaluation of your connection. Somewhere along the way on the return path, there is a problem. It could be a router, switch, or physical link problem.
Why would it happen at the MA and not other places? Well, the odds are pretty slim that any given connection you have to any give point on the Internet is not going to take the same path, but if it does, you will see the same problem.
Not having access to the return path makes it difficult to see where the problem is.
To answer some other questions; The reason all the other arenas may be working fine for you is due to the different path and backbone ISP AppLink uses.
I know the knee jerk reaction is to think HTC is the problem, but in fact, the real issue may be beyond thier control at this time. Hopefully this will not be an issue much longer, as we are making headway to getting the new pipes to AppLink so we can get the MA back here.
-
CC DSL here loosing 60-70% at theplanet.
Skuzzy maybe or maybe not that the reason is to search at HT.
But the thing that make me galling is: There is not one reaction to the mail`s that i have send to the support.
To know that they are searching for the Problem would be a bit becalming.
-
Cable here, 50% PL, :(
-
Sweden, ADSL, 400-800 ping to HTC server. The problem is at HTC, I have 150ms to the server before HTC then it goes up to nearly 800 when it hits HTC.
-
Problem seems to be the same in Germany, Netherlands, Spain and Sweden. It must be a HTCproblem but no react from them.
-
..and Finland as well. Never had this bad conx. 450-750 ms (usually solid 180ms) and discos that costs 70 perks / each.
-
Originally posted by Wilbus
Sweden, ADSL, 400-800 ping to HTC server. The problem is at HTC, I have 150ms to the server before HTC then it goes up to nearly 800 when it hits HTC.
Wilbus, again, it is an asynchrounous route. This is not something HTC can control. It very well could be the return path, but do not take the last hop jump as a HTC problem. They cannot control how data is routed over the Internet.
-
Originally posted by Skuzzy
Wilbus, again, it is an asynchrounous route. This is not something HTC can control. It very well could be the return path, but do not take the last hop jump as a HTC problem. They cannot control how data is routed over the Internet.
Hi Skuzzy, the Problem is in 5 Countries in europe. It`s Germany,Netherlands,Sweden,Spain and Finnland. Who the hell if not HTC can find out the Problem. ME NOT.
-
Clumpsy said Skuzzy, what I ment is that it's at HTC or nearby, it's not our connections that is for sure, unless we all happen to have a pretty bad day down here in europe. Connection is sollid untill it gets to the HTC server.
-
It is not about who can find out the problem Alino. Depending on where the problem lies, there may be nothing HTC can do but wait it out.
I do not know exactly where the problem is. Looking at all the trace data I have seen, it mostly appears to be a return data path issue. I do not have access to the network where the MA is hosted, so it is difficult for me to say.
However, I have been through issues like this one, and it is not usually something that is resolved quickly.
Also, while many are complaining, very few are posting any helpful data. I see a ton of complaints in the Internet Forum, but only 2 traceroutes. Without data, there is absolutely nothing anyone can do. So any complaints without any trace data is pretty much worthless and would/should be ignored.
You are one of the few that has posted any trace data Alino, and it is appreciated. This is what is needed to find the problem.
-
Originally posted by Skuzzy
Also, while many are complaining, very few are posting any helpful data. I see a ton of complaints in the Internet Forum, but only 2 traceroutes. Without data, there is absolutely nothing anyone can do. So any complaints without any trace data is pretty much worthless and would/should be ignored.
Why should I bother stuffing my post with trace routes, when every other trace route that is already posted, shows the same.
Up to theplanet-2 erverything is fine.
I do not know and I cant test it, if there are any switches and routers between theplanet-2 and tpl.HTC .
But if there is any rerouting on routers or more likely balancers, then it happens between the last two hops.
The ISP had problem with the bandwith??
It seems, that they have solved the problem in a very unorthodox way.
They mask out a certain group of IP-adresses and let them run into a bottleneck. :mad: :mad:
Skuzzy, please take the Main-server back as soon as possible. Even with a T1-Connection it was never that bad. We had lags, but we could play at least.
Here is my actual trace route
NeoTrace Version 2.12a - Shareware (2-1-2000)
Destination: tpl.hitechcreations.com
-#--------------Node Name---------------IP Address------Location-----------RT*--High---Low---Avg-Tot---D-Who
1 tom 192.168.1.1 50.000N, 6.000E 0 0 0 0 1 0
2 217.5.98.141 Unknown 54 54 54 54 1 0
3 217.237.156.94 Unknown 53 53 53 53 1 0
4 vienna-gw12.usa.net.dtag.de 62.156.131.182 Unknown 150 150 150 150 1 0
5 dt-gw.wswdc.ip.att.net 194.25.6.234 38.908N, 77.017W 147 147 147 147 1 0
6 gbr4-p50.wswdc.ip.att.net 12.123.9.54 38.908N, 77.017W 146 146 146 146 1 0
7 gbr4-p30.attga.ip.att.net 12.122.2.225 33.750N, 84.383W 158 158 158 158 1 0
8 gbr3-p20.dlstx.ip.att.net 12.122.2.89 32.783N, 96.800W 171 171 171 171 1 0
9 gbr5-p60.dlstx.ip.att.net 12.122.5.73 32.783N, 96.800W 172 172 172 172 1 0
10 gar2-p360.dlstx.ip.att.net 12.123.17.25 32.783N, 96.800W 172 172 172 172 1 0
11 gar1-p3100.dlrtx.ip.att.net 12.123.196.101 Unknown 172 172 172 172 1 0
12 12.119.136.22 Unknown 172 172 172 172 1 0
13 border3.ge4-1-bbnet2.ext1.dal.pnap.net 216.52.191.83 Unknown 171 171 171 171 1 0
14 theplanet-2.border3.003.dal.pnap.net 216.52.189.222 Unknown 173 173 173 173 1 0
15 tpl.hitechcreations.com 216.234.247.240 32.934N, 97.095W 360 360 360 360 1 0
--------------------------------------------------------------------------------------------------------
*All times in milliseconds (ms), D=Dropped packets
------------------------------------------------------------------------------------------------------------
May 5, 2002 21:2:23
NeoTrace Copyright ©1997-1999 NeoWorx inc
http://www.neoworx.com
-
Skuzzy appreciate ur work to explain the whole problem. Thx and
:)
Target Name: tpl.hitechcreations.com
IP: 216.234.247.240
Date/Time: 05.05.2002 21:23:40
1 55 ms 69 ms 110 ms 55 ms [217.5.98.61]
2 55 ms 68 ms 82 ms 69 ms [217.237.153.194]
3 193 ms 151 ms 165 ms 164 ms Vienna-gw12.USA.net.DTAG.DE [62.156.131.182]
4 165 ms 151 ms 165 ms 151 ms dt-gw.wswdc.ip.att.net [194.25.6.234]
5 165 ms 164 ms 151 ms 151 ms gbr4-p50.wswdc.ip.att.net [12.123.9.54]
6 179 ms 165 ms 192 ms 164 ms gbr4-p30.attga.ip.att.net [12.122.2.225]
7 192 ms 178 ms 192 ms 192 ms gbr3-p10.dlstx.ip.att.net [12.122.3.37]
8 193 ms 192 ms 193 ms 192 ms gbr6-p60.dlstx.ip.att.net [12.122.5.81]
9 192 ms 179 ms 178 ms 178 ms gar2-p370.dlstx.ip.att.net [12.123.17.29]
10 178 ms 178 ms 179 ms 179 ms gar1-p3100.dlrtx.ip.att.net [12.123.196.101]
11 179 ms 179 ms 219 ms 178 ms [12.119.136.22]
12 192 ms 398 ms 261 ms 192 ms border3.ge3-1-bbnet1.ext1.dal.pnap.net [216.52.191.22]
13 193 ms 179 ms 248 ms 192 ms theplanet-2.border3.003.dal.pnap.net [216.52.189.222]
14 * * * * [-]
15 371 ms * 385 ms 357 ms [216.234.247.240]
-
Ok Skuzzy here is one actually
1 69 ms 55 ms 1442 ms 217.5.98.143
2 55 ms 55 ms 55 ms 217.237.156.110
3 151 ms 137 ms 137 ms Vienna-gw12.USA.net.DTAG.DE [62.156.131.182]
4 1071 ms 151 ms 151 ms dt-gw.wswdc.ip.att.net [194.25.6.234]
5 151 ms 151 ms 151 ms gbr4-p50.wswdc.ip.att.net [12.123.9.54]
6 151 ms 165 ms 165 ms gbr4-p30.attga.ip.att.net [12.122.2.225]
7 179 ms 178 ms 179 ms gbr3-p20.dlstx.ip.att.net [12.122.2.89]
8 178 ms 179 ms 178 ms gbr6-p60.dlstx.ip.att.net [12.122.5.81]
9 178 ms 179 ms 165 ms gar2-p370.dlstx.ip.att.net [12.123.17.29]
10 178 ms 179 ms 178 ms gar1-p3100.dlrtx.ip.att.net [12.123.196.101]
11 178 ms 165 ms 164 ms 12.119.136.22
12 178 ms 179 ms 178 ms border3.ge3-1-bbnet1.ext1.dal.pnap.net [216.52
91.22]
13 178 ms 179 ms 178 ms theplanet-2.border3.003.dal.pnap.net [216.52.1
.222]
14 357 ms 370 ms * 216.234.247.240
15 370 ms 357 ms * 216.234.247.240
16 357 ms 385 ms * 216.234.247.240
17 * * * Zeitüberschreitung der Anforderung.
18 357 ms 370 ms 357 ms 216.234.247.240
Like ToFri said take it back soon please.
-
Ah hah! Anyone notice that all the traces start from the same Class A address of 217.x.x.x?
Looks like we got a route problem going on here. I did a trace back to one of the posters in the Internet forum and the data going back to him was getting hung up in a router on his local ISP (telia).
Looks like someone has propogated a bad route table for the 217.x.x.x IP address block.
The owner of that Class A block is Deutsche Telekom AG. They are apparently propagating bad route tables for this block.
This is why we need traceroutes. It is not neccessarily the times in the routes, it is also the addresses. When the routes are asynchronous, there is no way for you to know where the problem really is.
Now, getting it fixed could be a problem. I have not had much luck in getting overseas issues corrected. Anyone familiar with the above company?
-
tofri, Duedel and Alino, tracing back to you, the data stops at the following router - 217.237.156.109, which is a dtag.de router.
-
Skuzzy that`s good to know. I will phone the Telekom and confront them with that.
Thank`s a lot for your work man.
-
Skuzzy here i am again.
I phoned to the Telekom. And told them of that 217...router
They asked from who i got that information and asked for your mailadress is ok to give it to them ??
They will check it out tomorrow. So i can`t do anything more then wait now.
-
Sure Alino,..would be happy to help them anyway I can. Until they get involved the problem will drag on forever.
-
Originally posted by tofri
The ISP had problem with the bandwith?? It seems, that they have solved the problem in a very unorthodox way.
No, that's common practice I think.
Das oben war nicht wirklich als Witz gemeint, fliegt irgendjemand von hier fuer Tuerme?
-
Hahaha told u guys it was telekom all along :D
Dangnabbit.
-
LOL ..hehehe ...hohoho ......ya'll want help from Telekom, .....good luck.:eek:
-
FedEx P0WNX0RZ UPS, both in prices, delivery time, and they dont play soccer with your packages.
Maybe not soccer but after a look in the back of the guy from UPs delivering our company it could be maybe "catch the packet"
-
Day 4 still the same
C:\WINDOWS>tracert 216.234.247.240
Routenverfolgung zu 216.234.247.240 über maximal 30 Abschnitte
1 55 ms 68 ms 55 ms 217.5.98.143
2 55 ms 55 ms 55 ms 217.237.156.110
3 137 ms 151 ms 151 ms Vienna-gw12.USA.net.DTAG.DE [62.156.131.182]
4 * 151 ms 151 ms dt-gw.wswdc.ip.att.net [194.25.6.234]
5 138 ms 151 ms 151 ms gbr4-p50.wswdc.ip.att.net [12.123.9.54]
6 152 ms 164 ms 165 ms gbr4-p10.attga.ip.att.net [12.122.2.161]
7 179 ms 178 ms 179 ms gbr3-p10.dlstx.ip.att.net [12.122.3.37]
8 * 192 ms * gbr2-p60.dlstx.ip.att.net [12.122.5.229]
9 179 ms 164 ms 165 ms gar1-p370.dlstx.ip.att.net [12.123.16.237]
10 179 ms 164 ms 179 ms gar1-p340.dlrtx.ip.att.net [12.123.196.97]
11 165 ms 178 ms 179 ms 12.119.136.22
12 179 ms 164 ms 179 ms border3.ge3-1-bbnet1.ext1.dal.pnap.net [216.52.
91.22]
13 165 ms 178 ms 192 ms theplanet-2.border3.003.dal.pnap.net [216.52.18
.222]
14 357 ms 371 ms 357 ms 216.234.247.240
Ablaufverfolgung beendet.
No way to get into MA
-
Alino, the problem still exists. Here is a traceroute back to 217.5.98.143 (number 1 hop in your trace) from the MA location.
Notice how the trace just stops at 217.237.156.109. This router/system seems to think it owns the 217.5.98.x Class C IP Block.
Get this to the Telekom folks and see if they can do something about it.
traceroute 217.5.98.143
traceroute to 217.5.98.143 (217.5.98.143), 30 hops max, 38 byte packets
1 core0.dllstx.theplanet.com (216.234.234.1) 2.926 ms 0.740 ms 5.180 ms
2 border3.fe5-1.theplanet-2.003.dal.pnap.net (216.52.189.221) 1.294 ms 0.876
ms 1.758 ms
3 core2.ge1-0-0-bbnet2.ext1.dal.pnap.net (216.52.191.97) 6.289 ms 2.136 ms
1.812 ms
4 500.POS2-2.GW2.DFW13.ALTER.NET (65.208.15.145) 4.327 ms 5.386 ms 2.897 ms
5 0.so-1-0-0.XL2.DFW13.ALTER.NET (152.63.103.230) 1.282 ms 6.191 ms 6.727 m
s
6 0.so-3-0-0.XL2.DFW9.ALTER.NET (152.63.103.221) 3.786 ms 6.512 ms 4.213 ms
7 POS7-0.BR2.DFW9.ALTER.NET (152.63.99.213) 9.329 ms 8.845 ms 11.555 ms
8 204.255.168.166 (204.255.168.166) 6.173 ms 4.457 ms 5.226 ms
9 p6-0.crtntx1-br1.bbnplanet.net (4.24.9.249) 6.636 ms 2.423 ms 10.329 ms
10 p9-0.iplvin1-br2.bbnplanet.net (4.24.10.214) 26.556 ms 23.030 ms 25.021 m
s
11 p15-0.iplvin1-br1.bbnplanet.net (4.24.10.153) 31.194 ms 26.280 ms 23.405
ms
12 p13-0.phlapa1-br1.bbnplanet.net (4.24.10.181) 40.704 ms 38.460 ms 46.529
ms
13 p13-0.nycmny1-nbr2.bbnplanet.net (4.24.10.178) 46.965 ms 48.385 ms 47.859
ms
14 so-7-0-0.nycmny1-hcr3.bbnplanet.net (4.0.7.13) 58.426 ms 44.158 ms 38.728
ms
15 p12-2.deutscheti.bbnplanet.net (4.25.133.6) 48.411 ms 42.967 ms 49.990 ms
16 BN-EB1.BN.DE.net.dtag.de (62.154.66.38) 129.821 ms 136.463 ms 130.239 ms
17 217.237.156.109 (217.237.156.109) 145.336 ms 134.128 ms 131.499 ms
-
Ok Skuzzy i will transmitit to them. Thx for your work.
-
Here we go again. Maybe Telekom knows that we play AH and that this is very expencive for them?
-
Now we have a few more trace routes on other postings, that do not go over the 217.x.x.x block.
And they have also problems of lags and packet losses.
What's about them?
I have some time, (I cannot log into the Main, remember?) so I traced down ervery goddoed IP from 216.234.247.1 to 216.234.247.100
The whole C-Class 216.234.247.x is owned by Internap.
I made first a traceroute and then checked the answering IPs with a browser.
There was one thing I noticed at once.
All Ips with the same nasty behviour as the TPL , refer to servers, that do not answer to standard browser requests (means no www or ftp...) and errr.... to porno sites :eek:
I have no idea what that might mean, just want to mention it.
a very frustrated Tofri
-
Originally posted by Duedel
Here we go again. Maybe Telekom knows that we play AH and that this is very expencive for them?
LOL Duedel. You never loose Humor he ? ,-)
-
Could it be interesting to compare our traceroutes to the MA with those to the TA or CT? Maybe we could get new hints where the problem is?
Whats the adress of the TA?
-
All the traces I see in this thread have a 217.x.x.x IP address in them. Which ones are you talking about tofri?
-
I checked the dsl news forum of t-online.
There are many complaints about the connection to US sites.
Seems that there is really a problem at the telekom lines.
Problem is the lack of response to complaints of customers.:(
tofri
-
Is it lack of response, or lack of information? ISP's need a lot of data to get routing problems ironed out. Sometimes they are not even aware of where the problem may be. This holds especially true of large ISP's.
I posted that trace back to the 217.x.x.x block to help show where one of the potential problems are. It has to be sent to the ISP so they can see a place to start fixing the problem.
I can categorically say the 217.5.98.x Class C block has a serious routing problem. The trace I posted shows the problem and at what router the problem is ocurring.
-
Out of curiousity, where did you learn all this stuff?
I would love to have the power of understanding the inner workings of the net.
-
This morning the connection is perfect as never before.
Constant pings around 180ms, no packet losses.
But now I have to go to work AAARRRGGGHHHHH
Cant HTC do anything against work, because of work I cant fly now in the Main;) :D ;) :D ;) :D
Thanks Skuzzy for your help!!!!
Tofri
-
Damn damn damn ;-)))))))) like Tofri said perfekt connect but we must go to work. I´m lucky that we can play this evening, hope we unlearned not to much.
Thank`s alot for your Help Skuzzy.
cya all
-
Can't believe it. It works? Im at work so i cant test it. Skuzzy Alino Tofri many thx for ur help. Anybody knows where's the cause for the problem, Telekom?
BTW dtx heute wollen wir uns so ab 20:00 in der MA treffen.
-
Sorry, bin bis Mittwochabend in München und ohne Kiste. Vielleicht kann ich ein I-Net Cafee auftreiben...
-
Hallo Leute,
no probs here since yesterday when nearly everybody in Main got bad connect.
If you german people wanna try out something beside
Fu(&/()%§"!)=&/((%$§§ing Telekom go Q-dsl.de.
It's a bit more expensive ,59 Eu flat, but worth the price.
You may wanna get MTU-Speed too. It's a nice little programm that helps to optimize Win network. It's freeware, btw.
Normally gettin around 170ms This was taken Tuesday around 1 oc daytime
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
tpl.hitechcreations.com 216.234.247.240 137ms 137ms 0% 30 / 30 137ms / 139ms
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * 212.202.222.33 2 3ms
* Unknown Host * 62.67.36.73 3 3ms
ge-7-0-0.mp2.Berlin1.Level3.net 195.122.132.130 4 3ms
so-1-0-0.mp1.London2.Level3.net 212.187.128.49 5 24ms
so-1-0-0.mp1.Washington1.Level3.n212.187.128.138 6 96ms
gigabitethernet7-2.core1.Washingt64.159.18.133 7 97ms
above-level3-ds3.iad.above.net 209.244.219.150 8 97ms
acr1-loopback.Dallas.cw.net 208.172.130.61 9 135ms
aar2-loopback.Dallas.cw.net 208.172.130.7 10 135ms
internap.Dallas.cw.net 208.172.135.70 11 142ms
border3.ge3-1-bbnet1.ext1.dal.pna216.52.191.22 12 141ms
theplanet-2.border3.003.dal.pnap.216.52.189.222 13 141ms
tpl.hitechcreations.com 216.234.247.240 14 137ms
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * 212.202.222.33 2 3ms
* Unknown Host * 62.67.36.73 3 4ms
ge-7-0-0.mp2.Berlin1.Level3.net 195.122.132.130 4 3ms
so-1-0-0.mp1.London2.Level3.net 212.187.128.49 5 25ms
so-1-0-0.mp1.Washington1.Level3.n212.187.128.138 6 97ms
gigabitethernet7-2.core1.Washingt64.159.18.133 7 98ms
above-level3-ds3.iad.above.net 209.244.219.150 8 98ms
acr1-loopback.Dallas.cw.net 208.172.130.61 9 135ms
aar2-loopback.Dallas.cw.net 208.172.130.7 10 135ms
internap.Dallas.cw.net 208.172.135.70 11 219ms
border3.ge3-1-bbnet1.ext1.dal.pna216.52.191.22 12 141ms
theplanet-2.border3.003.dal.pnap.216.52.189.222 13 141ms
tpl.hitechcreations.com 216.234.247.240 14 137ms
Blitz from Berlin
-
For all u German dudes QSC rules the world. Fek the TELEKOM.
:) :) :)
Got it sonce nearly a year and satisfied with it. it is worth every cent u pay for itQ-DSL (http://www.qsc.de)
-
glad you folks are back up and running. now come fight the bishrook hordes.
-
Originally posted by moose
Out of curiousity, where did you learn all this stuff?
I would love to have the power of understanding the inner workings of the net.
Geez moose....just through experience I guess. After doing this type of work for over 20 years, ya just pick up stuff.
I do spend a lot of time reading and researching though. The Internet and the associated protocols are always changing, so in some sense I am always in school.
I do spend a bit of time and money at Barnes and Noble as well.
-
I did some testing this morning and it does appear Telekom has corrected the routing problem.
Thank you to the guys that gave them the data to get this fixed. We are all in this together and times like this is when we needed to bang from both ends to get it fixed.
A special thanks to those that posted the traces, which enabled me to find out what the problem (at least this one anyways) was.
-
AAAAAAAAAAARRRRRRRRRRRRGGGGGG GGGGGGGGGGGGGGGGGGHHHHHHHHHHH HHHHHHHHHHHHHH :mad: :mad: :mad: :mad: :mad: :mad:
Come home from work and the same SH#T as the last days
Tofri
-
Dang it. They fixed one problem and introduced another. Here is a trace.
/usr/sbin/traceroute 217.237.156.110
traceroute to 217.237.156.110 (217.237.156.110), 30 hops max, 38 byte packets
1 core0.dllstx.theplanet.com (216.234.234.1) 24.391 ms 4.018 ms 2.242 ms
2 border3.fe5-1.theplanet-2.003.dal.pnap.net (216.52.189.221) 1.179 ms 1.776
ms 3.622 ms
3 core4.ge1-0-0-bbnet2.ext1.dal.pnap.net (216.52.191.99) 10.980 ms 6.967 ms
13.668 ms
4 so-1-2-0.a11.dllstx01.us.ra.verio.net (157.238.227.225) 6.334 ms 1.188 ms
1.518 ms
5 ge-6-0-0.r02.dllstx01.us.bb.verio.net (129.250.31.48) 1.300 ms 1.521 ms 1
.989 ms
6 p16-2-0-0.r00.stngva01.us.bb.verio.net (129.250.5.35) 36.071 ms 33.998 ms
36.544 ms
7 p4-0.dt.stngva01.us.bb.verio.net (129.250.9.198) 40.303 ms 32.558 ms 32.4
44 ms
8 Vienna-gw12.USA.net.DTAG.DE (62.156.131.173) 129.331 ms 130.004 ms 127.11
8 ms
9 H-SA2.H.DE.net.DTAG.DE (62.156.131.181) 130.369 ms 131.999 ms 130.722 ms
10 H-SA1.H.DE.net.dtag.de (62.154.49.157) 134.790 ms 127.400 ms 128.544 ms
11 K-SA1.K.DE.net.dtag.de (62.154.0.118) 129.815 ms 128.461 ms 128.115 ms
12 BN-SA1.BN.DE.net.dtag.de (62.154.1.98) 126.760 ms 126.768 ms *
13 BN-EB1.BN.DE.net.dtag.de (62.154.66.38) 133.343 ms * 131.338 msace.
Notice where I was tracing to? 217.237.156.110, and notice where it stops. The IP address is a router, which cannot be reached now. Also, notice the dropped packets/timeouts in the last 2 routers.
Sigh,..someone please get this to dtag.de and make them aware there is still a problem.
-
Same ole same for me
connect to the MA
-
And one to the CT
-
Unbelievable this morning was everything ok, and now it`s the same like last 4 days. I hate it.
Routenverfolgung zu 216.234.247.240 über maximal 30 Abschnitte
1 68 ms 55 ms 55 ms 217.5.98.143
2 632 ms 55 ms 55 ms 217.237.156.110
3 151 ms 151 ms 151 ms Vienna-gw12.USA.net.DTAG.DE [62.156.131.182]
4 151 ms 151 ms 137 ms dt-gw.wswdc.ip.att.net [194.25.6.234]
5 151 ms 151 ms 151 ms gbr4-p50.wswdc.ip.att.net [12.123.9.54]
6 165 ms 165 ms 151 ms gbr4-p30.attga.ip.att.net [12.122.2.225]
7 164 ms 165 ms 178 ms gbr3-p20.dlstx.ip.att.net [12.122.2.89]
8 179 ms 164 ms 179 ms gbr5-p60.dlstx.ip.att.net [12.122.5.73]
9 179 ms 178 ms 179 ms gar2-p360.dlstx.ip.att.net [12.123.17.25]
10 164 ms 179 ms 178 ms gar1-p3100.dlrtx.ip.att.net [12.123.196.101]
11 179 ms 192 ms 179 ms 12.119.136.22
12 179 ms 178 ms 178 ms border3.ge4-1-bbnet2.ext1.dal.pnap.net [216.52.1
91.83]
13 178 ms 179 ms 178 ms theplanet-2.border3.003.dal.pnap.net [216.52.189
.222]
14 357 ms * * 216.234.247.240
15 370 ms * * 216.234.247.240
16 371 ms * 370 ms 216.234.247.240
Ablaufverfolgung beendet.
Seems we joyed to early this morning. DAMN
-
Actually. it is worse than it was yesterday. They really have that 217.x.x.x Class A block messed up.
It has changed from the path it was taking yesterday, but not for the better. At least the router that was claiming this particular Class A, was able to pass some packets, the new path is wrought with all kinds of packet loss and is not routing correctly.
Notice the differences in my two traces. The last hop of the trace yesterday stopped at a partucular router. The new trace from today stops one hop before the the router from yesterday.
Almost looks like they just turned off a router. I know that is not it, but this is just bizarre.
-
Scccccccccchhhhhhhhhheeeeeeei iiiissssssseeee *
*Alino u notice i've lost my humor right NOW!
BTW I send the traceroute from Skuzzy to our beloved Telekom but i doubt they'll take a look at it.
-
Originally posted by Duedel
Scccccccccchhhhhhhhhheeeeeeeiiiiissssssseeee *
*Alino u notice i've lost my humor right NOW!
BTW I send the traceroute from Skuzzy to our beloved Telekom but i doubt they'll take a look at it.
Jau Mann ich auch Sch.......................eiße
-
Skuzzy i have send all that tracert`s to the Telekom.
I hope they will fix that Problem in the next 5 day`s.
I go for a short holliday trip now. I don`t want to see that bad stuff here longer ;-)))
to all. Don`t worry be happy.
-
I dunno.. I'm on Cable here in Fla.. and the game just sucked last night..I had a ping rate of 218.. today it seems a bit better. I feel it's a HTC server problem..Not ours..
-
Happy if I have ping 218. Right now I have 750.
-
Yeap same s**t now as have been for almost a week now
Ping is 750-900 and 10-30% PL , and now I always get the swithing to TCP when trying to log on to MA (never has that in normally)
usally I have ping times steady on 150
I am beginning to wonder if its worth to pay for a game u cant play? :mad:
-
Now the connection to the MA is perfect again.
I found an unofficial news board for telekom routing problems. Now I'm absolutely sure that it was a problem of the telekom.
There many people who had the same problems on other adresses.
But at the moment it seems to work everything.
Most funny were the reaction of the telekom to the complaint I posted on their news board.
They spoke of conspiracy and moved the post to an other board, which hardly anybody uses.
I wasn't even sarcastic, just posted the facts we found.
Seems that this is the standard punishment for renegade clients.
I finally decided to look for some more customer friendly ISP.
THX again to everybody
I hope this was the last time to post in this post :cool:
-
Rompa, does your traceroute contain a 217.x.x.x IP Address? I noticed you are from Sweden, so it is worth a look. If the trace has that IP address in it, then you are suffering from the same routing problem as many of the European players.
nuchpatrick: There is a real routing problem in Europe. How many ways to I have to post the proof of this? If you are having a problem and want help, please post a traceroute. With no data, there is nothing anyone can do to help.
The immediate assumption it is HTC's problem is not correct. It is thier problem if you are not happy, but they nor I can do anything about it if you just get on the BBS and rant/comment about it. These types of complaints are appearing all over many BBS's, for many games.
There are some real problems with the Internet right now. It has me somewhat befuddled, as I have never seen such a huge scope of problems ocurring on the Internet at one time.
-
I just did some tests tofri, They look to be working on it, but it may not be stable yet.
By the way, just to put a number to the magnitude of the problem here. This particular routing problem has the ability to effect over 16.3 million computers in Europe.
Thats a lot of potentially angry people.
Ahh tofri,...you doubt my work,...bummer.
-
Alrighty..I'm still showing some bad spikes today..so heres my two cents worth... heres my trace from Florida..Right now on AH i'm getting 180.. where I normally get 55-75. Since yester day it has been horrid..and thats using clean wording.
Tracing route to 216.234.247.240 over a maximum of 30 hops
1 13 ms 28 ms 27 ms 10.105.208.1
2 28 ms 13 ms 28 ms HE8-CENTRAL-7507A-P010.cfl.rr.com [24.95.225.122
]
3 14 ms 69 ms 41 ms HE6-CENTRAL-GSRB-SRP10.cfl.rr.com [24.95.224.39]
4 28 ms 137 ms 28 ms HE5-CENTRAL-GSRD-SRP40.cfl.rr.com [24.95.224.10]
5 110 ms 96 ms 83 ms pop1-tby-P0-2.atdn.net [66.185.136.173]
6 28 ms 82 ms 55 ms bb1-tby-P0-0.atdn.net [66.185.136.161]
7 55 ms 96 ms 110 ms bb2-atm-P7-0.atdn.net [66.185.153.94]
8 110 ms 82 ms 41 ms pop1-atm-P1-0.atdn.net [66.185.147.198]
9 55 ms 110 ms 41 ms atl-edge-07.inet.qwest.net [65.112.33.129]
9 55 ms 110 ms 41 ms atl-edge-07.inet.qwest.net [65.112.33.129]
10 110 ms 83 ms 27 ms atl-core-01.inet.qwest.net [205.171.21.81]
11 68 ms 83 ms 68 ms atl-core-03.inet.qwest.net [205.171.21.154]
12 96 ms 137 ms 124 ms kcm-core-03.inet.qwest.net [205.171.29.153]
13 110 ms 96 ms 96 ms iah-core-02.inet.qwest.net [205.171.8.141]
14 151 ms 110 ms 123 ms iah-core-03.inet.qwest.net [205.171.31.42]
15 165 ms 179 ms 110 ms dal-core-03.inet.qwest.net [205.171.5.171]
16 96 ms 110 ms 124 ms dal-core-01.inet.qwest.net [205.171.25.133]
17 96 ms 83 ms 110 ms dal-edge-07.inet.qwest.net [205.171.25.54]
18 123 ms 83 ms 68 ms 65.118.50.142
19 110 ms 110 ms 68 ms border3.ge4-1-bbnet2.ext1.dal.pnap.net [216.52.1
91.83]
20 316 ms 247 ms 247 ms theplanet-2.border3.003.dal.pnap.net [216.52.189
.222]
21 110 ms 123 ms 110 ms 216.234.247.240
Trace complete.
-
Ahoi all, just fr the german folks.
tday 12oc i t night w q-dsl
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
rqsc-frnk-de01-pm1-1-0-143.nw.med213.20.255.65 2 23ms
rmws-frnk-de12-ln5-0-0.nw.mediawa195.71.236.187 3 21ms
rmws-lond-uk09-pp3-2-1.nw.mediawa195.71.254.234 4 38ms
rmws-lond-uk05-ln5-0-0.nw.mediawa62.55.96.7 5 38ms
ge-0.linx.londen02.uk.bb.verio.ne195.66.224.138 6 37ms
p4-1-1-0.r00.amstnl02.nl.bb.verio129.250.2.51 7 43ms
p4-1-3-0.r01.amstnl02.nl.bb.verio129.250.2.133 8 44ms
p4-0-1-0.r80.nwrknj01.us.bb.verio129.250.2.222 9 133ms
p4-1-3-0.r01.nwrknj01.us.bb.verio129.250.5.41 10 132ms
p4-0-1.r01.phlapa01.us.bb.verio.n129.250.3.125 11 136ms
p4-1-0-0.r00.phlapa01.us.bb.verio129.250.3.153 12 136ms
p4-6-0-0.r00.stngva01.us.bb.verio129.250.3.105 13 142ms
p16-2-0-0.r02.dllstx01.us.bb.veri129.250.5.34 14 175ms
ge-0-0-0.a11.dllstx01.us.ra.verio129.250.31.59 15 171ms
so-1-2-0.a11.dllstx01.us.ce.verio157.238.227.226 16 161ms
border3.ge4-1-bbnet2.ext1.dal.pna216.52.191.83 17 161ms
theplanet-2.border3.003.dal.pnap.216.52.189.222 18 162ms
tpl.hitechcreations.com 216.234.247.240 19 197ms
blitz
-
YES Skuzzy my first hop is 217.210.254.1
So my connect is all fubar because of something on d-telecoms net,.... hmmm atleast Sweden won over Germany in icehockey world ch tonigt :D
-
The thing is, every day for the past (almost) week between (Central Euro time) 6pm and about 1am the connection SUCKS, this is when every european dweeb are surfing after they get home from work. So we can't fly. Check servers before that time (I was home early today) and you got normal good connection, posting now, 1.12am and ping time is stable and bellow 200ms.
-
looks like things are happening in the Internet world:D
-
Something is still very wrong. Check out the following traces.
This trace is tracing to hop #2 in your trace. Notice the route and final place it stops. The IP address it stops at is not the IP address I am tracing to.
/usr/sbin/traceroute 217.5.98.90
traceroute to 217.5.98.90 (217.5.98.90), 30 hops max, 38 byte packets
1 core0.dllstx.theplanet.com (216.234.234.1) 0.720 ms 0.642 ms 0.758 ms
2 border3.fe5-1.theplanet-2.003.dal.pnap.net (216.52.189.221) 1.154 ms 0.796
ms 0.690 ms
3 core2.ge1-0-0-bbnet2.ext1.dal.pnap.net (216.52.191.97) 0.795 ms 0.675 ms
0.904 ms
4 500.POS2-2.GW2.DFW13.ALTER.NET (65.208.15.145) 1.173 ms 1.027 ms 0.681 ms
5 0.so-1-0-0.XL1.DFW13.ALTER.NET (152.63.103.226) 0.966 ms 1.145 ms 0.887 m
s
6 0.so-3-1-0.XL1.DFW9.ALTER.NET (152.63.103.217) 1.955 ms 1.670 ms 1.662 ms
7 POS6-0.BR2.DFW9.ALTER.NET (152.63.99.209) 1.647 ms 1.817 ms 1.698 ms
8 204.255.168.166 (204.255.168.166) 2.647 ms 5.902 ms 2.535 ms
9 p6-0.crtntx1-br1.bbnplanet.net (4.24.9.249) 3.492 ms 2.943 ms 18.619 ms
10 p9-0.iplvin1-br2.bbnplanet.net (4.24.10.214) 22.119 ms 22.087 ms 21.914 m
s
11 p15-0.iplvin1-br1.bbnplanet.net (4.24.10.153) 22.444 ms 22.182 ms 21.836
ms
12 p13-0.phlapa1-br1.bbnplanet.net (4.24.10.181) 41.164 ms 55.543 ms 37.253
ms
13 p13-0.nycmny1-nbr2.bbnplanet.net (4.24.10.178) 41.960 ms 38.628 ms 40.991
ms
14 so-7-0-0.nycmny1-hcr3.bbnplanet.net (4.0.7.13) 83.018 ms 47.708 ms 39.228
ms
15 p12-2.deutscheti.bbnplanet.net (4.25.133.6) 40.670 ms 210.021 ms 208.422
ms
16 F-EB1.F.DE.net.dtag.de (62.154.17.138) 120.260 ms 121.943 ms 124.761 ms
17 217.237.152.101 (217.237.152.101) 130.859 ms 123.073 ms 136.983 ms
This trace is to your hop #3. Notice how different the route is and the last hop is, again, not the IP address I am tracing to.
/usr/sbin/traceroute 217.237.152.102
traceroute to 217.237.152.102 (217.237.152.102), 30 hops max, 38 byte packets
1 core0.dllstx.theplanet.com (216.234.234.1) 6.386 ms 0.632 ms 5.611 ms
2 border3.fe5-1.theplanet-2.003.dal.pnap.net (216.52.189.221) 1.557 ms 2.162
ms 2.662 ms
3 core1.ge1-0-0-bbnet2.ext1.dal.pnap.net (216.52.191.96) 1.719 ms 3.766 ms
1.125 ms
4 sl-gw40-fw-1-3.sprintlink.net (160.81.60.213) 1.953 ms 2.017 ms 1.926 ms
5 sl-bb22-fw-4-3.sprintlink.net (144.232.8.249) 117.321 ms 37.850 ms 12.940
ms
6 sl-bb20-atl-11-1.sprintlink.net (144.232.18.22) 17.640 ms 17.826 ms 19.94
2 ms
7 sl-bb20-nyc-10-0.sprintlink.net (144.232.8.89) 37.855 ms 37.475 ms 38.272
ms
8 sl-bb27-nyc-6-0.sprintlink.net (144.232.13.153) 50.966 ms 40.929 ms 38.12
6 ms
9 sl-gw31-nyc-1-0.sprintlink.net (144.232.13.34) 36.847 ms 39.277 ms 39.189
ms
10 sl-deutsche-3-0.sprintlink.net (144.223.27.134) 35.357 ms 36.120 ms 37.21
8 ms
11 F-EB1.F.DE.net.dtag.de (62.154.17.138) 119.272 ms * 120.428 ms
Something is still wrong with the routing tables. I suspect the only reason you are getting anywhere is due to the light load of traffic on the Internet.
EDIT: I just realized that hops 11 (second trace) and hops 16 (first trace) in the above traces is the same router, but 2 very different paths were taken to get there. This, in of itself, is not unusual, bu the fact that I started with a 217.x.x.x address and ended up going two different routes is bizarre and that both addresses I was tracing to are on the other side of this particular router makes this truly bizarre.
Hey Monk, take your traceroute and trace to the last one or two hops before the MA and see what happens. They should be the same paths, but if not, then there is more wrong than I suspected.
-
Thanks for the help Skuzzy, I guess we will wait and see.