Tracert - Something Neotel techies need to use

Venom Rush

Venom Rush

Expert Member
Joined
Sep 19, 2008
Messages
1,006
Reaction score
1
Clearly we need to do the work for Neotel. A month of this bulls**t is about all I can take. So let's give Neotel the results from our tracert tests.

How:
1. Click on Start menu and go to "Run".
2. Type in cmd and press Enter.
3. Type "tracert www.google.com" (without the inverted commas).
4. Right click on the window and click "select all".
5. Left click on the selected area (this copies the selected area).
6. Log into myBB and post your results here.

I will be doing this later tonight. What Neotel will finally realise from these results is that there is a problem with one of the Johannesburg server.
 
Hi all,

First off, my Neotel is acting up today, it's disconnected like 4x in a hour!
I did this at 6:15pm

tracert www.google.com

Tracing route to www.l.google.com [66.102.9.147]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 185 ms 612 ms 188 ms 41.174.0.1
4 160 ms 148 ms 278 ms 41.160.0.244
5 205 ms 243 ms 199 ms if-1-8.bb1.JSO-Johannesburg.as6453.net [216.6.55
.41]
6 370 ms 604 ms 404 ms if-1-7.bb2.JSO-Johannesburg.as6453.net [216.6.55
.10]
7 431 ms 413 ms 394 ms if-3-7.core2.LDN-London.as6453.net [216.6.59.34]

8 591 ms 352 ms 357 ms if-9-1.mcore3.LDN-London.as6453.net [195.219.195
.5]
9 402 ms 323 ms 489 ms ldn-b4-link.telia.net [213.248.74.1]
10 371 ms 369 ms 357 ms google-118150-ldn-b4.c.telia.net [213.248.104.58
]
11 366 ms 476 ms 332 ms 209.85.252.40
12 380 ms 368 ms 657 ms 209.85.250.216
13 413 ms 391 ms 476 ms 72.14.232.235
14 787 ms 401 ms 369 ms 64.233.174.14
15 340 ms 432 ms 336 ms lm-in-f147.google.com [66.102.9.147]

Trace complete.
 
I had a technician come over to my place today. He did a tracert test then, which was 5:20pm. This yielded similar results to yours gdiza. But try do a tracert test during 7:30pm/8pm and I guarantee you'll get results similar to the following:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>tracert www.google.com

Tracing route to www.l.google.com [66.102.9.104]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 245 ms 187 ms 506 ms 41.174.0.1
4 314 ms 323 ms 737 ms 41.160.0.244
5 188 ms 225 ms 202 ms if-1-8.bb1.JSO-Johannesburg.as6453.net [216.6.55.41]
6 1633 ms 1618 ms 1500 ms if-1-7.bb2.JSO-Johannesburg.as6453.net [216.6.55.10]
7 1489 ms 1463 ms 1566 ms if-3-7.core2.LDN-London.as6453.net [216.6.59.34]
8 1472 ms 1645 ms 1582 ms if-3-2.mcore3.LDN-London.as6453.net [195.219.195.13]
9 1606 ms 1714 ms 1908 ms ldn-b4-link.telia.net [213.248.74.1]
10 1538 ms 1593 ms 1570 ms google-118150-ldn-b4.c.telia.net [213.248.104.58]
11 1602 ms 1675 ms 2058 ms 209.85.252.40
12 1931 ms 2021 ms 2671 ms 209.85.251.190
13 1566 ms 1560 ms 1940 ms 72.14.232.237
14 1600 ms * 1840 ms 64.233.174.18
15 1670 ms 1710 ms 1739 ms lm-in-f104.google.com [66.102.9.104]

Trace complete.
Click to expand...

The problem lies with:
if-1-7.bb2.JSO-Johannesburg.as6453.net [216.6.55.10]

Every tracert test I've done has shown a problem with this server.
 
Tracing route to www.l.google.com [216.239.59.99]
over a maximum of 30 hops:

