Ping issue

[ovaisaijaz]

ISP: WorldCall
Modem: WebStar DPC2100

I always get "Request timed out" whenever i ping to any server.
previously I thought that it might be an issue with the ip i am pinging, but since everyone can ping these bf3 servers ip why I get request timed out error.

It should be Destination host unreachable, if the pinged ip is down..

Need help guys..

 

[Shinobi]

Hello Ovais,

can you give me the address of BF servers. I can help you out.

---------- Post added at 06:51 PM ---------- Previous post was at 06:46 PM ----------

Most game servers block incoming ping requests. Pinging has a new name and its called Tracert. Many game giants open there servers to a trace route and you can always see the ping in the tracert. The last response on the tracert is the ping you will be getting.

 

[ovaisaijaz]

problem is, this issue is'nt specific to ony these bf3 servers.

any ip that i try gives the same timed out error. like, if i ping Google, gives the same error request timed out.......

 

[Shinobi]

do you have a router connected ? if yes then have you tried connecting the modem directly to the pc. ?

---------- Post added at 07:32 PM ---------- Previous post was at 07:31 PM ----------

secondly why exactly do you want to use Ping ? games have a latency bar built in nowadays else you can always use tracert.

 

[ovaisaijaz]

removed the router already, but same result,

just to check the latency between me and destination, even if i use tracert same request timed out result is produced.

 

[Shinobi]

maybe its bocked in your modem by Wcall. I think you better call them then.

Can you tell me what destination would you like to know your latency for ?

 

[ovaisaijaz]

for example,
google.com.pk
or
210.23.14.73

 

[Shinobi]

go to CMD. type Tracert www.google.com.pk

Your ping would be in front of u and same goes for the other address.

---------- Post added at 08:18 PM ---------- Previous post was at 08:14 PM ----------

Tracing route to www.l.google.com [74.125.71.99]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 2 ms 2 ms host81-218.worldcall.net.pk [203.81.218.81]
3 1 ms 1 ms 1 ms WBL.worldcall.net.pk [203.81.204.249]
4 1 ms 1 ms 1 ms WBL.worldcall.net.pk [203.81.204.1]
5 2 ms 1 ms 2 ms 202.133.70.129
6 2 ms 1 ms 2 ms tw31-static89.tw1.com [117.20.31.89]
7 2 ms 1 ms 1 ms tw192-static33.tw1.com [110.93.192.33]
8 48 ms 48 ms 48 ms 72.14.218.33
9 48 ms 48 ms 48 ms 209.85.249.72
10 47 ms 48 ms 52 ms 209.85.241.52
11 63 ms 63 ms 63 ms 209.85.251.95
12 94 ms 95 ms 163 ms 66.249.94.74
13 125 ms 124 ms 124 ms 209.85.241.217
14 132 ms 132 ms 139 ms 209.85.253.71
15 139 ms 141 ms 142 ms 216.239.48.226
16 139 ms 139 ms 137 ms hx-in-f99.1e100.net [74.125.71.99]
Trace complete.

140 ms is my ping for www.google.com.pk

 

[ovaisaijaz]

i have tried tracert as well, it also gives me timed out error

you are alsa a Wcall user i guess, basically i think its an error with the node/router i am connected to ...

 

[Shinobi]

does it give you Error on the first Hop or in the last ?

 

[Googler]

use manual ip's and DNS and then try pinging........it always works for me....... for PTCL

 

[ovaisaijaz]

does it give you Error on the first Hop or in the last ?

right from the first hop, it gives the error.

 

[Shinobi]

Hmm. Then i guess its the node for sure