We help IT Professionals succeed at work.

Last 3 hops of a traceroute are the exact same address, why?

denver218
denver218 asked
on
6,136 Views
Last Modified: 2013-11-13
If I do a traceroute from my office to one of my customer locations it finishes fine, but the last three hops are the exact same public IP.  This public IP is NAT'ed to a Server on the network.   Does it show up three times because thats the amount of hops from the firewall to the server? I have a complete cisco infrastucture.  Below is my traceroute:  See the last three hops:

C:\>tracert xx.124.54

Tracing route to x.x.124.54 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  10.0.0.2
  2     1 ms     1 ms     1 ms  hx.x.x.74.static.ip.windstream.net [x.x.x.129]
  3    25 ms    23 ms     2 ms  hx.x.x.66.static.ip.windstream.net [x.x.x.129]
  4    36 ms     2 ms     2 ms  hx.x.x.x.66.static.ip.windstream.net [x.x.x.113]
  5    19 ms    26 ms     3 ms  hx.x.x.173.static.ip.windstream.net [173.189.232.113]
  6    72 ms    34 ms    29 ms  h19.236.109.66.static.ip.windstream.net [66.109.236.19]
  7    30 ms    49 ms    53 ms  h96.254.213.151.static.ip.windstream.net [151.213.254.96]
  8    53 ms    53 ms    54 ms  h11.254.213.151.static.ip.windstream.net [151.213.254.11]
  9    47 ms    47 ms    51 ms  h13.254.213.151.static.ip.windstream.net [151.213.254.13]
 10    74 ms    88 ms    56 ms  ip65-47-204-81.z204-47-65.customer.algx.net [65.47.204.81]
 11    60 ms    70 ms    89 ms  207.88.14.238.ptr.us.xo.net [207.88.14.238]
 12    88 ms   105 ms    81 ms  vb24.rar3.washington-dc.us.xo.net [207.88.12.34]
 13    91 ms    68 ms    86 ms  ae0d0.mcr1.philadelphia-pa.us.xo.net [216.156.0.42]
 14    62 ms    63 ms   103 ms  ae1d0.mcr2.philadelphia-pa.us.xo.net [216.156.1.22]
 15    75 ms   100 ms   103 ms  x.x.8.158.ptr.us.xo.net [x.x.8.158]
 16    72 ms    82 ms   110 ms  ipx-47-x-x.z113-x-65.customer.algx.net [x.x.x.118]
 17    80 ms   108 ms   108 ms  x.x.124.54
 18    88 ms   101 ms   107 ms  x.x.124.54
 19    78 ms    96 ms    103 ms  x.x.124.54

Trace complete.
You will see that the last three hops are the exact same IP.  This IP is the public address of a Server I have Nat'ed.  I'm just looking for an explanation of why the last 3 hops are the same IP.  Thanks.

 

Comment
Watch Question

Adrian CantrillSolutions Architect
CERTIFIED EXPERT

Commented:
Check the routing on the box which is natting, it may be that its bouncing between interfaces.

Author

Commented:
I have a Cisco ASA5510 doing the natting.  I have one route outside statement that goes to my router that connects to the ISP.  I also have route inside statements for my internal networks.  
Adrian CantrillSolutions Architect
CERTIFIED EXPERT

Commented:
That explains it then, its just that the route the packets are taking are being natted to the external interface address if your NAT box.. nothing to worry about.

Author

Commented:
Can you explain a little further, I'm still not completely sure why the last three hops are the same IP address.  Thanks.
Solutions Architect
CERTIFIED EXPERT
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
Top Expert 2010
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
OK, so this is normal and nothing to worry about right?  
Top Expert 2010

Commented:
Normal is no need to worry.

Billy
Adrian CantrillSolutions Architect
CERTIFIED EXPERT

Commented:
Yep its fine.. no need to worry

Author

Commented:
Thanks
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.