Quote:
Originally Posted by AaronCooper
You have to enable "Respond to Ping on WAN Port" on your router.
|
Thanks Aaron
it was actually ticked already but still didn't work?
A Google search later and someone had a similar problem, with a solution.
Guess what..a flaky superhub is the problem.
(quote)
I needed ping on wan port in order to use the Thinkbroadband Broadband Quality Monitor.
However I did some further investigation and have discovered this apparent bug is related to Port Forwarding on the Superhub.
Setting up a single Port Forwarding rule using protocol both causes the Superhub to stop responding to pings on the wan port. If I set up two separate rules (i.e. UDP and TCP) on the same port (say 5775) ping appears to work fine as does the forwarding.
So I currently have a satisfactory work around.
This bug should be easy to replicate and you may want to pass on this info to Netgear or who ever does your Superhub firmware.
I had a port forwarded using both protocol..changed it and will see how it goes.