or Connect
AVS › AVS Forum › Gaming & Content Streaming › Networking, Media Servers & Content Streaming › Netgear R7000 Nighthawk AC1900 Router Review and Comments Thread
New Posts  All Forums:Forum Nav:

Netgear R7000 Nighthawk AC1900 Router Review and Comments Thread - Page 12

post #331 of 618
Quote:
Originally Posted by Almighty2 View Post

anky,

Looking at all those ping outputs, those look normal and doesn't experience the problem as you stated earlier since a majority of your ping runs are 1ms all the way and only one packet out of a few pings were 2-3ms max with the rest at 1ms. Does the problem only happen during a certain time of day and did you happen to reboot or power-cycle the router not too long before you did it since if you did, that can also be the reason as I have seen some things work well after you boot it but act weird after some uptime.


It happens on its own, whenever it wants. And like I said earlier when it happens rebooting the router at that very moment doesn't fix it but a reboot of my laptop or desktop only fixes it. Pretty weird. I changed the channel for 5GHZ and saved the settings, so it rebooted to save the setting. I am not exactly sure whether I did it before the ping test or after it. So to retest I will wait for probably 3 days and then redo the test, is it okay or should I wait for some more time?

post #332 of 618
Quote:
Originally Posted by anky View Post


It happens on its own, whenever it wants. And like I said earlier when it happens rebooting the router at that very moment doesn't fix it but a reboot of my laptop or desktop only fixes it. Pretty weird. I changed the channel for 5GHZ and saved the settings, so it rebooted to save the setting. I am not exactly sure whether I did it before the ping test or after it. So to retest I will wait for probably 3 days and then redo the test, is it okay or should I wait for some more time?

