Sign in to follow this  
Followers 0
3d

Some can, some can't PING

6 posts in this topic

My Windows box:

Tracing route to server41.integrityserver.net [70.86.138.18]
over a maximum of 30 hops:
...
 3     9 ms     9 ms    10 ms  68.87.174.69
 4    26 ms    48 ms    27 ms  12.118.20.9
 5    41 ms    45 ms    39 ms  tbr1-p010901.sl9mo.ip.att.net [12.122.80.194]
 6    45 ms    41 ms    40 ms  tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
 7    40 ms    40 ms    51 ms  12.122.82.45
 8    42 ms    40 ms    39 ms  12.119.136.14
 9    40 ms    40 ms    41 ms  vl31.dsr02.dllstx3.theplanet.com [70.85.127.30]

10    39 ms    53 ms    41 ms  po32.dsr02.dllstx5.theplanet.com [70.85.127.110]

11    46 ms    43 ms    47 ms  po2.car06.dllstx5.theplanet.com [70.84.160.168]

12     *        *        *     Request timed out.
13

Pinging 70.86.138.18 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 70.86.138.18:
   Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

From my slackware box:

PING 70.86.138.18 (70.86.138.18) 56(84) bytes of data.

--- 70.86.138.18 ping statistics ---
24 packets transmitted, 0 received, 100% packet loss, time 22999ms

traceroute to 70.86.138.18 (70.86.138.18), 30 hops max, 38 byte packets
...
3  68.87.174.69 (68.87.174.69)  15.958 ms  11.218 ms  11.581 ms
4  12.118.20.9 (12.118.20.9)  25.676 ms  24.121 ms  23.286 ms
5  tbr1-p010901.sl9mo.ip.att.net (12.122.80.194)  39.417 ms  44.254 ms  40.495 ms
6  tbr2-cl6.dlstx.ip.att.net (12.122.10.90)  38.219 ms  40.600 ms  39.334 ms
7  12.122.82.45 (12.122.82.45)  39.027 ms  39.241 ms  38.165 ms
8  12.119.136.14 (12.119.136.14)  39.585 ms  41.279 ms  38.486 ms
9  vl31.dsr02.dllstx3.theplanet.com (70.85.127.30)  39.274 ms vl32.dsr01.dllstx3.theplanet.com (70.85.127.61)  39.652 ms vl32.dsr02.dllstx3.theplanet.com (70.85.127.62)  38.115 ms
10  po32.dsr02.dllstx5.theplanet.com (70.85.127.110)  38.768 ms po31.dsr01.dllstx5.theplanet.com (70.85.127.106)  38.892 ms  37.929 ms
11  po2.car06.dllstx5.theplanet.com (70.84.160.168)  38.271 ms  38.316 ms  41.296 ms
12  * * *

From another box in my city:

ping 70.86.138.18
PING 70.86.138.18 (70.86.138.18) 56(84) bytes of data.
64 bytes from 70.86.138.18: icmp_seq=1 ttl=51 time=61.6 ms
64 bytes from 70.86.138.18: icmp_seq=2 ttl=51 time=64.6 ms
64 bytes from 70.86.138.18: icmp_seq=3 ttl=51 time=63.4 ms
64 bytes from 70.86.138.18: icmp_seq=4 ttl=51 time=66.6 ms
64 bytes from 70.86.138.18: icmp_seq=5 ttl=51 time=63.5 ms
64 bytes from 70.86.138.18: icmp_seq=6 ttl=51 time=61.5 ms

And traceroute passes on this box.

Most people can ping and tracert it, why can't I?

0

Share this post


Link to post
Share on other sites

maybe its the mysterious netghost :P

i can ping and traceroute it fine.

0

Share this post


Link to post
Share on other sites

I was able to ping and tracert myself too.

Have you checked to see if your ISP has blacklisted that IP for some reason? Maybe it could be something with your firewall on that box?

Edited by Booter
0

Share this post


Link to post
Share on other sites

It could also be that your connection is unstable, resulting in slight connection drops but not enough for you to really notice. Or I could be making stuff up.

0

Share this post


Link to post
Share on other sites

It could also be that they have ICMP packets turned off on a particular interface of the router. That is why from one network it works, but not on another.

0

Share this post


Link to post
Share on other sites

To me it looks like your IP has been blocked by the host you're trying to connect to.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0