i see other servers 9999 ping

[Rotem]

i am not sure if this belongs here so i am sorry if not, admins please move it.
i have the well known 9999 ping issue but its not a problem with a server i open, its a problem with half of the servers i see in server browser - half of what my server browser finds, i see 9999 ping. most of the times i can connect to them, but sometimes i cant. it does nothing, not waiting to download anything, just nothing. i have already port forwarded the ports: 23073 and 23083. but the problem remains. what else should i do?
thanks for reading

[GhostRiderSwiss]

where u life? and what an inet are u using, its maybe how far away u are + u got a slow internet maybe 
and its normal that around 1/4 of servers (unfiltered) are 9999 pinged becauze of the distance or other stuff :/ happens for me too =(

but not sure if its that... may wait for another "possible reason" ^^

Greetz "GR"

[Rotem]

i live in Isreal and i do have a slow connection but it cant be the problem because there are known servers like Beos or snipe and slice that worked fine a few months ago and now they show 9999 . and its not 1/4 its almost 1/2 . and most of these servers are from EU

[GhostRiderSwiss]

hmmm letz wait for bether help then im sorry    ='(

[Furai]

Are you using some proxy? Only thing that cames to my mind that you've been firewalled by serverowner.

[Rotem]

how can i check if i am using proxy? i never dealt with something like that. i am using COMODO firewall but i remember the problem started before i started using it.

[Falcon`]

launch windows command line (Start->Run->cmd in XP or Start->Search field->cmd in vista&7) and exec:
tracert <insert_some_9999_ping_ip_here>

[FliesLikeABrick]

9999 ping can happen if your ISP or something else is blocking the small UDP packets used to ping servers.  If that is the case, there is nothing you can do but call and complain.

[Rotem]

launch windows command line (Start->Run->cmd in XP or Start->Search field->cmd in vista&7) and exec:
tracert <insert_some_9999_ping_ip_here>

i did what u said and here are the resaults:

Tracing route to beooo.eu [178.63.235.51]
over a maximum of 30 hops:

  1    28 ms    12 ms    10 ms  10.171.128.1
  2    13 ms    21 ms    15 ms  10.171.128.1
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5    17 ms    12 ms    15 ms  bzq-179-124-169.static.bezeqint.net [212.179.124
.169]
  6    14 ms    14 ms    14 ms  bzq-179-124-162.static.bezeqint.net [212.179.124
.162]
  7     *        *      505 ms  bzq-179-124-18.static.bezeqint.net [212.179.124.
18]
  8    74 ms    77 ms    71 ms  decix2-gw.hetzner.de [80.81.193.164]
  9    93 ms   107 ms    94 ms  hos-bb1.juniper1.fs.hetzner.de [213.239.240.242]

 10   122 ms   103 ms   103 ms  hos-tr1.ex3k9.rz10.hetzner.de [213.239.227.138]

 11    79 ms    74 ms    80 ms  HE-80003.proplay.de [78.46.33.180]
 12    75 ms    79 ms    78 ms  beooo.eu [178.63.235.51]

Trace complete.

[FliesLikeABrick]

Based on the mess that is the first 4 hops of your traceroute, I suspect your ISP is doing something that is filtering out those tiny UDP packets used to ping servers - if that's the case then there's nothing you can to do fix it.