NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
rpz620
Nov 09, 2010Aspirant
WN2000RPT - Internet Access Keeps Dropping
All of my devices can continually access the WN2000RPT device and access the local network as well as the internet. However, after some time, the internet connection drops for the repeater only - I c...
WallyZ21
Jul 02, 2011Aspirant
My 2 cents worth.
If you set up a continuous ping to the extender then when you start to have problems will will notice "Request timed out" messages and ridiculous ping times:
C:\Documents and Settings\walter>ping -t 10.1.1.3
Pinging 10.1.1.3 with 32 bytes of data:
Reply from 10.1.1.3: bytes=32 time=60ms TTL=64
Reply from 10.1.1.3: bytes=32 time=204ms TTL=64
Reply from 10.1.1.3: bytes=32 time=57ms TTL=64
Reply from 10.1.1.3: bytes=32 time=1125ms TTL=64
Reply from 10.1.1.3: bytes=32 time=14ms TTL=64
Reply from 10.1.1.3: bytes=32 time=14ms TTL=64
Reply from 10.1.1.3: bytes=32 time=15ms TTL=64
Reply from 10.1.1.3: bytes=32 time=70ms TTL=64
Reply from 10.1.1.3: bytes=32 time=64ms TTL=64
Reply from 10.1.1.3: bytes=32 time=3ms TTL=64
Reply from 10.1.1.3: bytes=32 time=75ms TTL=64
Reply from 10.1.1.3: bytes=32 time=105ms TTL=64
Reply from 10.1.1.3: bytes=32 time=3ms TTL=64
.
.
.
Request timed out.
Reply from 10.1.1.3: bytes=32 time=17ms TTL=64
Reply from 10.1.1.3: bytes=32 time=51ms TTL=64
Reply from 10.1.1.3: bytes=32 time=145ms TTL=64
Reply from 10.1.1.3: bytes=32 time=2774ms TTL=64
Reply from 10.1.1.3: bytes=32 time=45ms TTL=64
Reply from 10.1.1.3: bytes=32 time=154ms TTL=64
Reply from 10.1.1.3: bytes=32 time=67ms TTL=64
Reply from 10.1.1.3: bytes=32 time=5ms TTL=64
Ping statistics for 10.1.1.3:
Packets: Sent = 1007, Received = 879, Lost = 128 (12% lost
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 4054ms, Average = 165ms
Control-C
^C
And here is what is should run like:
C:\Documents and Settings\walter>ping -t 10.1.1.3
Pinging 10.1.1.3 with 32 bytes of data:
Reply from 10.1.1.3: bytes=32 time=12ms TTL=64
Reply from 10.1.1.3: bytes=32 time=8ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=8ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=5ms TTL=64
Reply from 10.1.1.3: bytes=32 time=5ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=5ms TTL=64
Reply from 10.1.1.3: bytes=32 time=8ms TTL=64
Reply from 10.1.1.3: bytes=32 time=9ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=9ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=8ms TTL=64
Reply from 10.1.1.3: bytes=32 time=7ms TTL=64
Reply from 10.1.1.3: bytes=32 time=8ms TTL=64
Reply from 10.1.1.3: bytes=32 time=8ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=9ms TTL=64
Reply from 10.1.1.3: bytes=32 time=11ms TTL=64
Reply from 10.1.1.3: bytes=32 time=8ms TTL=64
Reply from 10.1.1.3: bytes=32 time=7ms TTL=64
Reply from 10.1.1.3: bytes=32 time=9ms TTL=64
Reply from 10.1.1.3: bytes=32 time=10ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=7ms TTL=64
Reply from 10.1.1.3: bytes=32 time=9ms TTL=64
Reply from 10.1.1.3: bytes=32 time=11ms TTL=64
Reply from 10.1.1.3: bytes=32 time=8ms TTL=64
Reply from 10.1.1.3: bytes=32 time=21ms TTL=64
Reply from 10.1.1.3: bytes=32 time=4ms TTL=64
.
.
.
Reply from 10.1.1.3: bytes=32 time=7ms TTL=64
Reply from 10.1.1.3: bytes=32 time=7ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=11ms TTL=64
Ping statistics for 10.1.1.3:
Packets: Sent = 997, Received = 997, Lost = 0 (0% lost
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 47ms, Average = 9ms
Control-C
^C
And the observation of others that smart phones are interfering the extender seems accurate. Every five minutes my smart phone attempts to find access points and then the extender starts dropping ping packets. If I turn off my phone it appears to resolve the issue.
However this behavior is only exhibited on netgear products. My smart phone doesn't seem to affect any other manufactures products I have tested. To be fair the only other I have tested is Belkin
It appears netgear wireless products are overtly susceptible to interference.
If you set up a continuous ping to the extender then when you start to have problems will will notice "Request timed out" messages and ridiculous ping times:
C:\Documents and Settings\walter>ping -t 10.1.1.3
Pinging 10.1.1.3 with 32 bytes of data:
Reply from 10.1.1.3: bytes=32 time=60ms TTL=64
Reply from 10.1.1.3: bytes=32 time=204ms TTL=64
Reply from 10.1.1.3: bytes=32 time=57ms TTL=64
Reply from 10.1.1.3: bytes=32 time=1125ms TTL=64
Reply from 10.1.1.3: bytes=32 time=14ms TTL=64
Reply from 10.1.1.3: bytes=32 time=14ms TTL=64
Reply from 10.1.1.3: bytes=32 time=15ms TTL=64
Reply from 10.1.1.3: bytes=32 time=70ms TTL=64
Reply from 10.1.1.3: bytes=32 time=64ms TTL=64
Reply from 10.1.1.3: bytes=32 time=3ms TTL=64
Reply from 10.1.1.3: bytes=32 time=75ms TTL=64
Reply from 10.1.1.3: bytes=32 time=105ms TTL=64
Reply from 10.1.1.3: bytes=32 time=3ms TTL=64
.
.
.
Request timed out.
Reply from 10.1.1.3: bytes=32 time=17ms TTL=64
Reply from 10.1.1.3: bytes=32 time=51ms TTL=64
Reply from 10.1.1.3: bytes=32 time=145ms TTL=64
Reply from 10.1.1.3: bytes=32 time=2774ms TTL=64
Reply from 10.1.1.3: bytes=32 time=45ms TTL=64
Reply from 10.1.1.3: bytes=32 time=154ms TTL=64
Reply from 10.1.1.3: bytes=32 time=67ms TTL=64
Reply from 10.1.1.3: bytes=32 time=5ms TTL=64
Ping statistics for 10.1.1.3:
Packets: Sent = 1007, Received = 879, Lost = 128 (12% lost
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 4054ms, Average = 165ms
Control-C
^C
And here is what is should run like:
C:\Documents and Settings\walter>ping -t 10.1.1.3
Pinging 10.1.1.3 with 32 bytes of data:
Reply from 10.1.1.3: bytes=32 time=12ms TTL=64
Reply from 10.1.1.3: bytes=32 time=8ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=8ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=5ms TTL=64
Reply from 10.1.1.3: bytes=32 time=5ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=5ms TTL=64
Reply from 10.1.1.3: bytes=32 time=8ms TTL=64
Reply from 10.1.1.3: bytes=32 time=9ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=9ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=8ms TTL=64
Reply from 10.1.1.3: bytes=32 time=7ms TTL=64
Reply from 10.1.1.3: bytes=32 time=8ms TTL=64
Reply from 10.1.1.3: bytes=32 time=8ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=9ms TTL=64
Reply from 10.1.1.3: bytes=32 time=11ms TTL=64
Reply from 10.1.1.3: bytes=32 time=8ms TTL=64
Reply from 10.1.1.3: bytes=32 time=7ms TTL=64
Reply from 10.1.1.3: bytes=32 time=9ms TTL=64
Reply from 10.1.1.3: bytes=32 time=10ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=7ms TTL=64
Reply from 10.1.1.3: bytes=32 time=9ms TTL=64
Reply from 10.1.1.3: bytes=32 time=11ms TTL=64
Reply from 10.1.1.3: bytes=32 time=8ms TTL=64
Reply from 10.1.1.3: bytes=32 time=21ms TTL=64
Reply from 10.1.1.3: bytes=32 time=4ms TTL=64
.
.
.
Reply from 10.1.1.3: bytes=32 time=7ms TTL=64
Reply from 10.1.1.3: bytes=32 time=7ms TTL=64
Reply from 10.1.1.3: bytes=32 time=6ms TTL=64
Reply from 10.1.1.3: bytes=32 time=11ms TTL=64
Ping statistics for 10.1.1.3:
Packets: Sent = 997, Received = 997, Lost = 0 (0% lost
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 47ms, Average = 9ms
Control-C
^C
And the observation of others that smart phones are interfering the extender seems accurate. Every five minutes my smart phone attempts to find access points and then the extender starts dropping ping packets. If I turn off my phone it appears to resolve the issue.
However this behavior is only exhibited on netgear products. My smart phone doesn't seem to affect any other manufactures products I have tested. To be fair the only other I have tested is Belkin
It appears netgear wireless products are overtly susceptible to interference.