Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: akkobek on October 21, 2005, 08:58:42 PM
-
I dont know how to get a picture of ping plotter so here goes.
I have 35 hops showing everything looks good unitl hop 15. At #16 it shows 63.241.250.227 at 17 is 63.241.250.225. It then alternates between those to until hop 35 where the graph ends never getting to 206.16.60.39. With packet loss starting at hop 23.
Any advice would be appreciated
-
Without seeing the trace, it is difficult to know where the actual problem lies.
Use the Windows 'tracert' utility in the command box (Start->Run->command), then type 'tracert 206.16.60.39' and press .
Then you can copy the results and paste it here.
-
Lets see if this will help
hop err pl avg
1 207.200.122.11 ipt-ntca11.dial.aol.com 117
2 207.200.120.30 iptfarmna-ntc-swo.net.aol.com 116
3 172.24.20.11 ------------ 116
4 66.185.142.117 pop1-ntc-p7-0-atdn.net 116
5 66.185.142.112 bbn-ntc-p1-0.atn.net 123
6 66.185.152.63 bb1-sjg-p6-0.atdn.net 130
7 66.185.150.81 pop1-sjg-po-o.atdn.net 117
8 66.185.150.90 att.atdn.net 119
9 12.122.81.102 -------------- 180
10 12.122.10.26 tbr1-cl3/la2ca.ip.att.net 183
11 12.122.10.49 tbr1-cl20.dlstx.ip.att.net 182
12 12.122.12.58 gbr1-p10-dlstx.ip.att.net 181
13 12.123.16.233 gar1-p360.dlstx.ip.att.net 177
14 12.122.255.170 mdf1-gsr12-2-pos-7-0.dal1.attens.net 177
15 63.241.192.230 mdf1-bi8k-1-eth-2-3.dal1.attnes.net 191
16 63.241.250.227------------- 192
17 63.241.250.225-------------- 192
18 63.241.250.227 ------------- 192
19 63.241.250.225 ------------- 187
20 63.241.250.227 ------------- 188
It repeats 16 & 17 until hop 35 hope this helps
-
I found the problem. It is in the path back to your computer. What you have here is an asynchronous route. The data is taking a different path back to your computer than it takes when it leaves your computer.
This causes strange things in traceroutes as traceroutes/pingplots cano only show the one path.
When I traced back to you, it was dieing in AOL's network, one hop before it could get to the gateway to you.
Here is the trace (started from 20.16.60.39). Notice I traced back to your hop #2, which is a router in AOL's network. I cannot get to it.
You need to point AOL at this post so they can find the problem.
=============
traceroute 207.200.120.30
traceroute to 207.200.120.30 (207.200.120.30), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.586 ms 0.507 ms 0.453 ms
2 mdf1-gsr12-1-gig-1-2.dal1.attens.net (63.241.192.205) 0.233 ms 0.268 ms 0.150 ms
3 gar1-p310.kc9mo.ip.att.net (12.122.255.173) 9.901 ms 9.730 ms 9.849 ms
4 tbr2-p012902.sl9mo.ip.att.net (12.122.2.210) 23.270 ms 22.988 ms 23.117 ms
5 tbr2-cl7.cgcil.ip.att.net (12.122.10.45) 22.807 ms 23.291 ms 22.721 ms
6 ggr2-p390.cgcil.ip.att.net (12.123.6.37) 23.665 ms 22.594 ms 22.112 ms
7 pop2-chi-P5-3.atdn.net (66.185.132.97) 22.256 ms 22.152 ms 22.018 ms
8 bb1-chi-P1-0.atdn.net (66.185.148.64) 21.758 ms 21.806 ms 21.760 ms
9 bb1-kcy-P6-0.atdn.net (66.185.152.125) 34.759 ms 34.667 ms 34.733 ms
10 bb2-kcy-P1-0.atdn.net (66.185.152.127) 34.733 ms 34.703 ms 34.749 ms
11 bb2-den-P7-0.atdn.net (66.185.152.188) 83.596 ms 83.514 ms 83.539 ms
12 bb1-den-P1-0.atdn.net (66.185.152.136) 85.594 ms 85.650 ms 85.450 ms
13 bb1-sun-P5-0.atdn.net (66.185.152.253) 73.704 ms 73.677 ms 73.670 ms
14 bb1-ntc-P4-0.atdn.net (66.185.152.88) 85.681 ms 85.606 ms 85.734 ms
15 pop1-ntc-P0-0.atdn.net (66.185.142.113) 85.787 ms 85.821 ms 85.975 ms
16 * * *
17 * * *
18 * * *
-
As you can see I am having a similar problem, but it still shows Savvis in the route. Is it the same thing as akkobek's problem? Thanks
1,10.22.0.1,12ms,,0
2,172.20.22.65,15ms,,0
3,172.26.22.1,20ms,,0
4,172.20.8.137,15ms,,0
5,203.117.6.53,21ms,,0
6,203.118.3.170,15ms,gi1-3-0-an-utl-int02.starhub.net.sg,0
7,129.250.11.85,201ms,p4-3-3-0.r03.sttlwa01.us.bb.verio.net,0
8,208.173.50.65,203ms,bpr4-so-5-2-0.SeattleSwitchDesign.savvis.net,0
9,208.172.83.66,225ms,acr2-so-0-0-0.Seattle.savvis.net,0
10,204.70.193.58,220ms,dcr2-so-1-0-0.Denver.savvis.net,0
11,204.70.193.62,221ms,dcr1-so-1-0-0.Denver.savvis.net,0
12,204.70.192.46,231ms,dcr2-so-5-0-0.Chicago.savvis.net,0
13,204.70.192.134,231ms,dcr1-so-7-0-0.Chicago.savvis.net,0
14,208.172.3.86,239ms,acr2-so-1-0-0.Chicago.savvis.net,0
15,0.0.0.0,20ms,,0
16,0.0.0.0,20ms,,0
17,0.0.0.0,20ms,,0
18,0.0.0.0,20ms,,0
19,0.0.0.0,20ms,,0
20,0.0.0.0,20ms,,0
21,0.0.0.0,20ms,,0
22,0.0.0.0,20ms,,0
23,0.0.0.0,20ms,,0
24,0.0.0.0,20ms,,0
25,0.0.0.0,20ms,,0
26,0.0.0.0,20ms,,0
27,0.0.0.0,20ms,,0
28,0.0.0.0,20ms,,0
29,0.0.0.0,20ms,,0
30,0.0.0.0,20ms,,0
-
What IP adress are you using in that trace?
-
216.91.187.39, is it the correct one?
-
FTJR, the new IP address is 206.16.60.39 - try tracing that one.
-
That works :) Sorry i didn't realise the ip address had changed. Thanks
-
here's mine.
I've been having difficulties since the move to the new server. My pings used to be around 250ms, now it's more then double and it's horrible. The location of the problems seems obvious but what do I do about it?
Tracing route to 206.16.60.39 over a maximum of 30 hops
1 18 ms 12 ms 13 ms c1.actcom.co.il [192.114.47.218]
2 13 ms 15 ms 12 ms rtr76.actcom.co.il [192.114.47.250]
3 20 ms 17 ms 17 ms 212.150.165.41
4 29 ms 27 ms 27 ms 62.90.133.169
5 20 ms 18 ms 19 ms 62.90.133.129
6 22 ms 18 ms 20 ms 212.150.232.125
7 203 ms * * 212.150.232.106
8 236 ms 203 ms * 212.150.232.94
9 426 ms 422 ms 450 ms 12.118.94.57
10 487 ms 407 ms 384 ms 12.122.82.138
11 390 ms 434 ms 445 ms tbr2-cl15.wswdc.ip.att.net [12.122.10.54]
12 357 ms 361 ms 370 ms 12.122.10.70
13 489 ms 485 ms 490 ms 12.122.9.158
14 522 ms 492 ms 512 ms 12.122.2.89
15 480 ms 458 ms 466 ms gbr2-p10.dlstx.ip.att.net [12.122.12.62]
16 484 ms 488 ms 491 ms gar1-p370.dlstx.ip.att.net [12.123.16.237]
17 469 ms 444 ms 432 ms mdf1-gsr12-2-pos-7-0.dal1.attens.net [12.122.255.170]
18 336 ms 318 ms 322 ms mdf1-bi8k-1-eth-2-1.dal1.attens.net [63.241.192.194]
19 525 ms 530 ms 537 ms 206.16.60.39
Trace complete.
thanks.
Bozon