Go Back   Wireless and Wifi Forums > News > Newsgroups > alt.internet.wireless
belkin router problems

belkin router problems

belkin router problems. Discuss belkin router problems, on Wireless Forums.

Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 10-01-2005, 10:21 PM
Andymcgoo
Guest
  
Posts: n/a
Default belkin router problems
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.




Reply With Quote
  #2 (permalink)  
Old 10-02-2005, 02:14 AM
Doz
Guest
  
Posts: n/a
Default Re: belkin router problems
Could be radio interference...


"Andymcgoo" <andy_ma@blueyonder.co.uk> wrote in message
news:35D%e.44309$RW.41425@fe2.news.blueyonder.co.u k...
> 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.
>
>
>



Reply With Quote
  #3 (permalink)  
Old 10-02-2005, 04:41 PM
Jeff Liebermann
Guest
  
Posts: n/a
Default Re: belkin router problems
On Sat, 01 Oct 2005 21:21:03 GMT, "Andymcgoo"
<andy_ma@blueyonder.co.uk> wrote:

>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

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.

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

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

>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
(...)

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.


--
Jeff Liebermann jeffl@comix.santa-cruz.ca.us
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

Reply With Quote
  #4 (permalink)  
Old 10-02-2005, 09:19 PM
Andymcgoo
Guest
  
Posts: n/a
Default Re: belkin router problems
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


"Jeff Liebermann" <jeffl@comix.santa-cruz.ca.us> wrote in message
news:d3vvj11l6niqfri2an0epcm9karj253k8j@4ax.com...
> On Sat, 01 Oct 2005 21:21:03 GMT, "Andymcgoo"
> <andy_ma@blueyonder.co.uk> wrote:
>
>>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
>
> 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.
>
>>Reply from 192.168.2.2: bytes=32 time=124ms TTL=128
>
> This is the initial "slow start" wakeup time and is common with all
> routers. The first ping is always slow.
>
>>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
> (...)
>
> 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.
>
>
> --
> Jeff Liebermann jeffl@comix.santa-cruz.ca.us
> 150 Felker St #D http://www.LearnByDestroying.com
> Santa Cruz CA 95060 http://802.11junk.com
> Skype: JeffLiebermann AE6KS 831-336-2558



Reply With Quote
  #5 (permalink)  
Old 10-02-2005, 10:26 PM
Doz
Guest
  
Posts: n/a
Default Re: belkin router problems
I had the same problem with a wireless TV sender.. a right pain.


"Andymcgoo" <andy_ma@blueyonder.co.uk> wrote in message
news:ahX%e.60016$RW.8832@fe2.news.blueyonder.co.uk ...
> 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
>
>
> "Jeff Liebermann" <jeffl@comix.santa-cruz.ca.us> wrote in message
> news:d3vvj11l6niqfri2an0epcm9karj253k8j@4ax.com...
>> On Sat, 01 Oct 2005 21:21:03 GMT, "Andymcgoo"
>> <andy_ma@blueyonder.co.uk> wrote:
>>
>>>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
>>
>> 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.
>>
>>>Reply from 192.168.2.2: bytes=32 time=124ms TTL=128
>>
>> This is the initial "slow start" wakeup time and is common with all
>> routers. The first ping is always slow.
>>
>>>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
>> (...)
>>
>> 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.
>>
>>
>> --
>> Jeff Liebermann jeffl@comix.santa-cruz.ca.us
>> 150 Felker St #D http://www.LearnByDestroying.com
>> Santa Cruz CA 95060 http://802.11junk.com
>> Skype: JeffLiebermann AE6KS 831-336-2558
>
>



Reply With Quote
Sponsored Links
Reply

« RG-58U for external antenna | WRT54GS block most outgoing ports.. »
Thread Tools
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Keep Losing connection with Belkin router ladyelect Network Troubleshooting 4 09-10-2007 05:36 PM
Help!: setup Belkin wireless router on LAN ImaChessNut@gmail.com alt.internet.wireless 2 01-11-2007 03:38 AM
Belkin wireless router WAN/LAN problem vphilomin@googlemail.com alt.internet.wireless 10 08-01-2006 10:33 PM
Wireless Belkin F5D72304 router -port forwarding-Webserver problems danskimanuk Network Troubleshooting 1 02-06-2006 10:46 PM
Problems with WPA-PSK and Belkin F5D7632uk4 adsl router Martyn D. Wheeler alt.internet.wireless 1 08-14-2005 11:17 PM


All times are GMT. The time now is 08:09 PM.

Contact Us - Wireless Support Forum - Archive - Top - Bike Forums - Cooking Junkies Forums

Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.2.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45