1 3 ms <1 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 68 ms 70 ms 80 ms 41.174.0.1
5 77 ms 59 ms 69 ms 41.160.0.244
6 63 ms 92 ms 76 ms if-1-8.bb1.JSO-Johannesburg.as6453.net [216.6.55.41]
7 1453 ms 1495 ms 1514 ms if-1-7.bb2.JSO-Johannesburg.as6453.net [216.6.55.10]
8 1520 ms 1536 ms 1537 ms if-3-7.core2.LDN-London.as6453.net [216.6.59.34]
9 1550 ms 1581 ms 1567 ms if-3-2.mcore3.LDN-London.as6453.net [195.219.195.13]
10 1642 ms 1571 ms 1573 ms ldn-b4-link.telia.net [213.248.74.1]
11 1544 ms 1516 ms 1576 ms google-118150-ldn-b4.c.telia.net [213.248.104.58]
12 1469 ms * 1399 ms 209.85.252.40
13 1379 ms 1387 ms * 209.85.251.190
14 * 1351 ms 1375 ms 66.249.95.169
15 * 1442 ms 1414 ms 216.239.49.114
16 1387 ms 1384 ms 1399 ms 216.239.59.99

Trace complete.

Emphasis placed by me

Now for a local address

Tracing route to www.neotel.co.za [196.34.133.113]
over a maximum of 20 hops:

1 <1 ms 2 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 76 ms 79 ms 69 ms 41.174.0.1
5 82 ms 71 ms 70 ms 41.160.0.244
6 67 ms 65 ms 128 ms is.jinx.net.za [198.32.142.10]
7 75 ms 60 ms 79 ms core5a-rba-gi1-0-0.ip.isnet.net [168.209.1.164]
8 75 ms 71 ms 80 ms core1a-bry-gi0-0-1-215.ip.isnet.net [168.209.0.98]
9 72 ms 79 ms 92 ms csw1-b-jup-bry-gi3-2.ip.isnet.net [168.209.218.21]
10 * * * Request timed out.
.
.
20 * * * Request timed out.

Trace complete.

Done at 20h15 in Robindale, Randburg on the Neoflex Data 10gb package.
 
It seems that they have resolved the bandwidth issues in my area, with several tests during the day giving a minimum of about 400kbps, and mostly around 500kbps+.

At 7:30pm I started noticing the international latency picking up gradually. Here are two tracerts I did to www.google.com. Note that the issue arises at if-1-7.bb2.JSO-Johannesburg.as6453.net each time. Before 7:30pm the international latency was around 300-400ms.

7:40pm
Code: 
Tracing route to www.l.google.com [66.102.9.104]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    43 ms    84 ms    79 ms  41.174.0.1
  5    48 ms    69 ms    50 ms  41.160.0.244
  6    81 ms    79 ms    74 ms  if-1-8.bb1.JSO-Johannesburg.as6453.net [216.6.55.41]
  7   913 ms   895 ms   876 ms  if-1-7.bb2.JSO-Johannesburg.as6453.net [216.6.55.10]
  8   864 ms   849 ms   839 ms  if-3-7.core2.LDN-London.as6453.net [216.6.59.34]
  9   858 ms   791 ms   819 ms  if-3-2.mcore3.LDN-London.as6453.net [195.219.195.13]
 10   844 ms   863 ms   867 ms  ldn-b4-link.telia.net [213.248.74.1]
 11   889 ms   889 ms   934 ms  google-118150-ldn-b4.c.telia.net [213.248.104.58]
 12     *      947 ms     *     209.85.252.40
 13   934 ms   922 ms     *     209.85.250.216
 14  1032 ms  1050 ms  1091 ms  72.14.232.235
 15  1193 ms  1214 ms  1212 ms  64.233.174.18
 16     *     1195 ms  1165 ms  lm-in-f104.google.com [66.102.9.104]

