General discussion

Locked

Can traceroute but cannot ping the device

By wabulencia ·
I have a device which I will install on my network and in doing some preliminary tests, I traceroute the IP address that I will assign to this device and the result was that I can reach it. If I tried to ping this IP address, there is no reply. The network engineer maintaining the the LAN confirmed to me that he has not assigned the IP number that I will use to any device. Appreciate if you can tell me what is happening here!

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

what kind of "device" is it?

by jdclyde In reply to Can traceroute but cannot ...

does it have a firewall on it? If so, it isn't responding to the ping.

If you put it on a network that already has that IP address used, you would get a notice and you wouldn't even get that traceroute.

get into the device (whatever it is) and ping FROM it to somewhere else. If it can connect out, don't worry about a ping.

The other problem might be, it sounds like it is on a different segment of your network. Make sure it has a gateway set in it, so it knows how to get off the local lan.

Collapse -

First

by stargazerr In reply to Can traceroute but cannot ...

First: What device is it??

Second: TR has a Tech Q&A section. Post in there please.

]:)

Collapse -

details of this problem

by wabulencia In reply to Can traceroute but cannot ...

i will assign this IP to a firewall device and as a pre-requisite, I did some test. Ping is negative but Trace is positive. Note again that the device is not yet connected to the network.
The result of the trace test is as follows:
traceroute to 84.235.228.146 (84.235.228.146) from malasada.lava.net (64.65.64.17), 40 hops max, 40 byte packets
1 iiwi-fe-0-0-0.lava.net (64.65.64.30) 0.526 ms 0.436 ms 0.424 ms
2 noio-fe-0-0-3-16.lava.net (64.65.127.97) 0.512 ms 0.454 ms 0.455 ms
3 12.125.92.113 (12.125.92.113) 0.701 ms 0.607 ms 1.217 ms
4 tbr1-p012410.sffca.ip.att.net (12.123.12.226) 114.410 ms 113.154 ms 113.209 ms
5 tbr1-cl1.cgcil.ip.att.net (12.122.10.5) 111.520 ms 111.003 ms 111.034 ms
6 tbr1-cl14.n54ny.ip.att.net (12.122.10.1) 110.166 ms 111.879 ms 110.210 ms
7 gar4-p300.n54ny.ip.att.net (12.123.3.2) 109.330 ms 109.341 ms 109.313 ms
8 12.126.124.86 (12.126.124.86) 110.137 ms 109.780 ms 109.660 ms
9 ar1.str.de.colt.net (212.121.151.242) 202.945 ms 202.949 ms 202.990 ms
10 h-213.61.175.86.host.de.colt.net (213.61.175.86) 204.460 ms 204.572 ms 204.406 ms
11 217.159.0.46 (217.159.0.46) 206.472 ms 205.586 ms 207.544 ms
12 * * *
13 * * *
14 host-84-235-228-146.satlynx.net (84.235.228.146) 1176.303 ms 1278.339 ms 1156.192 ms
15 host-84-235-228-146.satlynx.net (84.235.228.146) 1114.012 ms 1209.531 ms 1292.518 ms
16 host-84-235-228-146.satlynx.net (84.235.228.146) 1222.024 ms 1252.135 ms 1211.808 ms
17 host-84-235-228-146.satlynx.net (84.235.228.146) 1148.327 ms 1265.921 ms 1193.689 ms
18 host-84-235-228-146.satlynx.net (84.235.228.146) 1160.853 ms * 1196.338 ms
19 host-84-235-228-146.satlynx.net (84.235.228.146) 1244.407 ms 1164.490 ms 900.238 ms
20 host-84-235-228-146.satlynx.net (84.235.228.146) 981.950 ms 1243.181 ms 1245.984 ms
21 host-84-235-228-146.satlynx.net (84.235.228.146) 1313.671 ms 1663.569 ms 1555.129 ms
22 host-84-235-228-146.satlynx.net (84.235.228.146) 1128.767 ms 1327.238 ms *
23 * host-84-235-228-146.satlynx.net (84.235.228.146) 1197.319 ms 1233.690 ms
24 host-84-235-228-146.satlynx.net (84.235.228.146) 1293.624 ms 1189.121 ms 1162.247 ms
25 host-84-235-228-146.satlynx.net (84.235.228.146) 1230.367 ms 1418.516 ms *
26 host-84-235-228-146.satlynx.net (84.235.228.146) 1270.841 ms 1320.907 ms 1283.577 ms
27 host-84-235-228-146.satlynx.net (84.235.228.146) 1201.239 ms 1304.643 ms 1184.144 ms
28 * host-84-235-228-146.satlynx.net (84.235.228.146) 1234.115 ms 1047.263 ms
29 * host-84-235-228-146.satlynx.net (84.235.228.146) 949.905 ms 1099.158 ms
30 * host-84-235-228-146.satlynx.net (84.235.228.146) 1439.523 ms 1265.908 ms
31 host-84-235-228-146.satlynx.net (84.235.228.146) 1223.279 ms 1357.869 ms 1306.242 ms
32 * host-84-235-228-146.satlynx.net (84.235.228.146) 1373.085 ms 1483.654 ms
33 host-84-235-228-146.satlynx.net (84.235.228.146) 1280.719 ms 12**.806 ms 1414.794 ms
34 host-84-235-228-146.satlynx.net (84.235.228.146) 1300.306 ms 1189.451 ms 1253.675 ms
35 host-84-235-228-146.satlynx.net (84.235.228.146) 1424.949 ms 1061.885 ms 1112.960 ms
36 host-84-235-228-146.satlynx.net (84.235.228.146) 1303.678 ms 1415.011 ms *
37 host-84-235-228-146.satlynx.net (84.235.228.146) 1424.868 ms 1442.160 ms 1409.399 ms
38 host-84-235-228-146.satlynx.net (84.235.228.146) 1301.209 ms 1177.293 ms *
39 host-84-235-228-146.satlynx.net (84.235.228.146) 1430.104 ms 1440.656 ms 1115.152 ms
40 host-84-235-228-146.satlynx.net (84.235.228.146) 1334.889 ms 1388.058 ms 1332.022 ms

