Pinging Limitation Detected By ISP

[Explicitt]

I am using WTFast for online gaming and I've been using it for quite some time. I have Comcast as my ISP and I used to be directly connected to the modem, and while using the feature "Pinging Servers" by WTFast to give me the best server to connect to for gaming, it worked great.

I had some issues and ended up having to get a router so I am not directly connected to the modem any longer, since doing this everytime that I try to ping the servers, I get an error stating "Pinging Limitation detected by your ISP"

I contacted my ISP and they said they had no idea in regards to a limitation put out by them, they said it's more than likely caused by my router since I had no issues prior to being directly connected to the modem.

I am using a Netgear WGR614v10 and would like to know how I can solve this issue. Under the advanced tab there is a box where I can check "Respond to ping on internet wan port" I have this checked, and am still having the issue. Any idea on how I can solve this problem so that I can successfully ping servers again?

 

[Urumiko]

Respond to ping on internet wan port just tells your router to respond to people trying to ping it from the outside world. Best security practice would be to have this turned off. There is really no reason a ping shouldn't make it through unless you had firewall rules set up on the router. There could be some security feature on the router though this is unlikely.

You may wish to try DMZing your computer as a test.

 

[bill001g]

The large problem with that software is they hide any details under a huge piles of technically confusing details....better known as <mod edit>. They seldom give clear answers to what message mean or how running non compressible game data through VPN tunnels can decrease the bandwidth and the latency.

I can easily see why the ISP knows nothing. Few ISP would prevent you from doing a ping scan because they don't want to pay for firewalls. What is really bad is if this software is using ping scanning in a way that trips off firewall rules then it is very bad. They all allows some the rules are generally to prevent attacks. Still it would likely be your router or even your PC firewall doing this.

WTFast is mostly smoke and mirrors it only provides a benefit in a very tiny situation. You can easily write a bat file with a list of the server you use with ping commands and it will never trip off a firewall rule and you will still get as good results.

<Let's watch our language in the forums>

 

[Explicitt]

The large problem with that software is they hide any details under a huge piles of technically confusing details....better known as <mod edit>. They seldom give clear answers to what message mean or how running non compressible game data through VPN tunnels can decrease the bandwidth and the latency.

I can easily see why the ISP knows nothing. Few ISP would prevent you from doing a ping scan because they don't want to pay for firewalls. What is really bad is if this software is using ping scanning in a way that trips off firewall rules then it is very bad. They all allows some the rules are generally to prevent attacks. Still it would likely be your router or even your PC firewall doing this.

WTFast is mostly smoke and mirrors it only provides a benefit in a very tiny situation. You can easily write a bat file with a list of the server you use with ping commands and it will never trip off a firewall rule and you will still get as good results.

Well like I said nothing changed on my computer prior to being directly connected to the modem, this issue only arose after connecting the modem to the router and the router to my PC. Now this issue is happening.

I use WTFast because the routing of the game that I play is awful, and it caused some major latency issues sometimes while playing. WTFast solves those routing issues, and I experience much better game play and latency while using it.

Normally I'd say it's a gimmick, but I've been using it for months now and comparing to my normal connection due to the routing, it drastically improves my connection to the game server.

I just want to know why my router isn't allowing the program to ping servers to show me the best possible server to connect to using WTFast. I'm just picking one of the three closest to me and hoping for the best.

 

[Urumiko]

I dont fully understand your issue, but if you are using something which is pinging many destinations in a short space of time it could well trigger a firewall/ips rule. Are there any options to alter the frequency/number of pings in the utility you are using?

Is the optimum server always changing? because if not some dns trickery could be in order?

An explicit rule in the firewall allowing the pings or all traffic may help, or again DMZ?

and teehee bill001g got told off 😉

 

[Explicitt]

I dont fully understand your issue, but if you are using something which is pinging many destinations in a short space of time it could well trigger a firewall/ips rule. Are there any options to alter the frequency/number of pings in the utility you are using?

Is the optimum server always changing? because if not some dns trickery could be in order?

An explicit rule in the firewall allowing the pings or all traffic may help, or again DMZ?

and teehee bill001g got told off 😉

Here is the issue I'm referring to.

As I said it never happened until after connecting thru the router , directly connected to the modem was fine previously.

http://i58.tinypic.com/153qtsw.png

There is nothing to change the pinging options, there's just a button to ping servers, which basically tells you the best possible server to connect to for the game your playing, for the lowest latency. It get's to 3/4th of the way done then pops up the pinging limitation.

I'm a big newbie when it comes to this stuff, so I'm not sure how to get it to work again, or what settings to change in the router to allow it, and as far as my firewall via computer, I already have it enabled to pass through, and it worked previously before connecting through router.

 

[Urumiko]

That image is pretty much confirming the issue.
it is a common security feature that if you send lots of pings in quick succession it will start blocking them after a fixed number of pings or time. The only real solution is to use less pings.
The software seems to be suggesting it has the option to do that, this may be in menus, or you may be able to modify a file in the initial directory such as an "ini" file.

I would suggest googling things like "Wttfast number of pings" and if you still have no luck, contact WTFFast