Trace complete.

8:30pm
Code: 
Tracing route to www.l.google.com [66.102.9.104]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    90 ms    78 ms    74 ms  41.174.0.1
  5    71 ms    74 ms    47 ms  41.160.0.244
  6    72 ms    78 ms    79 ms  if-1-8.bb1.JSO-Johannesburg.as6453.net [216.6.55.41]
  7  1421 ms  1455 ms  1409 ms  if-1-7.bb2.JSO-Johannesburg.as6453.net [216.6.55.10]
  8  1413 ms  1421 ms  1490 ms  if-3-7.core2.LDN-London.as6453.net [216.6.59.34]
  9  1412 ms  1450 ms  1419 ms  if-3-2.mcore3.LDN-London.as6453.net [195.219.195.13]
 10  1454 ms  1407 ms  1410 ms  ldn-b4-link.telia.net [213.248.74.1]
 11  1420 ms  1412 ms  1448 ms  google-118150-ldn-b4.c.telia.net [213.248.104.58]
 12  1418 ms  1454 ms  1452 ms  209.85.252.40
 13  1558 ms  1453 ms     *     209.85.250.216
 14  1478 ms  1451 ms  1368 ms  64.233.174.187
 15  1395 ms  1404 ms  1413 ms  64.233.174.18
 16  1361 ms     *     1340 ms  lm-in-f104.google.com [66.102.9.104]

Trace complete.
 
Robindale Randburg - Prime Device 9:00

]

Tracing route to www.l.google.com [66.102.9.104]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 3272 ms 809 ms 1445 ms 41.174.0.1
4 867 ms 314 ms 419 ms 41.160.0.244
5 2284 ms * 813 ms if-1-8.bb1.JSO-Johannesburg.as6453.net [216.6.55
.41]
6 4057 ms 3214 ms 1375 ms if-1-7.bb2.JSO-Johannesburg.as6453.net [216.6.55
.10]
7 * 1523 ms * if-3-7.core2.LDN-London.as6453.net [216.6.59.34]

8 * 1327 ms 1689 ms if-9-1.mcore3.LDN-London.as6453.net [195.219.195
.5]
9 2225 ms * * ldn-b4-link.telia.net [213.248.74.1]
10 2516 ms 1382 ms * google-118150-ldn-b4.c.telia.net [213.248.104.58
]
11 1584 ms 1394 ms 1392 ms 209.85.252.40
12 2481 ms 3217 ms * 209.85.250.216
13 1566 ms 1586 ms 1712 ms 72.14.232.235
14 1564 ms 1901 ms 1739 ms 64.233.174.18
15 2819 ms 2426 ms 1652 ms lm-in-f104.google.com [66.102.9.104]

Trace complete.
 
Paulshof, Sandton - NeoConnect Prime (21h25)
Tracing route to www.l.google.com [66.102.9.99]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 958 ms 2569 ms 2540 ms 41.174.0.1
4 1584 ms 960 ms 246 ms 41.160.0.244
5 1627 ms 618 ms 1202 ms if-1-8.bb1.JSO-Johannesburg.as6453.net [216.6.55.41]
6 2566 ms 2542 ms 2555 ms if-1-7.bb2.JSO-Johannesburg.as6453.net [216.6.55.10]
7 1675 ms 2574 ms 2542 ms if-3-7.core2.LDN-London.as6453.net [216.6.59.34]
8 2187 ms 2531 ms 2579 ms if-9-1.mcore3.LDN-London.as6453.net [195.219.195.5]
9 2595 ms 2521 ms 2574 ms ldn-b4-link.telia.net [213.248.74.1]
10 2532 ms 2595 ms 2523 ms google-118150-ldn-b4.c.telia.net [213.248.104.58]
11 2546 ms 2546 ms 2559 ms 209.85.252.40
12 1119 ms 2507 ms 1096 ms 209.85.251.190
13 1109 ms 2549 ms 2572 ms 64.233.174.187
14 1142 ms 1139 ms 2424 ms 64.233.174.18
15 1034 ms 1144 ms 2546 ms 66.102.9.99

