Thunderbird Wireless Broadband  
16410 84th St NE #D313
Lake Stevens, WA. 98258		Thunderbird Wireless Broadband Phone: 360-691-6963    
Fax: 360-294-5087    
Home Blogs Coverage Map News
Community Forums & Support Contact Us
    Search   Register  Login   
..:: Support::..
 Support
Registration for the Forums is free and easy, just click the "Register" link on the right, then check your email to confirm your login.
  

 FAQ
  

 Third Party Tools

For general computer support, not related directly to your Thunderbird Broadband internet connection, we suggest the following third party resources:

AVG Antivirus - A free, constantly updated antivirus suite for your computer

Ad Aware - A free, constantly updated anti-spyware utility for your computer

A Squared - A free, constantly updated anti-trojan and backdoor utility for your computer

Windows Updates - Microsoft's free security and bug fix update service for Windows
  

     
  Forums
SearchForum Home
  Discussions  Thunderbird Technical Support and Troubleshooting  Recent increase...
 Recent increase in Lag. Damaged router?
 
 12/31/2008 1:08:18 AM
rcm156
2 posts


Recent increase in Lag. Damaged router?
Greetings.

My name's Ron M. and I have been using TB for about half a year.

Everything has been fine up until all these recent winter storms we have been having. My connection WAS great, had the occasional 10 second disconnect but nothing big. Unfortunately, now my connection as slowed and is currently fluttering a fine line of even BEING connected.

My latest speedtest (taken about 2am 12/31/08)

<a href="http://www.speedtest.net"><img src="http://www.speedtest.net/result/381709749.png"></a>


Now, currently seeing these dismal numbers, I decided to run a ping test in my run: cmd (ping -t 192.168.0.1)

Here is a copy of the following log that I received:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Ronnie>ping -t 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:

