Internet
GENERAL INFORMATION
Web Development
TROUBLESHOOTING
SLOW SPEEDS
USE WINKEY-R OR START/RUN OR START/PROGRAMS/ACCESSORIES/RUN AND RUN "CMD" FOR THE COMMAND LINE
COMMAND TO RUN:
Run this for a minute and then ctrl-c to break and log stats.
ping yahoo.com -t
STATS TO LOG:
packets sent 000, received 000, lost 0, loss 0%, min 0ms, max 0ms, avg 0ms, ttl=00
- Anything with 2%+ packet loss is suspect.
- Anything with 8%+ packet loss is an issue.
- An average of 200ms or higher is a latency issue.
COMMAND TO RUN:
Run trace route to see where connection is failing.
tractrt yahoo.com
STATS TO LOG:
If there are time-outs in the first three hops, there could be a connecting server issue.
Based on these stats and whether or not there is line noise or filtering that needs to be verified, we can possibly tell from where the slow speeds are coming.
GETTING LINE STATS
You can also get modem stats at browser address http://192.168.1.1/
or whatever your modem address is.
Example used here is a Westell 7500:
Just go to System Monitoring, (FAR left) Advanced Status, admin/admin to get in, click Yes, Tranceiver Statistics.
Log Downstream Margin [(DS)SNR], and Downstream Attenuation [(DS)Atten.]
SNR 8.0+ is good, Atten. 49.0- is good.
RUNNING SPEEDTEST
Example used here is the Frontier ISP:
Frontier speedtest - http://speedtest.frontier.com/
Pick city closest and run.
Match that against ADSL Downstream speed in advanced tranceiver statistics.
OTHER SITES OF INFORMATIONAL INTEREST: