belkin router problems

Oct 02, 2005 4 Replies

Hi I have got a problem with my laptop loosing connection to the router I have done a ping test and after a very short time the ping times go from 1ms to over 900ms the time fluctuates, any ideas


Pinging 192.168.2.2 with 32 bytes of data:


Reply from 192.168.2.2: bytes=32 time=124ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Request timed out.



Reply from 192.168.2.2: bytes=32 time=41ms TTL=128



Reply from 192.168.2.2: bytes=32 time=3ms TTL=128



Reply from 192.168.2.2: bytes=32 time=209ms TTL=128



Reply from 192.168.2.2: bytes=32 time=847ms TTL=128



Reply from 192.168.2.2: bytes=32 time=702ms TTL=128



Reply from 192.168.2.2: bytes=32 time=849ms TTL=128



Reply from 192.168.2.2: bytes=32 time=482ms TTL=128



Reply from 192.168.2.2: bytes=32 time=957ms TTL=128



Reply from 192.168.2.2: bytes=32 time=876ms TTL=128



Reply from 192.168.2.2: bytes=32 time=2572ms TTL=128



Reply from 192.168.2.2: bytes=32 time=2493ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1882ms TTL=128



Request timed out.



Reply from 192.168.2.2: bytes=32 time=390ms TTL=128



Request timed out.



Reply from 192.168.2.2: bytes=32 time=3ms TTL=128



Reply from 192.168.2.2: bytes=32 time=1ms TTL=128



Reply from 192.168.2.2: bytes=32 time=11ms TTL=128



Request timed out.


I do wish you wouldn't double space your postings. If you continue to consume white space at that rate, the limited supply of white space will eventually run out and AllTheWordsWillRunTogether.

This is the initial "slow start" wakeup time and is common with all routers. The first ping is always slow.

(...)

Classic interference. No way to tell from here if the interference is appearing at the wireless router or the client radio. It could be almost anything that transmits on 2.4GHz including other wireless networks. Guessing by the large numbers, the connection was comatose for a long time during which the system retried several times. This level of obliteration generally points to a microwave oven or possibly a nearby 2.4Ghz cordless phone. Another Wi-Fi network or Bluetooth would not yield such large delays.

Thank you I will have a look around the place and also have a look at all of my machine son the network to see if there is a trend

I had the same problem with a wireless TV sender.. a right pain.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required