Ping in cmd. Packets are always lost no matter timeout value
August 13th, 2013
I AM SURE THAT THE PROBLEM IS IN THE ROUTER OR ISP (but I hope it’s in the router). I only used wireless, never tried to connect router using a cable.
Sometimes downloads starts at 3 kbp/s and there’s nothing I can do to change it UNLESS I restart it. If so, it will then come at full speed. This occurs often.
But I’m trying to fix it and to begin i’m testing to ping google in cmd.
I realized that in 20 tries, about 1-2 packets are lost, even setting timeout value to 5 minutes.
How come?
Any ideas?
Thanks
Are you sure there aren’t any anti-virus or firewall software messing with the connection?
No, it’s not.
about 1-2 packets are lost
this happen if you ping your router or your ISP, or just happen when your ping a site
it drop packets when pinging major sites (say google or micro$oft)
might be a problem with your MTU size (Maximum Transmission Unit)
http://help.expedient.com/broadband/mtu_ping_test.shtml
https://www-304.ibm.com/support/docview.wss?uid=swg21086718
other ping tools here
http://www.dslreports.com/tools
also check out the “tracert” function for possible clues
http://www.mediacollege.com/internet/troubleshooter/traceroute.html
a diff DNS (Domain Name System) server might also help
google “DNS”