You can test the Lan ping using the method below
start->run->command prompt->ping website name or ping ip-address
you can check website ping using the site whoisxy.com
Ping is one of the first tools to use to check computer, router and Internet connectivity. It's run at a command prompt, but getting the basic information is quite easy. You can do the whole thing in 30 seconds. 1. To run ping, type Start > Run. 2. Type cmd in the Run window, and click OK. A black and white command line window pops up. 3. Type ping followed by an IP address or a DNS address. 4. Press Enter to execute the command. Three useful examples: 1. ping 127.0.0.1 (This is a "loopback ping" ? your computer trying to talk to itself. This tests whether your computer is able to handle Ethernet traffic. If this has a negative result, the computer has an operating system problem.) 2. ping 192.168.1.1 (If the result is "Request timed out", type ping 192.168.0.1. If that also times out, then the computer is not making a connection to your router.) 3. ping www.netgear.com. (Tests whether your computer can contact Internet computers.) When there is no problem, the ping results look as shown in the following screenshot. Three items of interest in the results are highlighted with arrows. The first arrow shows the computer being contacted is replying. (The DNS address "www.netgear.com" is converted by ping into the equivalent IP address, 10.1.1.86.) This shows both that your network is connnected to the Internet, and that that computer on the Internet is running normally. www.netgear.com is always running, so this is a good test address to use. The second arrow shows that Ethernet packets have "0% loss". This is the best possible result. It means that the network connection is lightly loaded, and that it has not been necessary to transmit any of the same information twice. The third arrow shows the average time it took to answer. "Average = 0ms" is the best possible result. Probably you'll only get responses this quickly from computers on your own network. Interpreting Ping when There's a Problem As far as NETGEAR equipment, the problem you're most likely to run into is "Request Timed Out". This means there is no connection. Read these posts: http://www.fixya.com/ThreadView.aspx?prdid=252225&thid=102077 and http://www.fixya.com/ThreadView.aspx?prdid=252225&thid=102074 Another error is "Unknown host", which just means that the DNS or IP address you typed doesn't exist. Probably, you made a typo. Other problems are generally outside the scope of NETGEAR support. Often they are problems with your ISP ? contact them with concerns. A controversial situation is when packet loss is not 0%. Sometimes this indicates a severe problem, but in other situations it doesn't indicate any problem whatever. However anything higher than 5% is definitely a problem. If the average round trip time is > 500 ms, there' s possible latency problem. Again, contact your ISP. Limitations of the Ping Tool * Ping is not a good tool for diagnosing intermittent problems. * Good results are reliable, but ?bad results? could be caused by any number of things, and are not necessarily reliable! * Ping uses ICMP, which has low priority, showing speeds that are slower than regular network traffic. Some computers reject ICMP, and therefore pinging, entirely. * When an IP appears between the source and destination in a traceroute command it does *not* mean that that IP must be pingable.
Great detail
498 views
Usually answered in minutes!
×