How can this be??

[BlackLoti]

Tracert'ing the countesrtrike server i play at from my machine (machine 2) does this:

8 50 ms 20 ms 20 ms pos2-0-155M.cr2.WDC2.gblx.net [208.178.174.61]
9 30 ms 30 ms 30 ms pos4-0-622M.cr2.BOS1.gblx.net [206.132.249.253]

10 20 ms 20 ms 80 ms pos1-0-0-155M.ar1.BOS1.gblx.net [206.132.247.54]

11 130 ms 130 ms 131 ms GlobalNaps.s11-1-0.ar1.BOS1.gblx.net [209.143.20
.42]
12 130 ms 110 ms 191 ms f2-0-vL2.ar2.qui.cent.net [199.232.77.8]
13 150 ms 130 ms 140 ms link74-102.cent.net [199.232.74.102]

Machine #3 also shows the same thing. Machine #1 on the network zings right through without a hitch at hop 11.

How can this be?? Machine 1 and 3 are running win98, machine2 has win2K. that can't be the problem.

they both take the same route along the way. any help woudl be appreciated.

[BlackLoti]

swapped IP's on two machines. whichever machine is hosting the main IP of the house does not spike at hop 11. the other purchased IP's do however.

[BlackLoti]

anyone?

[YeOldeStonecat]

If you swapped IP's, and a particular IP always takes the longer or shorter route, then it's the way your ISP handles that IP. Do you have the exact same DNS servers, in the same order, on all 3?

[Kip Patterson]

The first question is whether the spike is real. The variability in your pings approaches the size of the spike, so it may be an artifact.

If it is real, then the difference results from differences in the routing tables on the path BACK to your IP. Take a look at the full route - does the spike show up on all routers after 11, and are those routers on different Autonomous systems? If so, then the problem is likey to be near your end. Not much you can do to figure it out because there is no way of tracing backwards.

I'd call my ISP, ask them to put the second IP in the same group as the first. Good luck getting them to understand the issue.

Kip Patterson

[ 02-03-2001: Message edited by: Kip Patterson ]