Reply from 192.168.0.1: bytes=32 time=70ms TTL=63
Reply from 192.168.0.1: bytes=32 time=103ms TTL=63
Reply from 192.168.0.1: bytes=32 time=100ms TTL=63
Reply from 192.168.0.1: bytes=32 time=137ms TTL=63
Reply from 192.168.0.1: bytes=32 time=179ms TTL=63
Reply from 192.168.0.1: bytes=32 time=60ms TTL=63
Reply from 192.168.0.1: bytes=32 time=100ms TTL=63
Reply from 192.168.0.1: bytes=32 time=20ms TTL=63
Reply from 192.168.0.1: bytes=32 time=159ms TTL=63
Reply from 192.168.0.1: bytes=32 time=130ms TTL=63
Reply from 192.168.0.1: bytes=32 time=70ms TTL=63
Request timed out.
Reply from 192.168.0.1: bytes=32 time=643ms TTL=63
Reply from 192.168.0.1: bytes=32 time=48ms TTL=63
Reply from 192.168.0.1: bytes=32 time=70ms TTL=63
Reply from 192.168.0.1: bytes=32 time=157ms TTL=63
Reply from 192.168.0.1: bytes=32 time=79ms TTL=63
Reply from 192.168.0.1: bytes=32 time=45ms TTL=63
Reply from 192.168.0.1: bytes=32 time=44ms TTL=63
Reply from 192.168.0.1: bytes=32 time=50ms TTL=63
Reply from 192.168.0.1: bytes=32 time=126ms TTL=63
Reply from 192.168.0.1: bytes=32 time=86ms TTL=63
Request timed out.
Reply from 192.168.0.1: bytes=32 time=389ms TTL=63
Request timed out.
Reply from 192.168.0.1: bytes=32 time=554ms TTL=63
Reply from 192.168.0.1: bytes=32 time=81ms TTL=63
Reply from 192.168.0.1: bytes=32 time=94ms TTL=63
Reply from 192.168.0.1: bytes=32 time=60ms TTL=63
Reply from 192.168.0.1: bytes=32 time=45ms TTL=63
Reply from 192.168.0.1: bytes=32 time=157ms TTL=63
Reply from 192.168.0.1: bytes=32 time=40ms TTL=63
Reply from 192.168.0.1: bytes=32 time=195ms TTL=63
Reply from 192.168.0.1: bytes=32 time=53ms TTL=63
Reply from 192.168.0.1: bytes=32 time=21ms TTL=63
Request timed out.
Reply from 192.168.0.1: bytes=32 time=752ms TTL=63
Reply from 192.168.0.1: bytes=32 time=26ms TTL=63
Reply from 192.168.0.1: bytes=32 time=178ms TTL=63
Request timed out.
Reply from 192.168.0.1: bytes=32 time=649ms TTL=63
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=786ms TTL=63
Reply from 192.168.0.1: bytes=32 time=20ms TTL=63
Reply from 192.168.0.1: bytes=32 time=165ms TTL=63
Reply from 192.168.0.1: bytes=32 time=16ms TTL=63
Reply from 192.168.0.1: bytes=32 time=103ms TTL=63
Reply from 192.168.0.1: bytes=32 time=164ms TTL=63
Reply from 192.168.0.1: bytes=32 time=100ms TTL=63
Reply from 192.168.0.1: bytes=32 time=30ms TTL=63
Reply from 192.168.0.1: bytes=32 time=129ms TTL=63
Reply from 192.168.0.1: bytes=32 time=209ms TTL=63
Reply from 192.168.0.1: bytes=32 time=126ms TTL=63
Reply from 192.168.0.1: bytes=32 time=85ms TTL=63
Reply from 192.168.0.1: bytes=32 time=73ms TTL=63
Reply from 192.168.0.1: bytes=32 time=201ms TTL=63
Reply from 192.168.0.1: bytes=32 time=92ms TTL=63
Reply from 192.168.0.1: bytes=32 time=14ms TTL=63
Reply from 192.168.0.1: bytes=32 time=131ms TTL=63
Reply from 192.168.0.1: bytes=32 time=105ms TTL=63
Reply from 192.168.0.1: bytes=32 time=57ms TTL=63
Reply from 192.168.0.1: bytes=32 time=37ms TTL=63
Reply from 192.168.0.1: bytes=32 time=225ms TTL=63
Reply from 192.168.0.1: bytes=32 time=98ms TTL=63
Reply from 192.168.0.1: bytes=32 time=94ms TTL=63
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=951ms TTL=63
Reply from 192.168.0.1: bytes=32 time=19ms TTL=63
Reply from 192.168.0.1: bytes=32 time=31ms TTL=63
Reply from 192.168.0.1: bytes=32 time=29ms TTL=63
Reply from 192.168.0.1: bytes=32 time=57ms TTL=63
Reply from 192.168.0.1: bytes=32 time=40ms TTL=63
Reply from 192.168.0.1: bytes=32 time=53ms TTL=63
Reply from 192.168.0.1: bytes=32 time=46ms TTL=63
Request timed out.
Reply from 192.168.0.1: bytes=32 time=239ms TTL=63
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=696ms TTL=63
Reply from 192.168.0.1: bytes=32 time=21ms TTL=63
Reply from 192.168.0.1: bytes=32 time=104ms TTL=63
Reply from 192.168.0.1: bytes=32 time=29ms TTL=63
Reply from 192.168.0.1: bytes=32 time=35ms TTL=63
Reply from 192.168.0.1: bytes=32 time=15ms TTL=63
Reply from 192.168.0.1: bytes=32 time=170ms TTL=63
Reply from 192.168.0.1: bytes=32 time=69ms TTL=63
Reply from 192.168.0.1: bytes=32 time=175ms TTL=63
Reply from 192.168.0.1: bytes=32 time=64ms TTL=63
Reply from 192.168.0.1: bytes=32 time=42ms TTL=63
Reply from 192.168.0.1: bytes=32 time=99ms TTL=63
Reply from 192.168.0.1: bytes=32 time=153ms TTL=63
Reply from 192.168.0.1: bytes=32 time=22ms TTL=63
Reply from 192.168.0.1: bytes=32 time=130ms TTL=63
Reply from 192.168.0.1: bytes=32 time=96ms TTL=63
Reply from 192.168.0.1: bytes=32 time=63ms TTL=63
Reply from 192.168.0.1: bytes=32 time=145ms TTL=63
Reply from 192.168.0.1: bytes=32 time=59ms TTL=63
Reply from 192.168.0.1: bytes=32 time=98ms TTL=63
Reply from 192.168.0.1: bytes=32 time=47ms TTL=63
Reply from 192.168.0.1: bytes=32 time=137ms TTL=63
Reply from 192.168.0.1: bytes=32 time=103ms TTL=63
Reply from 192.168.0.1: bytes=32 time=155ms TTL=63
Reply from 192.168.0.1: bytes=32 time=113ms TTL=63
Reply from 192.168.0.1: bytes=32 time=21ms TTL=63
Reply from 192.168.0.1: bytes=32 time=53ms TTL=63
Reply from 192.168.0.1: bytes=32 time=48ms TTL=63
Reply from 192.168.0.1: bytes=32 time=116ms TTL=63
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=939ms TTL=63
Reply from 192.168.0.1: bytes=32 time=17ms TTL=63
Reply from 192.168.0.1: bytes=32 time=157ms TTL=63
Reply from 192.168.0.1: bytes=32 time=112ms TTL=63
Reply from 192.168.0.1: bytes=32 time=23ms TTL=63
Reply from 192.168.0.1: bytes=32 time=14ms TTL=63
Reply from 192.168.0.1: bytes=32 time=137ms TTL=63
Reply from 192.168.0.1: bytes=32 time=68ms TTL=63
Reply from 192.168.0.1: bytes=32 time=24ms TTL=63
Reply from 192.168.0.1: bytes=32 time=90ms TTL=63
Reply from 192.168.0.1: bytes=32 time=128ms TTL=63
Reply from 192.168.0.1: bytes=32 time=35ms TTL=63
Reply from 192.168.0.1: bytes=32 time=111ms TTL=63
Reply from 192.168.0.1: bytes=32 time=155ms TTL=63
Reply from 192.168.0.1: bytes=32 time=93ms TTL=63
Reply from 192.168.0.1: bytes=32 time=505ms TTL=63
Reply from 192.168.0.1: bytes=32 time=187ms TTL=63
Reply from 192.168.0.1: bytes=32 time=78ms TTL=63
Reply from 192.168.0.1: bytes=32 time=82ms TTL=63
Reply from 192.168.0.1: bytes=32 time=19ms TTL=63
Reply from 192.168.0.1: bytes=32 time=141ms TTL=63
Reply from 192.168.0.1: bytes=32 time=162ms TTL=63
Reply from 192.168.0.1: bytes=32 time=100ms TTL=63
Reply from 192.168.0.1: bytes=32 time=29ms TTL=63
Reply from 192.168.0.1: bytes=32 time=165ms TTL=63
Reply from 192.168.0.1: bytes=32 time=153ms TTL=63
Reply from 192.168.0.1: bytes=32 time=95ms TTL=63
Reply from 192.168.0.1: bytes=32 time=94ms TTL=63
Reply from 192.168.0.1: bytes=32 time=128ms TTL=63
Reply from 192.168.0.1: bytes=32 time=162ms TTL=63
Reply from 192.168.0.1: bytes=32 time=180ms TTL=63
Reply from 192.168.0.1: bytes=32 time=35ms TTL=63
Reply from 192.168.0.1: bytes=32 time=16ms TTL=63
Reply from 192.168.0.1: bytes=32 time=36ms TTL=63
Reply from 192.168.0.1: bytes=32 time=216ms TTL=63
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=785ms TTL=63
Reply from 192.168.0.1: bytes=32 time=50ms TTL=63
Reply from 192.168.0.1: bytes=32 time=170ms TTL=63
Request timed out.
Reply from 192.168.0.1: bytes=32 time=538ms TTL=63
Reply from 192.168.0.1: bytes=32 time=198ms TTL=63
Reply from 192.168.0.1: bytes=32 time=45ms TTL=63
Request timed out.
Reply from 192.168.0.1: bytes=32 time=583ms TTL=63
Request timed out.
Reply from 192.168.0.1: bytes=32 time=862ms TTL=63
Reply from 192.168.0.1: bytes=32 time=15ms TTL=63
Reply from 192.168.0.1: bytes=32 time=14ms TTL=63
Reply from 192.168.0.1: bytes=32 time=143ms TTL=63
Reply from 192.168.0.1: bytes=32 time=165ms TTL=63
Reply from 192.168.0.1: bytes=32 time=149ms TTL=63
Reply from 192.168.0.1: bytes=32 time=89ms TTL=63
Request timed out.
Reply from 192.168.0.1: bytes=32 time=729ms TTL=63
Reply from 192.168.0.1: bytes=32 time=66ms TTL=63
Reply from 192.168.0.1: bytes=32 time=71ms TTL=63
Reply from 192.168.0.1: bytes=32 time=134ms TTL=63
Request timed out.
Reply from 192.168.0.1: bytes=32 time=703ms TTL=63
Reply from 192.168.0.1: bytes=32 time=16ms TTL=63
Request timed out.
Reply from 192.168.0.1: bytes=32 time=483ms TTL=63
Reply from 192.168.0.1: bytes=32 time=119ms TTL=63
Reply from 192.168.0.1: bytes=32 time=21ms TTL=63
Request timed out.
Reply from 192.168.0.1: bytes=32 time=552ms TTL=63
Reply from 192.168.0.1: bytes=32 time=238ms TTL=63
Reply from 192.168.0.1: bytes=32 time=219ms TTL=63
Reply from 192.168.0.1: bytes=32 time=173ms TTL=63
Reply from 192.168.0.1: bytes=32 time=226ms TTL=63
Reply from 192.168.0.1: bytes=32 time=192ms TTL=63
Reply from 192.168.0.1: bytes=32 time=183ms TTL=63
Reply from 192.168.0.1: bytes=32 time=88ms TTL=63
Reply from 192.168.0.1: bytes=32 time=124ms TTL=63
Reply from 192.168.0.1: bytes=32 time=93ms TTL=63
Reply from 192.168.0.1: bytes=32 time=106ms TTL=63
Reply from 192.168.0.1: bytes=32 time=123ms TTL=63
Reply from 192.168.0.1: bytes=32 time=31ms TTL=63
Reply from 192.168.0.1: bytes=32 time=252ms TTL=63
Reply from 192.168.0.1: bytes=32 time=62ms TTL=63
Reply from 192.168.0.1: bytes=32 time=140ms TTL=63
Reply from 192.168.0.1: bytes=32 time=90ms TTL=63
Reply from 192.168.0.1: bytes=32 time=79ms TTL=63
Reply from 192.168.0.1: bytes=32 time=35ms TTL=63
Reply from 192.168.0.1: bytes=32 time=77ms TTL=63
Reply from 192.168.0.1: bytes=32 time=88ms TTL=63
Reply from 192.168.0.1: bytes=32 time=56ms TTL=63
Reply from 192.168.0.1: bytes=32 time=90ms TTL=63
Reply from 192.168.0.1: bytes=32 time=98ms TTL=63
Reply from 192.168.0.1: bytes=32 time=43ms TTL=63