Trace complete.
Click to expand...
 
These logs have also been handed over to the engineering team. Keep them coming please.

Side note: tracert is used among other commands / tools.
 
Robindale , Randburg - Prime Device - 10:08

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>tracert www.google.com
Unable to resolve target system name www.google.com.

C:\Documents and Settings\Administrator>tracert www.google.com

Tracing route to www.l.google.com [216.239.59.103]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * 691 ms * 41.174.0.1
4 3366 ms 760 ms 161 ms 41.160.0.244
5 306 ms 477 ms 3229 ms if-1-8.bb1.JSO-Johannesburg.as6453.net [216.6.55.41]
6 346 ms 351 ms 921 ms if-1-7.bb2.JSO-Johannesburg.as6453.net [216.6.55.10]
7 360 ms 364 ms 325 ms if-3-7.core2.LDN-London.as6453.net [216.6.59.34]
8 * 846 ms 319 ms if-9-1.mcore3.LDN-London.as6453.net [195.219.195
.5]
9 337 ms 302 ms * ldn-b4-link.telia.net [213.248.74.1]
10 1671 ms * 3533 ms google-118150-ldn-b4.c.telia.net [ 213.248.104.58]
11 339 ms 349 ms 352 ms 209.85.252.40
12 369 ms * * 209.85.250.216
13 2458 ms 1601 ms 994 ms 66.249.95.169
14 591 ms * 2968 ms 216.239.49.114
15 612 ms * * 216.239.59.103
16 691 ms 969 ms 1479 ms 216.239.59.103

Trace complete.
 
Robindale Randburg - Prime - 07:10 Am

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>tracert www.google.com

Tracing route to www.l.google.com [216.239.59.147]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 185 ms 277 ms 574 ms 41.174.0.1
4 191 ms 151 ms 163 ms 41.160.0.244
5 461 ms 297 ms 164 ms if-1-8.bb1.JSO-Johannesburg.as6453.net [216.6.55
.41]
6 337 ms 357 ms 349 ms if-1-7.bb2.JSO-Johannesburg.as6453.net [216.6.55
.10]
7 706 ms 387 ms 344 ms if-3-7.core2.LDN-London.as6453.net [216.6.59.34]

8 539 ms 338 ms 349 ms if-3-2.mcore3.LDN-London.as6453.net [195.219.195
.13]
9 360 ms 345 ms 328 ms ldn-b4-link.telia.net [213.248.74.1]
10 446 ms 378 ms 349 ms google-118150-ldn-b4.c.telia.net [213.248.104.58
]
11 409 ms 1046 ms 336 ms 209.85.252.40
12 323 ms 322 ms 366 ms 209.85.250.216
13 799 ms 352 ms 351 ms 72.14.232.241
14 449 ms 366 ms 359 ms 216.239.49.114
15 339 ms 490 ms 333 ms gv-in-f147.google.com [216.239.59.147]

Trace complete.

Speed still very slow
 
JMRHOWES, do a tracert test during peak hours when people have come home from work. 7:30pm/8pm is roughly when things start bottlenecking if not before then.
 
Venon Rush,

Would love to do it between the busy times, however the trace fails.

Check one of my posts.. You will see it says unable to resolve..
 
Hop 1 & 2 would be your device and first tower hops,I'd think they wouldn't respond to ping requests :P My telkom connection does the same to ping requests to the device
 
Robindale , Randburg

18:22

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>tracert www.google.com