If rebooting your laptop fixes it (and rebooting your router doesn't), I think that I'd focus my attention on the laptop. Maybe try a different wireless network adapter. Or maybe there's something wrong with the network configuration on your laptop, you could take a look at that as well. Finding out how to fix a problem points the finger at that piece of hardware and/or software as the first place to look.
post #333 of 618
Quote:
Originally Posted by RogerSC View Post

Got both of 'em from Newegg, the original and the replacement, RMA service by Newegg was really good. Nothing out of the ordinary on the box. I'm convinced that this problem is firmware, and it's definitely not a show-stopper, since when things are going well I don't have to reboot or power-cycle the router. Router (and cable modem) also on a sturdy UPS, so it doesn't get rebooted by power glitches, or even short power outages. The router stayed up for 7 days at one point before new firmware to try came around *smile*, and IPv6 was working the whole time for me. Given the performance of this router, I don't have a big problem with having to pull the WAN cable off the back when I have to reboot it, in fact I've put together a small hardware kludge to make this really easy *smile*. It would be nice if that got fixed, but so it goes, I can easily live with that one as long as I continue to get the great performance I've gotten so far.

I've never ordered anything other than memory from Newegg and they always ship using DHL's service that uses USPS to deliver it. Which carrier did Newegg use and for their RMA, did they provide the return shipping? Just a thought but wouldn't it work as well if you power cycle the R7000 or even just have a on/off switch between the outlet and the ac adapter that would achieve the same results?
post #334 of 618
Quote:
Originally Posted by RogerSC View Post

If rebooting your laptop fixes it (and rebooting your router doesn't), I think that I'd focus my attention on the laptop. Maybe try a different wireless network adapter. Or maybe there's something wrong with the network configuration on your laptop, you could take a look at that as well. Finding out how to fix a problem points the finger at that piece of hardware and/or software as the first place to look.
Quote:
Originally Posted by anky View Post


It happens on its own, whenever it wants. And like I said earlier when it happens rebooting the router at that very moment doesn't fix it but a reboot of my laptop or desktop only fixes it. Pretty weird. I changed the channel for 5GHZ and saved the settings, so it rebooted to save the setting. I am not exactly sure whether I did it before the ping test or after it. So to retest I will wait for probably 3 days and then redo the test, is it okay or should I wait for some more time?

I second what RogerSC said above as well.... There can also be another variable since just like people had problems with DSL, it can be because of things known to be over sensitive to RFI (Radio Frequency Interference). Lighting dimmer switches and/or electronic (non-magnetic) power supplies for halogen lighting are a common source of such interference. The result can be a degradation of performance or even a complete loss of signal, even when the source of the interference is not in close proximity to the router (because the interference can be not only radiated, but also conducted through building wiring). Interference is even possible when such switches and/or lights appear to be off, since some still generate interference even when turned off.
If you experience problems, particularly when those problems seem to be worse at certain times of the day, you can check for this possible cause by completely disconnecting all lighting dimmer switches and halogen lights. Putting the router on a power line RFI filter (included in many surge suppressors) may or may not solve the problem.

If you do determine that a lighting dimmer switch is causing interference, you may be able to solve the problem by replacing it with a switch that generates less interference (i.e., a switch with better RFI filtering). Cheap switches may have little or no RFI filtering; better switches that normally have good RFI filtering may be defective. Switches with good filtering are made by a number of manufacturers. And it can be your neighbors who is causing it as well.

On another subject to save from having to waste space in another post, I remember when the first AC routers came out which included the NETGEAR R6300, Linksys EA6500 and ASUS RT-AC66RorU, there was talk about this Android based router firmware being available called DROIDIFI http://www.droidifi.com/ - apparently it never did come out or otherwise we would yet have another choice.

There was something I forgot to mention...

Basically, I have a exisiting network that has Windows XP mahcines running on 192.168.1.0/24 connected to the GiGE Ethernet managed switch which is also where the DSL Modem configure as a bridge on 100BaseT and the R7000 is connected as 1000BaseT. As the R7000 is doing 192.168.2.0/24 which is where my Windows 7 clients are connected as they are wireless. I was trying to basically enable it so that the Windows machines on the R7000 can see the other Windows machines so that Windows file sharing connected to the GiGE Ethernet Managed switch will work. So I figured one way to do it would be to assign 192.168.2.0/24 static IP addresses to the Windows XP machines so that they are on the same network and also would probably require connecting a CAT6 cable between the GiGE Ethernet Managed switch to one of the GiGE Ethernet ports on the R7000. I didn't touch the IP assignment on the Windows XP machines connected to the GiGE Managed Ethernet switch yet but when I connected the CAT6 cable between the GiGE Ethernet Managed switch and the GiGE Ethernet port on the R7000, the R7000 basically seem to stop responding and after 10 minutes, unplugging the CAT6 on the R7000 didn't do anything as it was still not responding so I power cycled it with the CAT6 and the same problem happened so the only way to fix it is the unplug the CAT6 from the R7000. Does Windows Networking require it to be on the same network IP or does it actually use another protocol that is IP independent?
post #335 of 618
Quote:
Originally Posted by Almighty2 View Post

I've never ordered anything other than memory from Newegg and they always ship using DHL's service that uses USPS to deliver it. Which carrier did Newegg use and for their RMA, did they provide the return shipping? Just a thought but wouldn't it work as well if you power cycle the R7000 or even just have a on/off switch between the outlet and the ac adapter that would achieve the same results?

Newegg used UPS, and I had to pay the return postage (a nominal amount). Quick shipping for the price that I paid, I was okay with the whole process, especially since I basically wasted my time in hope that I had a bad router *smile*.

The internet connection loss with IPv6 enabled with Netgear's firmware happens when I power-cycle the router, or reboot it. That means that if I switch the power off and back on, either with the router's power switch or pulling the router's power cord, or reboot it via the GUI, it loses internet connection when it comes back up if IPv6 is enabled. I don't know if that will be a problem with dd-wrt, since IPv6 isn't implemented there yet, but I doubt that it will be, or wouldn't be very long, anyways. Kong's support is much more responsive than Netgear's *smile*.
post #336 of 618
Now that's interesting, I thought a power on would have fixed the problem, maybe they need to make RJ45 disconnect toggle switches just for this reason. LOL. For me, I just have to take the thing back to the vendor and they will have another one dropped shipped to me from their distributor and it seems like one can be sent a NAS or a PAS as they only list R7100 as the part # in their ordering system. So there are no restocking fees and I can get a refund too as a option so trying to create less of a hassle for the vendor who happens to be a friend of mines as he won't take orders like that normally.
post #337 of 618

Well I have a new R7000 that i recently just got. I went ahead, and loaded the latest beta firmware, which for me has been running pretty good. But today I notice when trying to connect a Netgear WN2500RP extender to the R7000 over the 2.4GHz band it wouldn't connect at all. The extender has the latest firmware that netgear made available, and it will connect to the 5GHz band but not the 2.4GHz band. I tried playing with all the settings on the R7000 didn't help. So maybe if/when Bob reads this thread again, he could maybe let netgear know for some odd reason there WN2500RP extender will not connect to this router over the 2.4GHz band. Everything else in my household so far is able to connect wirelessly as needed though.

 

Also I personally find the QoS feature that netgear is using on this router as junk. I don't like how they have the upstream/downstream setup. Upstream QoS is fine, but Downstream QoS doesn't make much sense with all its pre-configed crap(imo), it should be setup how the upstream side is.

post #338 of 618
Quote:
Originally Posted by Almighty2 View Post

Now that's interesting, I thought a power on would have fixed the problem, maybe they need to make RJ45 disconnect toggle switches just for this reason. LOL. .

Well, I did have 30 days to return it. Decided not to based on the fact that there is third party firmware for it (tomatoUSB is coming, too, looks like), and that when its running decent firmware, this router is a really great piece of hardware. At the moment, dd-wrt is working for me, we'll see about Netgear's next firmware release. If it's as bad as previous, there's still dd-wrt *smile*.

Edit: By the way, I did look for a switch for easy disconnect...the best I found was a 1 foot cable plus a cat 6 cable coupler. So I can just pull out one end of that instead of screwing around with the back of the router. Easy peasy *smile*. Not fond of the kludge, but has gotten a LOT of use.
Edited by RogerSC - 2/10/14 at 5:18pm
post #339 of 618
RogerSC, I have 90 days and basically have gone through about 45 days so far. Is tomato actually better than DD-WRT? I guess people can leave feedback on both the DD-WRT and the Netgear side so that they get everything we need and working so if there are problems, there is a choice.

Better breaking the coupler than either the router, maybe monoprice has something but probably not worth the hassle as you already have something working.

As far as QoS is concerned, I always knew the reason for upstream QoS but never knew the reason for the downstream QoS except it's more to make sure people get their gaming and streaming.
post #340 of 618

@Almighty2 Testing pings since yesterday to the router, I dunno what has happened but I am yet to experience that honky ponky ping pattern again. I just changed the channel for 5GHz band yesterday, but all my devices except my Galaxy S4 are running on the 2.4ghz band @ channel 6 since the beginning. My netgear wifi G usb adapter is able to ping the router at >1ms for 97% of the pings but today I noticed that outta 400-500 pings to the router there was one Request Timed Out and one ping was 583ms otherwise rest all were >1ms and a couple at 2-3ms. 

I did not try to get rid of any interference and nothing has changed around the router. And there hasn't been any driver updates for any of the WIFI Adapters I have.

 

EDIT: I was wrong, Just now after a reboot of system with the NETGEAR WIFI G Adapter, it happened again and rebooting the router, didn't fix it. Removing and re-plugging the USB adapter also doesn't seem to fix it.

 

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users>ping 10.0.0.1 -t

Pinging 10.0.0.1 with 32 bytes of data:
Reply from 10.0.0.1: bytes=32 time=536ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=538ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=535ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=533ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=532ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=530ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=534ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=529ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=527ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1528ms TTL=64
Reply from 10.0.0.1: bytes=32 time=12ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1022ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=976ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=975ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.0.1:
    Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1528ms, Average = 372ms
Control-C
^C
C:\Users\>

 

Also it seems to be fine on my laptop with TP-LINK wifi N adapter with normal pings.

 

EDIT 2: And Just after a while of pings. it fixed itself w/o a reboot. I did not turn on or off any gadget or any damn electronic thing in my house.

 

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users>ping 10.0.0.1 -t

Pinging 10.0.0.1 with 32 bytes of data:
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=6ms TTL=64

Ping statistics for 10.0.0.1:
    Packets: Sent = 6, Received = 6, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 6ms, Average = 1ms
Control-C
^C
C:\Users>ping 10.0.0.1 -t

Pinging 10.0.0.1 with 32 bytes of data:
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.0.1:
    Packets: Sent = 6, Received = 6, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms
Control-C
^C
C:\Users>ping 10.0.0.1 -t

Pinging 10.0.0.1 with 32 bytes of data:
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.0.1:
    Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms
Control-C
^C
C:\Users>ping 10.0.0.1 -t

Pinging 10.0.0.1 with 32 bytes of data:
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64

Ping statistics for 10.0.0.1:
    Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms
Control-C
^C
C:\Users>

 

I am badly confused :confused:


Edited by anky - 2/11/14 at 7:42am
post #341 of 618
anky, seems like the problem is worse when it comes back as your ping times went to 1500ms. 1000ms for reference is exactly 1 second. As for interference, you don't have to get rid of it since interference can be when you have certain things like lights when it is on. Does the problem come back if you let it idle for sometime without doing pings or traceroutes..... the sometime can be like 30 minutes or an hour.
post #342 of 618
Quote:
Originally Posted by Almighty2 View Post

anky, seems like the problem is worse when it comes back as your ping times went to 1500ms. 1000ms for reference is exactly 1 second. As for interference, you don't have to get rid of it since interference can be when you have certain things like lights when it is on. Does the problem come back if you let it idle for sometime without doing pings or traceroutes..... the sometime can be like 30 minutes or an hour.

Nope it doesn't. After that ping became alright. I left it idle without any pings or traceroute for about 1.5 hrs and then tried ping again and it didn't happen again.

post #343 of 618
Does it happen if you reboot the system, first making sure the pings are fine before you reboot?
post #344 of 618

Has anyone seen where to download version V1.0.3.22_1.1.19?  It is being discussed on the DD-WRT site as being released to only a sele10 ct group for testing, but it would be useful to have it for testing.

post #345 of 618
Quote:
Originally Posted by csm746 View Post

Has anyone seen where to download version V1.0.3.22_1.1.19?  It is being discussed on the DD-WRT site as being released to only a sele10 ct group for testing, but it would be useful to have it for testing.

I agree, it would be great to be able to test if my favorite bug has finally been fixed *smile*.
post #346 of 618
I would like someone to post V1.0.3.22_1.1.19 also smile.gif

Bob? Anyone?
Edited by dave1977nj - 2/11/14 at 5:26pm
post #347 of 618
For V1.0.3.22_1.1.19, I'm sure that's where Bob can help... Wonder if they brought telnet back! Until I read it a second time, I thought @csm746 actually said select ct group as either is some specific group or it's Connecticut! *smile* until I read it again and it really said select! biggrin.gif
post #348 of 618
Quote:
Originally Posted by Almighty2 View Post

Does it happen if you reboot the system, first making sure the pings are fine before you reboot?

Nope, Once its fixed, its not dependent on reboots. No matter how many reboots it doesn't happen. But if its happens its fixed by a reboot.

post #349 of 618
Next time when it happens, check to see if you have either snmp.exe or tcpsvcs.exe running.... If you do, kill the processes and see if it still happens.
post #350 of 618
I now have a "real world" installation with 7 R7000's running the .194 Firmware.

The site is a very large house with a detached guest house.

There is an R7000 in the Basement connected to a Cable Modem with 100 Mbps service. Wired Clients get Speedtest.net results of 100 Mbps.

There are 4 R7000 Access Points throughout the house and 1 at the Guest House.

There is an R7000 Bridge in the House providing access for wired devices in a location without a cable drop.

My 3rd generation iPad gets speeds between 30 an 40 Mbps throughout the house in either the 2.4 or 5 MHz bands.

My MacBook Air with AC capability gets close to 100 Mbps at 5 MHz and close to 50 Mbps at 2.4 MHz.

I will be implementing OpenVPN in the next few days.

Set up was as easy as any other Netgear devices I have used and went smoothly.

Physical installation and cut over went smoothly.

There was some discussion about the SSID's I had chosen and the Client wanted them changed. I gave the client a list of the static IP's of the 7 devices and he has changed 6 of them himself. Obviously, the Bridge needs to be updated via a wired connection and I will do that on my next visit.

I will be posting from time to time on our experiences with the installation.
post #351 of 618
hey Bob


Any updated on newer firmware builds being pushed out soon?
post #352 of 618
Thread Starter 
Beta Firmware Update 2/12/2014

Here is the link to the latest beta from Netgear V1.0.3.24


https://www.dropbox.com/s/r7cmamco132jmea/R7000-V1.0.3.24_1.1.20.chk

Enjoy everyone.

Bob Silver
Netgear AV Consultant
post #353 of 618
Bob, many thanks for 1.0.3.24!

Is there a trick to get telnet to work again?
post #354 of 618
Thank you BOB!!!!
post #355 of 618
Thanks Bob, we knew you will deliver and even have a newer version than what others have! biggrin.gif
Edited by Almighty2 - 2/12/14 at 12:17pm
post #356 of 618
Quote:
Originally Posted by 42LBX View Post

Bob, many thanks for 1.0.3.24!

Is there a trick to get telnet to work again?

Dagnab it *smile*, same problem with telnet as the previous beta.

Hopefully we'll hear how to enable telnet, or they'll have it fixed by the final release.

And many thanks for the opportunity to test a new beta, much appreciated!
post #357 of 618
RogerSC, hopefully they did not remove the telnet feature so people don't mess with their routers... There goes the region unlock hack but thankfully people can :cool:flash a older version first....
Edited by Almighty2 - 2/12/14 at 1:04pm
post #358 of 618
Still have my Comcast "power-cycle or reboot with IPv6 enabled, lose internet connection" bug.

Too bad.

Back to dd-wrt *smile*.
post #359 of 618
@RogerSC, wow, that was fast. I still haven't had a chance to install it yet since I''m still trying to test ipv6rd in dd-wrt using the CLI once I figure out the correct parameters to put in... Maybe that bug of yours still hasn't been reported to Netgear. there is still 16 days remaining in February for the official non-beta firmware to come out. As the new beta still has telnet disabled, I'm not in a big hurry to test it since I need the CLI to do the ipv6 config that is not available in the web interface.

@anky, one thing I thought of. If you are running Windows 7 or 8,. grab the following software and look at the lights which is what this program does, as it's a missing feature in Windows 7 or 8 that was in XP and earlier versions of Windows. Look to see if the lights is more solid than usual when the problem happens because I have seen cases where there is some process that runs that floods the network using whatever Network Interface Adapter you have.

http://www.gabsoftware.com/products/applications/gabnetstats/
post #360 of 618
Quote:
Originally Posted by bobsilver View Post

Beta Firmware Update 2/12/2014

Here is the link to the latest beta from Netgear V1.0.3.24


https://www.dropbox.com/s/r7cmamco132jmea/R7000-V1.0.3.24_1.1.20.chk

Enjoy everyone.

Bob Silver
Netgear AV Consultant

Thanks BOB!
New Posts  All Forums:Forum Nav:
  Return Home
AVS › AVS Forum › Gaming & Content Streaming › Networking, Media Servers & Content Streaming › Netgear R7000 Nighthawk AC1900 Router Review and Comments Thread