Can this IP route be reconfigured?

  • Thread starter Thread starter redrosekrs
  • Start date Start date
R

redrosekrs

I have an issue with the support team at my work but nothing is
getting resolved and it's been several months. I'm wondering what
needs/can be done.

I'm trying to access a server.. and I've tried it from 3 locations

Location 1- it goes from:
10.12.30.xx
10.12.38.xx
10.12.48.xx
Total average ping time = 2ms


Location 2- it goes from:
10.12.54.xx
10.12.79.xx
10.12.127.xx
10.12.63.xx
10.12.38.xx
10.12.48.xx
Total average ping time = 10ms

Location 3- it goes from:
10.15.227.xx
10.15.53.xx
10.15.53.xx
10.15.153.xx
10.15.186.xx
10.15.186.xx
10.27.16.xx
10.27.16..xx
10.12.48.xx
10.12.30.xx
10.12.38.xx
10.12.48.xx
Total average ping time = 96ms


Location 2 is the furthest away (around 100 miles) and Location 1 and
3 are very close. Why is location 3 going through all of these extra
hops??

Thanks.
 
(e-mail address removed) wrote in
I have an issue with the support team at my work but nothing is
getting resolved and it's been several months. I'm wondering what
needs/can be done.

I'm trying to access a server.. and I've tried it from 3 locations

Location 1- it goes from: [...]
Total average ping time = 2ms


Location 2- it goes from: [...]
Total average ping time = 10ms

Location 3- it goes from: [...]
Total average ping time = 96ms

Location 2 is the furthest away (around 100 miles) and Location 1 and
3 are very close. Why is location 3 going through all of these extra
hops??
Click to expand...

A "ping" will not show hops, only round-trip delays.
Rather than doing a "Ping", you need to do a "Traceroute":
tracert <ip address>

The output of a traceroute will show you all the hops between source
and destination and the delays associated with each hop. You can then
identify the hop that is causing the delay.

HTH,
John
 
(e-mail address removed) wrote in
I have an issue with the support team at my work but nothing is
getting resolved and it's been several months. I'm wondering
what needs/can be done.

I'm trying to access a server.. and I've tried it from 3
locations

Location 1- it goes from: [...]
Total average ping time = 2ms


Location 2- it goes from: [...]
Total average ping time = 10ms

Location 3- it goes from: [...]
Total average ping time = 96ms

Location 2 is the furthest away (around 100 miles) and Location 1
and 3 are very close. Why is location 3 going through all of
these extra hops??
Click to expand...

A "ping" will not show hops, only round-trip delays.
Rather than doing a "Ping", you need to do a "Traceroute":
tracert <ip address>

The output of a traceroute will show you all the hops between
source and destination and the delays associated with each hop.
You can then identify the hop that is causing the delay.
Click to expand...

After re-reading, I see you are doing a traceroute. (I thought you were
pinging from all those addresses and generationg an average.)
It appears that the first couple of routers from Location 3 often look
back on themselves but you have to remember that each step of a
traceroute is an independent event and routes can change each time...
so while it may look like things are in a loop, they probably aren't.
My guess: either you have a very heavily loaded router in the 10.15.x.x
subnet or a router needs to be reset.
-- john
 
I have an issue with the support team at my work but nothing is
getting resolved and it's been several months. I'm wondering what
needs/can be done.

I'm trying to access a server.. and I've tried it from 3 locations

Location 1- it goes from:
10.12.30.xx
10.12.38.xx
10.12.48.xx
Total average ping time = 2ms


Location 2- it goes from:
10.12.54.xx
10.12.79.xx
10.12.127.xx
10.12.63.xx
10.12.38.xx
10.12.48.xx
Total average ping time = 10ms

Location 3- it goes from:
10.15.227.xx
10.15.53.xx
10.15.53.xx
10.15.153.xx
10.15.186.xx
10.15.186.xx
10.27.16.xx
10.27.16..xx
10.12.48.xx
10.12.30.xx
10.12.38.xx
10.12.48.xx
Total average ping time = 96ms


Location 2 is the furthest away (around 100 miles) and Location 1 and
3 are very close. Why is location 3 going through all of these extra
hops??

Thanks.
Click to expand...

Without knowing how the network is configured it's impossible to say,
but if all of the routers on the 10.15 network are on the same subnet
(mask 255.255.0.0), it would appear that there is a misconfiguration in
a routing protocol, or a core piece of the mesh is missing. If they're
on different subnets (mask 255.255.255.0), then it's entirely possible
that there are just that many routers in the path. Since you didn't post
the times, we can't see where the big delay is. Likely on a DSL, T1, or
other WAN hop.


....kurt
 
Thanks Kurt and John..

Sorry for making this diagonosis a little difficult but I'm not sure
if it's safe to put my companie's internal IP addresses on the
Internet.. just in case someone wants to hack it..

Here are the corresponding tracert times that appear to the left of
the IP addresses:

1ms 10.15.227.xx
<10ms 10.15.53.xx
<10ms 10.15.153.xx
1ms 10.15.186.xx
75ms 10.15.186.xx
75ms 10.27.16.xx
75ms 10.27.16..xx
91ms 10.12.48.xx
92ms 10.12.30.xx
94ms 10.12.38.xx
92ms 10.12.48.xx

Good suggestion about reseting a router.. I wonder if that would
help... Or maybe it's a routing table issue? I work for a large
corporation and the company server that I'm trying to access is from
one sub-company to another sub-company.. and the servers can be all
over the US.. so it is definitely complex..
 
Thanks Kurt and John..

Sorry for making this diagonosis a little difficult but I'm not sure
if it's safe to put my companie's internal IP addresses on the
Internet.. just in case someone wants to hack it..

Here are the corresponding tracert times that appear to the left of
the IP addresses:

1ms 10.15.227.xx
<10ms 10.15.53.xx
<10ms 10.15.153.xx
1ms 10.15.186.xx
75ms 10.15.186.xx
75ms 10.27.16.xx
75ms 10.27.16..xx
91ms 10.12.48.xx
92ms 10.12.30.xx
94ms 10.12.38.xx
92ms 10.12.48.xx

Good suggestion about reseting a router.. I wonder if that would
help... Or maybe it's a routing table issue? I work for a large
corporation and the company server that I'm trying to access is from
one sub-company to another sub-company.. and the servers can be all
over the US.. so it is definitely complex..
Click to expand...

The full IP addresses aren't needed (they're private anyway, used by
thousands upon thousands of companies), but the subnet mask would be
useful, otherwise there's no way to tell if 10.15.227.x and 10.15.53.x
are on the same subnet or not (i suspect not). The big delay is at the
5th hop - between the first 10.15.186 router and the second, you pick up
over 80% of your latency at that hop. Even so, unless you're running
time-critical stuff (like VoIP) across that link, 91ms isn't all that
terrible. DSL typically has 60 - 80ms and often in the 90s. And if
latency is the only issue, even VoIP can be configured to handle it by
increasing the buffer size at the expense of a tad bit more delay.

....kurt

....kurt
 
Back
Top