Link to home
Start Free TrialLog in
Avatar of rstaveley
rstaveleyFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Traceroute does not conclude

There are 4 new servers that have been installed on a client site, which I can't PING. Traceroute indicates something odd.

I've tried traceroute with ICMP ECHO, TCP SYN and UDP and I see it consistently reaching my target IP address xxx.xxx.78.10 OK, but rather than stopping at that point it goes on to timeout on subsequent unnecessary looking hops.

e.g. Disguising the IP addresses out of a sense of duty:

[root@myserver ~]# traceroute -U xxx.xxx.78.10
traceroute to xxx.xxx.78.10 (xxx.xxx.78.10), 30 hops max, 40 byte packets
 .....(a load of good hops)...
10  zzz.zzz.zzz.zzz (zzz.zzz.zzz.zzz)  9.279 ms  9.265 ms  9.252 ms
11  xxx.xxx.78.10 (xxx.xxx.78.10)  10.217 ms  10.205 ms  6.435 ms   <- Hooray?!
12  * * * <- Eh, what's this?? I thought it had got there already!
13  * * *
14  * * *
15  * * *
16  * * *

I get the same result with all 4 servers, which are different operating systems, but on the same network.

I know something isn't set up right, but what is likely to be causing this?
SOLUTION
Avatar of Member_2_2473503
Member_2_2473503
Flag of Philippines image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of rstaveley

ASKER

Good thinking, Joel. They are the real IP addresses assigned to the NICs, but that does make me wonder, if the units were supposed to have been assigned private IP addresses and if the network admin was supposed to have set up NAT on the router. It's one of those nobody-talks-to-anybody set-ups! I'll see if I can break the conspiracy of silence with that idea.
Thanks for the help. It was mis-configured NAT.