NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

MaxNolder's avatar
MaxNolder
Tutor
Aug 03, 2021
Solved

R6700v3 firmware 1.0.4.118 caused connection problems

Thunderbird could not connect to imap servers. SplashTop said no internet. TomTom MyDrive Connect said no internet. Chrome would say site unavailable and then later connect. I went back to previo...
  • delerick's avatar
    delerick
    Sep 24, 2021
    New 120 Rev appears to be out and fixes the issue, along with others. Running it 5 days now, so far so good.
plemans's avatar
plemans
Guru - Experienced User
Aug 03, 2021

After the install, did you try a factory reset? 

If there's an issue after a firmware upgrade, thats one of the first things we recommend. 

  • MaxNolder's avatar
    MaxNolder
    Tutor
    Aug 08, 2021

    Yes I tried the factory reset after the firmware update amd saw no change.

  • cochese187's avatar
    cochese187
    Tutor
    Aug 09, 2021

    this router firmware is terrible especially the latest....this company still has not release a latest firmware to give me the speed I pay my ISP for......I have to revert all the way to 1.0.2.50 in order to get my bandwith....there is a big problem here and netgear needs to address and fix......test yourself its broken.  Security vunerability or better speeds.  I have not been able to get the router to get any better then 200mbs with newer firmwares.  I have done all the factory resets and all specified....no joy 

    • RepulsiveCoder's avatar
      RepulsiveCoder
      Aspirant
      Oct 02, 2021

      Had same issue (DNS error eveytime first time a new site is open) with latest update to 1.0.4.120. I thought DNS error was from ISP, then remove this router and directly connect my PC to Load Balancer and found no problem.

       

      Today I found that 172.16.27.1 is unreachable from my pc, ip 172.16.1.13/24 and Router's WAN ip is 192.168.0.2/24 and traceroute was looping. Then I downgraded the Firmware to 1.0.4.106  and problem resolved.

       

      tracert 172.16.27.1   ----   V1.0.4.120_10.0.91

      Tracing route to 172.16.27.1 over a maximum of 30 hops

      1 <1 ms <1 ms <1 ms READYSHARE [172.16.1.1]
      2 * * * Request timed out.
      3 <1 ms <1 ms <1 ms READYSHARE [172.16.1.1]
      4 * * * Request timed out.
      5 <1 ms <1 ms <1 ms READYSHARE [172.16.1.1]
      6 * * * Request timed out.
      7 1 ms <1 ms <1 ms READYSHARE [172.16.1.1]
      8 * * * Request timed out.

      tracert 172.16.27.1   ----   V1.0.4.106_10.0.80 

      Tracing route to 172.16.27.1 over a maximum of 30 hops

      1 <1 ms <1 ms <1 ms READYSHARE [172.16.1.1]
      2 1 ms <1 ms <1 ms 192.168.0.1
      3 1 ms 2 ms 2 ms 172.16.27.1

      Trace complete.