Ping statistics for 192.168.0.1:
    Packets: Sent = 203, Received = 180, Lost = 23 (11% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 951ms, Average = 153ms

As you can see, Im having a fairly high maximum (should only be in the double digits) and a 11% loss, and also alot of Time outs generally every 10 attempts.


I only have a couple theorys why this could be this way.
A) With all these power outages and storms, my Router has been damaged and needs replacing
B) The Snow and Ice (albeit its melting) is causing interference
C) The tower was damaged somehow and is affecting service.


I should also mention that Im running off a Wireless USB to plug into our little tower at the other end of the house. Ive heard that they can be subjected to more then normal lag, but like I said, I wasnt having all these problems before.

I will be running some more tests and some possible fixes tomarrow, and the following days until I can see an impromvent.

If there is anything you guys can suggest, my ears are open.


 12/31/2008 1:14:14 AM
rcm156
2 posts


Re: Recent increase in Lag. Damaged router?
whoops! looks like the speed test didn't register.

down 343

up 346


Also, would like to clarify about the USB, meant to say that we are operating on a LAN
 2/2/2009 3:52:38 PM
deltabrown
3 posts
www.aerotestsvc.com


Re: Recent increase in Lag. Damaged router?
What I've seen with these kinds of errors is a bad cable. Maybe the snow load pulled one wire out of the connector at the transmitter end, or maybe there is a bit of corrosion on a connector.
 Page 1 of 1
NextPreviousNo Rating
  Discussions  Thunderbird Technical Support and Troubleshooting  Recent increase...
SearchSearch  Forum HomeForum Home     

Terms Of Use  Privacy Statement
Copyright 2006 by Thunderbird Broadband