IS Routing problem

timhaak

Active Member
Joined
Jul 11, 2005
Messages
74
Reaction score
12
Location
Centurion
Hi

Does anyone else have a problem with IS routing. Trying to get to a work server thats on a IS uncapped account at work from a IS capped account. Have not reached cap but that should not be a problem either as its local to local. Also have tested to see if I can get to the server from a US server and can.

This has been going on since last week (possibly longer as only became aware of it then)

Anyone have any ideas?

Trying to get to 196.213.94.50 from 196.209.18.83

Traceroute from SA

traceroute to 196.213.94.50 (196.213.94.50), 30 hops max, 60 byte packets
1 192.168.200.1 (192.168.200.1) 1.727 ms 1.945 ms 2.256 ms
2 * * *
3 cdsl1-rba-vl2253.ip.isnet.net (196.38.73.181) 57.103 ms 67.478 ms 76.884 ms
4 curp1-rba-gi2.isdsl.net (196.38.72.238) 88.245 ms 99.299 ms 109.412 ms
5 cdsl1-rba-vl43.ip.isnet.net (196.38.72.229) 117.833 ms 126.835 ms 137.397 ms
6 clns5-rba.isdsl.net (196.35.63.66) 147.075 ms 26.023 ms 35.423 ms
7 196-209-18-80-tvwt-esr-2.dynamic.isadsl.co.za (196.209.18.80) 423.760 ms 424.124 ms 424.370 ms
8 * * *
9 * * *

Traceroute from US

traceroute to 196.213.94.50 (196.213.94.50), 30 hops max, 40 byte packets
1 64.151.70.1.servepath.com (64.151.70.1) 0.396 ms 0.396 ms 0.439 ms
2 vl23.border-core2.sfo2.servepath.com (208.96.31.65) 0.369 ms 0.427 ms 0.493 ms
3 ge-6-4.r04.plalca01.us.bb.gin.ntt.net (140.174.41.101) 2.454 ms 2.520 ms 2.552 ms
4 xe-0-3-0.r21.plalca01.us.bb.gin.ntt.net (129.250.4.121) 1.252 ms 1.315 ms 1.369 ms
5 ae-1.r20.snjsca04.us.bb.gin.ntt.net (129.250.5.33) 2.575 ms 2.605 ms 2.603 ms
6 p64-1-3-0.r21.chcgil09.us.bb.gin.ntt.net (129.250.5.21) 67.942 ms 67.941 ms 67.505 ms
7 ae-0.r20.chcgil09.us.bb.gin.ntt.net (129.250.3.97) 62.754 ms 62.749 ms 62.698 ms
8 as-1.r21.nycmny01.us.bb.gin.ntt.net (129.250.6.14) 87.068 ms 87.058 ms 87.033 ms
9 ae-0.r20.nycmny01.us.bb.gin.ntt.net (129.250.2.25) 82.659 ms p16-3-0-0.r01.nycmny03.us.bb.gin.ntt.net (129.250.3.85) 82.703 ms ae-0.r20.nycmny01.us.bb.gin.ntt.net (129.250.2.25) 82.613 ms
10 po-2.r02.nycmny03.us.bb.gin.ntt.net (129.250.5.102) 87.024 ms p16-2-0-0.r00.nycmny03.us.bb.gin.ntt.net (129.250.3.83) 83.238 ms 83.147 ms
11 ge-3-11.r02.nycmny03.us.ce.gin.ntt.net (129.250.192.214) 82.214 ms ge-3-0-0.r00.nycmny03.us.ce.gin.ntt.net (129.250.192.218) 82.246 ms ge-3-11.r02.nycmny03.us.ce.gin.ntt.net(129.250.192.214) 81.985 ms
12 core2a-ny-gi1-0-10-13.ip.isnet.net (168.209.247.22) 86.531 ms 86.549 ms 86.498 ms
13 168.209.0.241 (168.209.0.241) 726.109 ms 726.048 ms 726.087 ms
14 cdsl1-rba-gi0-2.isdsl.net (196.26.96.197) 566.450 ms 566.657 ms 566.551 ms
15 clns5-rba.isdsl.net (196.35.63.66) 568.022 ms 567.927 ms 568.366 ms
16 196.213.122.174 (196.213.122.174) 621.720 ms 615.764 ms 602.383 ms
17 labmail.lucidview.net (196.213.94.50) 615.645 ms 617.049 ms 623.445 ms

Tim
 
Not that this really helps much, but I'm on SAIX and it works fine, so defn an IS problem.

Tracing route to 196.213.94.50 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 172.19.50.253
2 8 ms 8 ms 7 ms 165.146.248.1
3 8 ms 8 ms 8 ms 196.43.8.190
4 9 ms 8 ms 8 ms 196.43.25.206
5 9 ms 9 ms 8 ms 196.25.247.26
6 10 ms 9 ms 8 ms 168.209.2.7
7 35 ms 34 ms 34 ms 168.209.100.153
8 35 ms 34 ms 35 ms 168.209.1.175
9 35 ms 34 ms 35 ms 196.35.63.66
10 160 ms 245 ms 309 ms 196.213.122.174
11 334 ms 229 ms 269 ms 196.213.94.50

Cheers!
 
Thanks :). Should from what I understand be IS to IS so weird that there own internal routing is broken.
 
Nothing weird about that... ;) their network is full of "tweaked" routing that has started causing problems all over the place, plus the fact that they are horribly over subscribed. Nothing beats SAIX at the moment I'm afraid
 
Ah well looks like I will be moving to a SAIX account as of next month. Pitty have a 12 month contract at work with IS.
 
Top
Sign up to the MyBroadband newsletter
X