NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
No internet access after installing firmware update 1.0.4.18
Soon after installing firmware update 1.0.4.18 on my Nighthawk R8000 webpages failed to load from all connected clients
My ISP tested my internet service and no issues where reported
Inbound con...
I installed the latest firmware update V1.0.4.28_10.1.54 and enabled standard parental controls and so far so good internet is working fine
The update did fail to install a few times over wifi but I got it to sucessfully install after I turned off my nighthawk wifi extender EX7300
I updated from V1.0.4.18_10.1.49 to V1.0.4.28_10.1.54 and noticed I had to enable the smart connect feature again after the update got installed
Other issues are reported on this thread that I didn't experience
I opened this discussion for internet access issues with V1.0.4.18_10.1.49 and after I installed the latest firmware V1.0.4.28_10.1.54 my internet access issues (with standard parental contols enabled) seem to be fixed.
TerryPh, OK, I've attached the 3.0 USB flash drive, see JPG on right.
That should be good enough to see if I'll have problems, especially since it is not powered so it will take some amperage to work?
Have no problem seeing it with NET VIEW (and SMB1 enabled):
=============
C:\>net view
Server Name Remark
-----------------------------------------------------------------------------
\\IRV8700 Irv's 8700
\\LARAINE-XPS8500 Laraine's XPS8500
\\READYSHARE readyshare
The command completed successfully.
C:\>net view \\readyshare
Shared resources at \\readyshare
readyshare
Share name Type Used as Comment
-----------------------------------------------------------------------------
Movies Disk read:all-no password;write:all-no password
S_Drive Disk read:all-no password;write:all-no password
USB_2.0_Storage Disk read:xxxx;write:xxxxxx
The command completed successfully.
=====
It is my W10 Media Install Disk:
=============
C:\>dir \\readyshare\s_drive
Volume in drive \\readyshare\s_drive is S_Drive
Volume Serial Number is 5464-8354
Directory of \\readyshare\s_drive
The parameter is incorrect.
<DIR> .
01/01/2015 01:00 AM <DIR> ..
09/29/2017 05:59 AM 128 autorun.inf
01/11/2018 09:01 AM <DIR> boot
09/29/2017 11:08 AM 397,752 bootmgr
09/29/2017 11:08 AM 1,236,376 bootmgr.efi
01/11/2018 09:01 AM <DIR> efi
03/17/2018 09:15 AM <DIR> netgear_downloader
09/29/2017 11:08 AM 80,696 setup.exe
01/11/2018 09:01 AM <DIR> sources
01/11/2018 09:03 AM <DIR> support
01/11/2018 09:01 AM <DIR> System Volume Information
4 File(s) 1,714,952 bytes
8 Dir(s) 27,807,318,016 bytes free
========
As you can see, the router added the NETGEAR_DOWNLOADER the last time I had it attached.
I just copied a .MOV file to it (slow, 30Mbps??? to a 3.0 drive ???):
C:\>dir \\readyshare\s_drive\*.mov
Volume in drive \\readyshare\s_drive is S_Drive
Volume Serial Number is 5464-8354
Directory of \\readyshare\s_drive
07/16/2017 02:38 PM 339,699,496 MVI_4394.MOV
1 File(s) 339,699,496 bytes
0 Dir(s) 27,467,612,160 bytes free
===================
That surely made the dlna catalog be updated.
We'll see if I now get some problems?
Did you notice the 'ERROR' above about the single '.' directory. When I ran the command again, it was fine???? no error???
===========
The parameter is incorrect.
<DIR> .
===========
See, no error:
------------
C:\>dir \\readyshare\s_drive\
Volume in drive \\readyshare\s_drive is S_Drive
Volume Serial Number is 5464-8354
Directory of \\readyshare\s_drive
06/09/2018 03:00 PM <DIR> .
01/01/2015 01:00 AM <DIR> ..
09/29/2017 05:59 AM 128 autorun.inf
01/11/2018 09:01 AM <DIR> boot
09/29/2017 11:08 AM 397,752 bootmgr
09/29/2017 11:08 AM 1,236,376 bootmgr.efi
01/11/2018 09:01 AM <DIR> efi
07/16/2017 02:38 PM 339,699,496 MVI_4394.MOV
03/17/2018 09:15 AM <DIR> netgear_downloader
09/29/2017 11:08 AM 80,696 setup.exe
01/11/2018 09:01 AM <DIR> sources
01/11/2018 09:03 AM <DIR> support
01/11/2018 09:01 AM <DIR> System Volume Information
5 File(s) 341,414,448 bytes
8 Dir(s) 27,467,612,160 bytes free
=======
Wonder if it had anything to do with writing the MOV file there and it had to update the directory?
Thanks for a detailed post. Greatly enjoy reading it.
I will keep an open mind and try to digest all the information that you provided. My mind is working toward compiling all the facts and relate to
NG what we are facing in terms of dealing with persisting faults. I have to admit to myself that this kind of router behaviors are not really acceptable, and NG should DO something about it.
TerryPh wrote:
Thanks for a detail post. Greatly enjoy reading it.
I will keep an open mind and try to digest all the information that you provided. My mind is working toward compiling all the facts and relate to
NG what we are facing in terms of dealing with persisting faults. I have to admit to myself that this kind of router behaviors are not really acceptable, and NG should DO something about it.
One thing I'd have liked, the DEBUG.HTML page that the R7000 has/had? I didn't use it much but it did allow a look at some stuff you couldn't garner other ways.
My personal feeling is that the CPU is somehow involved...
IrvSp -
--- DEBUG.HTML page that the R7000 has/had? I didn't use it much but it did allow a look at some stuff you couldn't garner other ways.
My personal feeling is that the CPU is somehow involved...---
That is what I have been thinking about all along. More than that, it is also involving the memory allocation and utilizing (catch/release). Software engineers did not accomplish this very well in their firmware scripts. This can only be accomplished (in terms of hardware capacity) with a fresh software design, and hopefully with new management, they will accomplish it.... Just have to cross the finger...
Terry
TerryPh, when I was looking to replace the R7000 I wanted an upgrade... The R7000 had all the features I wanted. I was 'happy' with NG as I've had other vendors routers and I didn't think 'they' or the vendor's support was any better, so a NG router was OK. I did want a speed increase. Both the R7000 and R8000 have the same CPU. I did find a review with this:
=========
Both Nighthawks have 1GHz CPU’s. Essential for processing the wireless Gigabit data flows, concurrent sessions, Quality of Service etc. The X6 R8000 does have another trick up it’s sleeve though. It has 3 offload processors, which take the strain off the main dual core. Gigabit networks can take their toll on network hardware, so having offload processors is a very welcome relief!
=========
I personally think that is where the possible problems lie, the offload processors (not really sure what they are either?) and how they work and coordinate data movement.
From my experience, both routers seem to have the same 'amount' of false positives in the log. I had thought that was due to the CPU losing track of a packet, either in or out, due to congestion or stress. If that is the case, those offload processors would surely cure this. Didn't happen... matter of fact, I can't find ANY info on those offload processors, what they are and how they help?
That DEBUG.HTM on the R7000 woudl show the CPU load, really missing that in the R8000.
Basically the R7000 is about 4 1/2 years old, should have been quite stable by now. Still, programmers seem capable of messing up what fixing security holes and minor changes. The R8000 is 4 years old, and I'd expect it to be stable as well. It certainly seems to have many less firmware releases than the R7000. From what it seems to me, the R8000 is basically an R7000 with 2 5Ghz radio's. I'd suspect any 'design' problems that the initial R7000 had would have been overcome, and probably more RAM and NVRAM were included.
I think NG has to really look at the firmware and discover why some have no problems (with minimal enabling of features) and others that enable more have problems. I don't think it is the features themselves that are the problem, as they do work 'alone' or with less other 'stuff' enabled it seems.
We can only hope they do....
- I do hope that they will take a fresh look at the issues at hand, rather than to around. 1."Dog chasing tail" seems to be the ongoing approach now at the software designing team.
2. They have to admit sometimes the more is not necessary the merrier, taking into account of hardware limitation much more seriously than they thought it should be ok to dump new feature(s) into the router without thoroughly and careful implementation of such features.
I'm not sure at the moment whether there is a change in higher level management at NG that could resolve into a revutationary and drastic change in the way their software department work, but hopefully with piles of problems, they will pay attention...