Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Anaxogoras on February 23, 2009, 01:21:28 AM
-
I was discoed tonight for the first time in months. Although I'm a comcast user, I'm one of the lucky ones who doesn't have problems with their service. I got the "lost udp" message, and lost the connection within a few seconds of "switching to tcp."
C:\Documents and Settings\Compaq_Owner>tracert 206.16.60.38
Tracing route to 206.16.60.38 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 10 ms 9 ms 12 ms ge-1-2-ur01.lafayette.in.indiana.comcast.net [68.85.178.193]
4 9 ms 11 ms 9 ms 68.85.176.237
5 22 ms 23 ms 21 ms 68.85.177.46
6 27 ms 25 ms 26 ms be-10-ar01.area4.il.chicago.comcast.net [68.87.229.109]
7 29 ms 25 ms 29 ms pos-0-6-0-0-cr01.chicago.il.ibone.comcast.net [68.86.90.53]
8 28 ms 25 ms 26 ms po-0-1-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.38]
9 40 ms 27 ms 25 ms 208.173.180.45
10 27 ms 27 ms 26 ms ber2-vlan-240.chicagoequinix.savvis.net [204.70.194.230]
11 25 ms 26 ms 26 ms savvis-gw.cgcil.ip.att.net [192.205.35.41]
12 94 ms 90 ms 91 ms cr2.cgcil.ip.att.net [12.122.132.138]
13 93 ms 95 ms 90 ms cr2.sl9mo.ip.att.net [12.122.2.22]
14 92 ms 90 ms 90 ms cr1.sl9mo.ip.att.net [12.122.2.217]
15 104 ms 90 ms 100 ms cr2.dlstx.ip.att.net [12.122.3.221]
16 90 ms 94 ms 92 ms gar5.dlstx.ip.att.net [12.122.138.5]
17 94 ms 90 ms 187 ms 12.122.255.226
18 106 ms 90 ms 90 ms mdf1-bi8k-1-eth-1-2.dal1.attens.net [63.241.192.202]
19 103 ms 90 ms 91 ms 206.16.60.38
Trace complete.
-
So far you are not being routed through Level3.
Seems your router might need to be power cycled though.
-
I also have comcast internet and I had called in multiple times about ping rates, packet loss and routing problems, on my last phone conversation I was able to talk to a tier II supervisor, he was helpful. I had emailed him my ping plots traces on three of the HTC Io's the responce is that ATT net is the problem, if you look at your own trace route when does your ping rate go up, as soon as it hits the att hubs. The comcast supervisor I had talked to said they would gladly help but att net will not cooperate with them saying that there is nothing wrong with there system.
I have a question does HTC use att net services and if you guys do why don't you talk to them and find out why they do not seem to be addressing this issue.
-
Because it is a Comcast issue.
Here is the trace back to you Anaxogoras
===
traceroute 68.85.178.193
traceroute to 68.85.178.193 (68.85.178.193), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.610 ms 0.544 ms 0.477 ms
2 mdf1-gsr12-1-gig-1-1.dal1.attens.net (63.241.192.201) 0.329 ms 0.313 ms 0.256 ms
3 gar5.dlstx.ip.att.net (12.122.255.225) 1.329 ms 1.430 ms 1.148 ms
4 cr1.dlstx.ip.att.net (12.122.139.6) 2.060 ms 1.449 ms 1.321 ms
5 ggr3.dlstx.ip.att.net (12.122.139.21) 1.208 ms 1.249 ms 1.225 ms
6 bcr2-so-6-0-0.Dallas.savvis.net (208.172.139.225) 1.538 ms 1.525 ms 1.328 ms
7 cr2-tengig-0-7-0-0.losangeles.savvis.net (204.70.196.154) 34.060 ms 34.218 ms 33.778 ms
8 er2-tengig-3-1.lay.savvis.net (204.70.198.10) 33.814 ms 33.904 ms 33.811 ms
9 208.172.41.162 (208.172.41.162) 34.621 ms 34.717 ms 34.470 ms
10 pos-0-15-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.138) 69.052 ms 69.168 ms 69.018 ms
11 pos-0-9-0-0-cr01.nashville.tn.ibone.comcast.net (68.86.85.22) 69.793 ms 70.212 ms 69.634 ms
12 pos-0-11-0-0-ar01.indianapolis.in.indiana.comcast.net (68.86.90.170) 79.530 ms 79.588 ms 79.633 ms
13 be-30-ar01.elmhurst.il.chicago.comcast.net (68.87.231.113) 68.228 ms 67.908 ms 67.892 ms
14 68.85.177.45 (68.85.177.45) 81.040 ms 81.046 ms 81.009 ms
15 * * *
16 * * *
The people you are talking to at Comcast either have no idea what an asynchronous route is, or they are just wanting to get you off the phone.
Check the above routing.
Once out of AT&T's network in Dallas,
The packet travels to Los Angeles, for two hops.
Then back to Dallas.
Then to Tennessee
Then to Indiana
and finally to Chicago.
I happen to know from Dallas to Chicago should only be two three hops, if the routing is done. correctly.
Comcast fixed one side of the problem and still have not fixed the other side of the issue. Unfortunately, you can only show them the path to the servers. In order to see the path back to you, I have to run the trace. All packets travel in an asynchronous route for the servers. AT&T has it configured that way. It means the path to your computer is guaranteed to be different than the path from your computer.
-
Ahhhh, thanks for that information skuzzy! I had no idea the rout back was so zig-zagged.
Going from Indianapolis to Chicago to get to Lafayette is unbelievable. :confused:
-
How do I get this to print out? My tracert program runs, but then disappears after the sequence runs. I've got AT&T DSL from Nevada, so I'd like to provide some information.
-
Open a "command" (Start->Run->command) box, then type "tracert 206.16.60.38 >text.txt" this will route the output to a text file. Open the text file with Notepad/Wordpad, select all the data, and copy (CTRL-INSERT) it to the Windows clipboard.
Open the forums, start a post, hit SHIFT-INSERT to insert the text to the post.
-
been trying to log in to play the past couple of days, only to find that all the bases in the clipboard map are green and udp packet loss happens before disconnecting. used to be able to play, maybe i'm going to have to ditch comcast now.
they promised a technician visit this pm. if he doesn't show up im signing up with at&t.
Tracing route to 206.16.60.38 over a maximum of 30 hops
1 10 ms 8 ms 21 ms NUKESTRIKERONE [0.0.0.0]
2 10 ms 9 ms 10 ms ge-2-26-ur02.almeda.tx.houston.comcast.net [68.85.249.237]
3 12 ms 9 ms 10 ms po-11-ur01.almeda.tx.houston.comcast.net [68.85.244.21]
4 13 ms 10 ms 10 ms po-12-ur02.pike.tx.houston.comcast.net [68.85.244.26]
5 10 ms 13 ms 12 ms po-11-ur01.pike.tx.houston.comcast.net [68.85.244.29]
6 12 ms 12 ms 17 ms po-14-ar02.bearcreek.tx.houston.comcast.net [68.85.244.33]
7 15 ms 12 ms 13 ms po-16-ar01.greenspoint.tx.houston.comcast.net [68.85.244.73]
8 13 ms 11 ms 17 ms po-12-ar02.greenspoint.tx.houston.comcast.net [68.85.244.154]
9 20 ms 22 ms 21 ms te-0-1-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.91.49]
10 54 ms 53 ms 53 ms pos-0-15-0-0-cr01.losangeles.ca.ibone.comcast.net [68.86.85.137]
11 51 ms 53 ms 51 ms 208.173.55.217
12 54 ms 53 ms 53 ms cr1-tengig-0-5-0-0.lay.savvis.net [204.70.198.5]
13 228 ms 53 ms 53 ms ber1-tenge-2-1.losangeles.savvis.net [204.70.193.106]
14 54 ms 54 ms 54 ms 208.174.194.66
15 87 ms 85 ms 86 ms cr2.la2ca.ip.att.net [12.123.30.134]
16 94 ms 87 ms 89 ms cr2.dlstx.ip.att.net [12.122.28.177]
17 84 ms 86 ms 86 ms gar5.dlstx.ip.att.net [12.122.138.5]
18 87 ms 85 ms 86 ms 12.122.255.226
19 87 ms 87 ms 87 ms 63.241.192.250
20 86 ms 86 ms 86 ms 206.16.60.38
Trace complete.
-
I'm another Comcast cable customer in Oregon. Does my traceroute below reveal anything new regarding these connection problems??
I always get request timed out for hops 9,10, and 11, for some reason.
Here it is:
C:\DOCUME~1\OWNER~1.YOU>tracert 206.16.60.38
Tracing route to 206.16.60.38 over a maximum of 30 hops
1 10 ms 7 ms 8 ms 73.90.26.1
2 9 ms 11 ms 8 ms 68.85.148.129
3 7 ms 7 ms 10 ms te-9-1-ur02.hillsboro.or.bverton.comcast.net [68.87
.216.66]
4 10 ms 11 ms 12 ms te-7-3-ar01.troutdale.or.bverton.comcast.net [68
.87.216.126]
5 15 ms 16 ms 17 ms te-0-4-0-6-cr01.seattle.wa.ibone.comcast.net [68
.86.90.225]
6 18 ms 30 ms 16 ms pos-0-8-0-0-cr01.portland.or.ibone.comcast.net [
68.86.85.206]
7 30 ms 30 ms 29 ms pos-1-14-0-0-cr01.sacramento.ca.ibone.comcast.ne
t [68.86.85.201]
8 32 ms 32 ms 31 ms pos-0-8-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.85.78]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 78 ms 75 ms 76 ms cr2.sffca.ip.att.net [12.122.136.122]
13 78 ms 75 ms 79 ms cr2.la2ca.ip.att.net [12.122.31.133]
14 80 ms 75 ms 76 ms cr2.dlstx.ip.att.net [12.122.28.177]
15 75 ms 75 ms 75 ms gar23.dlstx.ip.att.net [12.122.138.161]
16 76 ms 75 ms 75 ms 12-122-254-154.attens.net [12.122.254.154]
17 86 ms 76 ms 79 ms mdf1-bi8k-1-eth-2-2.dal1.attens.net [63.241.192.
226]
18 75 ms 75 ms 75 ms 206.16.60.38
Trace complete.
-
Those packets are turning in circles before ever going anywhere...
Your packets are going from Hillsboro (OR), to Troutdale (OR), then to Seattle (WA), then to Portland (OR), then to Sacramento (CA), then to San Jose (CA), and then finally to Dallas (TX). I'm pretty sure the trace back to you looks rather nasty as well.
Here's a quick trace back to you:
Target Name: N/A
IP: xx.xx.xx.x
Date/Time: 5/27/2009 8:37:18 AM to 5/27/2009 8:38:17 AM
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 30 0 0.0 0 1 0 home [xxx.xxx.x.xxx]
2 30 0 0.0 47 52 49 ppp-xx-xxx-xxx-xxx.dsl.rcsntx.swbell.net [xx.xxx.xxx.xxx]
3 30 1 3.3 47 70 49 [70.245.63.3]
4 30 0 0.0 47 204 58 bb2.10g3-0.rcsntx.sbcglobal.net [151.164.243.97]
5 30 0 0.0 48 204 55 ex2-p2-0.eqdltx.sbcglobal.net [151.164.240.225]
6 30 0 0.0 47 69 51 asn3561-savvis.eqdltx.sbcglobal.net [151.164.89.210]
7 30 0 0.0 47 55 50 pr2-ge-3-0-0.dallasequinix.savvis.net [204.70.204.150]
8 30 7 23.3 49 53 50 [204.70.200.170]
9 30 1 3.3 81 91 83 cr1-tengig-0-7-0-0.losangeles.savvis.net [204.70.196.153]
10 30 0 0.0 80 99 83 er2-tengig-2-1.lay.savvis.net [204.70.198.6]
11 30 30 100.0 0 0 0 [-]
12 30 30 100.0 0 0 0 [-]
13 30 30 100.0 0 0 0 [-]
14 30 30 100.0 0 0 0 [-]
15 30 30 100.0 0 0 0 [-]
16 30 30 100.0 0 0 0 [-]
17 30 30 100.0 0 0 0 [-]
18 30 30 100.0 0 0 0 [-]
19 30 30 100.0 0 0 0 [-]
20 30 30 100.0 0 0 0 [-]
21 30 30 100.0 0 0 0 [-]
22 30 30 100.0 0 0 0 [-]
23 30 30 100.0 0 0 0 [-]
24 30 30 100.0 0 0 0 [-]
25 30 30 100.0 0 0 0 [-]
26 30 30 100.0 0 0 0 [-]
27 30 30 100.0 0 0 0 [-]
28 30 30 100.0 0 0 0 [-]
29 30 30 100.0 0 0 0 [-]
30 30 30 100.0 0 0 0 [-]
31 30 30 100.0 0 0 0 [-]
32 30 30 100.0 0 0 0 [-]
33 30 30 100.0 0 0 0 [-]
34 30 30 100.0 0 0 0 [-]
35 30 30 100.0 0 0 0 [-]
Destination not reached in 35 hops
I live just a few miles south of HTC. While this is not what it will look like from the HTC network, I'm still within the AT&T network. That trace has trouble written all over it.
-
Actually Denhom, your traces show the same problem with Comcast as ours does. Comcast and Savvis are doing a bang-up job of obfuscating routes these days.
Neither one appears interested in fixing the problems. We are in progress of trying something with AT&T. Watch the front page for news about it. It may or may not fix anything. It definately will not fix Comcasts own internal routing problems.
-
Not to be difficult....... because Im sure this is an issue youve dealt with many many times and are familiar with......
however, always saying its the other guy and their ISP must be giving them the runaround is the pot talking to the kettle in a sense
I dont disco that often ........ maybe 2-3 times a month..........
but everytime I disco I quickly jump to ping plotter to see where the problem is....... and 99% of the time the problem comes from the last ATT hop before it hits your server 63.241.192.210
just ran one as I type this and that IP is the weakest point on the route....... so maybe ATT is to blame as well
-
It's only showing the trace to the HTC servers. The route back might be the actual problem.
-
Correct. The last hop is a switch, and it will not drop packets. It is a limitation of traceroutes/Ping Plots. They can only show the one direction. I have to run it back to you for you to see the path back to your computer, which is always different than the path to the server. If the error is on the return trip, it shows as a problem on the very last or next to the last hops of the traceroute/Ping Plot due to the uni-directional limitation they have.
Think about it. We have no reason to lie and every reason to get things fixed. This impacts our very livelihood. AT&T is not perfect and I have been known to lambast them as well, when they fat-finger things.
You can bank on the following: At any given minute of the day, there is a problem somewhere on the Internet.
Normally, these things last a minute or two, and most people run along oblivious to the fact thier ISP just panic rebooted thier routers. On the rare occasion when extended outages happen, they do cause a mess as all the routers get busy trying to get around the impacted areas.
Then there are event related issues. At certain times of the year, the Internet just gets nasty. Events such as school being let out for the summer, school starting in the fall, the month of December, spring break and so on. Like clock work, the Internet is always a mess during worldwide or nationwide events.