Tracing route to www.l.google.com [216.239.59.103]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 132 ms 2007 ms 2563 ms 41.174.0.1
4 1768 ms 2562 ms 2589 ms 41.160.0.244
5 2565 ms 2549 ms 2571 ms if-1-8.bb1.JSO-Johannesburg.as6453.net [216.6.55
.41]
6 2551 ms 2555 ms 2563 ms if-1-7.bb2.JSO-Johannesburg.as6453.net [216.6.55
.10]
7 2554 ms 2560 ms 801 ms if-3-7.core2.LDN-London.as6453.net [216.6.59.34]

8 2372 ms 2555 ms 2550 ms if-9-1.mcore3.LDN-London.as6453.net [195.219.195
.5]
9 2554 ms 2567 ms 2560 ms ldn-b4-link.telia.net [213.248.74.1]
10 2559 ms 2559 ms 2559 ms google-118150-ldn-b4.c.telia.net [213.248.104.58
]
11 2559 ms 2564 ms 2561 ms 209.85.252.40
12 2555 ms 2553 ms 2554 ms 209.85.251.190
13 2567 ms 2559 ms 2573 ms 66.249.95.169
14 2561 ms 2556 ms 2557 ms 216.239.49.114
15 2567 ms 2561 ms 2552 ms 216.239.59.103

Trace complete.
 
Robindale Randburg

Prime Device

18:47

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>tracert www.google.com

Tracing route to www.l.google.com [216.239.59.99]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 1498 ms 2531 ms 2556 ms 41.174.0.1
4 2569 ms 2584 ms 2546 ms 41.160.0.244
5 2544 ms 2583 ms 2527 ms if-1-8.bb1.JSO-Johannesburg.as6453.net [216.6.55
.41]
6 2005 ms 2556 ms 2571 ms if-1-7.bb2.JSO-Johannesburg.as6453.net [216.6.55
.10]
7 2559 ms 2564 ms 2545 ms if-3-7.core2.LDN-London.as6453.net [216.6.59.34]

8 2561 ms 2569 ms 2560 ms if-3-2.mcore3.LDN-London.as6453.net [195.219.195
.13]
9 2558 ms 2568 ms 2554 ms ldn-b4-link.telia.net [213.248.74.1]
10 2560 ms 2558 ms 2567 ms google-118150-ldn-b4.c.telia.net [213.248.104.58
]
11 2565 ms 2560 ms 2540 ms 209.85.252.40
12 2576 ms 2551 ms 2418 ms 209.85.251.190
13 2043 ms 2542 ms 2573 ms 64.233.174.185
14 2553 ms 2569 ms 2554 ms 216.239.49.126
15 2562 ms 2556 ms * 216.239.59.99
16 2546 ms 2560 ms 2566 ms 216.239.59.99

Trace complete
 
Robindale, Randburg

Prime Device

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>tracert www.google.com

Tracing route to www.l.google.com [66.102.9.104]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 795 ms 711 ms 821 ms 41.174.0.1
4 1275 ms 917 ms 527 ms 41.160.0.244
5 595 ms 484 ms 1412 ms if-1-8.bb1.JSO-Johannesburg.as6453.net [216.6.55
.41]
6 1696 ms 2799 ms 3100 ms if-1-7.bb2.JSO-Johannesburg.as6453.net [216.6.55
.10]
7 * 3443 ms 3615 ms if-3-7.core2.LDN-London.as6453.net [216.6.59.34]

8 4161 ms 3699 ms 3653 ms if-9-1.mcore3.LDN-London.as6453.net [195.219.195
.5]
9 3113 ms * 4044 ms ldn-b4-link.telia.net [213.248.74.1]
10 3807 ms 3413 ms 3672 ms google-118150-ldn-b4.c.telia.net [213.248.104.58
]
11 3419 ms 3672 ms * 209.85.252.40
12 4086 ms 3767 ms * 209.85.251.190
13 * 4209 ms 3857 ms 64.233.174.187
14 1584 ms * * 64.233.174.14
15 1371 ms * 1425 ms lm-in-f104.google.com [66.102.9.104]

Trace complete.

I have had enough now
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X