Collapse -

It's hitting a firewall somewhere...

by curlergirl In reply to details of this problem

in DEnmark. Is that where you are?

Here's the end of the trail according to DNSstuff.com:

31 1484 * * 1484 ms [+142ms]
84.235.228.146 AS16360
Gilat_Europe host-84-235-228-146.satlynx.net. -1 miles [+0] 0 miles [+0] 20 DE [Router did not respond]
32 * * * 99999 ms [+99999ms]
[Unknown] [Unknown - Firewall did not respond] -1 miles [+0] 0 miles [+0]
33 * * * 99999 ms [+0ms]
[Unknown] [Unknown - Firewall did not respond] -1 miles [+0] 0 miles [+0]
34 * * * 99999 ms [+0ms]
[Unknown] [Unknown - Firewall did not respond] -1 miles [+0] 0 miles [+0]
35 * * * 99999 ms [+0ms]
[Unknown] [Unknown - Firewall did not respond]
[4 hops with no response:
assuming we hit a firewall
that blocks pings] -1 miles [+0]

Analysis:
Number of hops: 35
Last hop responding to ICMP: 31, UDP: 30, TCP: 29.
There appears to be a firewall at (hop 32) that blocks ICMP (ping) packets.
There appears to be a firewall at 84.235.228.146 (hop 31) that blocks unwanted UDP packets.
There appears to be a firewall at 84.235.228.146 (hop 30) that blocks unwanted TCP packets.

If it's hitting your firewall, then the problem is that you are blocking ICMP packets so that it can't respond.

Collapse -

DNS

by Papus In reply to Can traceroute but cannot ...

it should be a DNS problem
check it out

Collapse -

could be the DNS, will definitely check this on Monday

by wabulencia In reply to DNS

could be the DNS, will definitely check this on Monday

Collapse -

the spoksperson for god has spoken...

by zenken_767 In reply to Can traceroute but cannot ...

U can ping all u want,but untill IT allows U 2 place your "item" it ain't gonna work.....ask very nicely and they may allow it access.Unless they have reason not to....

Back to IT Employment Forum
7 total posts (Page 1 of 1)  

Related Forums