NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
jasonleschnik
Oct 17, 2010Aspirant
Problems with WN2000RPT Range Extender
Hi all! Just bought a WN2000RPT range extender and i have it all setup. I'm having a strange problem where every couple of hours randomly my hosts on the other LAN segment seem to not be able to pi...
jerryv
Dec 08, 2010Aspirant
yeah, I have the same problems. Every now and then (and it seems like about 24 hours of uptime) it starts dropping connections. I get some connects still work across the router but drop randomly.
64 bytes from 10.1.1.7: icmp_seq=17 ttl=64 time=2.795 ms
64 bytes from 10.1.1.7: icmp_seq=18 ttl=64 time=4.248 ms
64 bytes from 10.1.1.7: icmp_seq=19 ttl=64 time=3.400 ms
64 bytes from 10.1.1.7: icmp_seq=20 ttl=64 time=3.553 ms
64 bytes from 10.1.1.7: icmp_seq=21 ttl=64 time=6.592 ms
64 bytes from 10.1.1.7: icmp_seq=22 ttl=64 time=9.186 ms
64 bytes from 10.1.1.7: icmp_seq=23 ttl=64 time=3.126 ms
64 bytes from 10.1.1.7: icmp_seq=24 ttl=64 time=2.936 ms
64 bytes from 10.1.1.7: icmp_seq=25 ttl=64 time=4.230 ms
64 bytes from 10.1.1.7: icmp_seq=26 ttl=64 time=2.732 ms
64 bytes from 10.1.1.7: icmp_seq=27 ttl=64 time=2.742 ms
64 bytes from 10.1.1.7: icmp_seq=28 ttl=64 time=3.179 ms
64 bytes from 10.1.1.7: icmp_seq=29 ttl=64 time=2.860 ms
64 bytes from 10.1.1.7: icmp_seq=30 ttl=64 time=9.084 ms
64 bytes from 10.1.1.7: icmp_seq=31 ttl=64 time=5.792 ms
64 bytes from 10.1.1.7: icmp_seq=32 ttl=64 time=275.768 ms
ping: sendto: No route to host
Request timeout for icmp_seq 33
64 bytes from 10.1.1.7: icmp_seq=34 ttl=64 time=223.035 ms
ping: sendto: No route to host
Request timeout for icmp_seq 35
Request timeout for icmp_seq 36
64 bytes from 10.1.1.7: icmp_seq=37 ttl=64 time=192.112 ms
64 bytes from 10.1.1.7: icmp_seq=38 ttl=64 time=3.670 ms
64 bytes from 10.1.1.7: icmp_seq=39 ttl=64 time=2.684 ms
64 bytes from 10.1.1.7: icmp_seq=40 ttl=64 time=3.692 ms
64 bytes from 10.1.1.7: icmp_seq=41 ttl=64 time=12408.304 ms
Request timeout for icmp_seq 42
Request timeout for icmp_seq 43
Request timeout for icmp_seq 44
Request timeout for icmp_seq 45
Request timeout for icmp_seq 46
Request timeout for icmp_seq 47
Request timeout for icmp_seq 48
Request timeout for icmp_seq 49
Request timeout for icmp_seq 50
Request timeout for icmp_seq 51
some connections dont work at all (but come back after 10-20 minutes)
I get a lot of DCHP ack and OFFER retries in my DSL modem logs.
Do you have apple stuff on your network. Maybe the IPv6 stuff that apple uses is confusing the forward table on the device ????
Would be very interested in comparing notes.
btw what is your DCHP lease time?
my config is
DSL router (and DHCP server) physically connected to an airport express (in bridge mode) and then the repeater is downstairs with about 4 wireless devices 'connected' to it
64 bytes from 10.1.1.7: icmp_seq=17 ttl=64 time=2.795 ms
64 bytes from 10.1.1.7: icmp_seq=18 ttl=64 time=4.248 ms
64 bytes from 10.1.1.7: icmp_seq=19 ttl=64 time=3.400 ms
64 bytes from 10.1.1.7: icmp_seq=20 ttl=64 time=3.553 ms
64 bytes from 10.1.1.7: icmp_seq=21 ttl=64 time=6.592 ms
64 bytes from 10.1.1.7: icmp_seq=22 ttl=64 time=9.186 ms
64 bytes from 10.1.1.7: icmp_seq=23 ttl=64 time=3.126 ms
64 bytes from 10.1.1.7: icmp_seq=24 ttl=64 time=2.936 ms
64 bytes from 10.1.1.7: icmp_seq=25 ttl=64 time=4.230 ms
64 bytes from 10.1.1.7: icmp_seq=26 ttl=64 time=2.732 ms
64 bytes from 10.1.1.7: icmp_seq=27 ttl=64 time=2.742 ms
64 bytes from 10.1.1.7: icmp_seq=28 ttl=64 time=3.179 ms
64 bytes from 10.1.1.7: icmp_seq=29 ttl=64 time=2.860 ms
64 bytes from 10.1.1.7: icmp_seq=30 ttl=64 time=9.084 ms
64 bytes from 10.1.1.7: icmp_seq=31 ttl=64 time=5.792 ms
64 bytes from 10.1.1.7: icmp_seq=32 ttl=64 time=275.768 ms
ping: sendto: No route to host
Request timeout for icmp_seq 33
64 bytes from 10.1.1.7: icmp_seq=34 ttl=64 time=223.035 ms
ping: sendto: No route to host
Request timeout for icmp_seq 35
Request timeout for icmp_seq 36
64 bytes from 10.1.1.7: icmp_seq=37 ttl=64 time=192.112 ms
64 bytes from 10.1.1.7: icmp_seq=38 ttl=64 time=3.670 ms
64 bytes from 10.1.1.7: icmp_seq=39 ttl=64 time=2.684 ms
64 bytes from 10.1.1.7: icmp_seq=40 ttl=64 time=3.692 ms
64 bytes from 10.1.1.7: icmp_seq=41 ttl=64 time=12408.304 ms
Request timeout for icmp_seq 42
Request timeout for icmp_seq 43
Request timeout for icmp_seq 44
Request timeout for icmp_seq 45
Request timeout for icmp_seq 46
Request timeout for icmp_seq 47
Request timeout for icmp_seq 48
Request timeout for icmp_seq 49
Request timeout for icmp_seq 50
Request timeout for icmp_seq 51
some connections dont work at all (but come back after 10-20 minutes)
I get a lot of DCHP ack and OFFER retries in my DSL modem logs.
Do you have apple stuff on your network. Maybe the IPv6 stuff that apple uses is confusing the forward table on the device ????
Would be very interested in comparing notes.
btw what is your DCHP lease time?
my config is
DSL router (and DHCP server) physically connected to an airport express (in bridge mode) and then the repeater is downstairs with about 4 wireless devices 'connected' to it