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

Forum Discussion

ezicefield's avatar
ezicefield
Follower
Jan 27, 2016

C7000-100NAS randomly drops internet connection

Hello,   My C7000-100NAS modem seems to randomly drop it's Comcast connection. This happen on 2.4 ghz, 5 ghz, and wired connections. There is no pattern, however the dropped connection usually last...
Firmware
Hardware
Troubleshooting
polishkaz's avatar
polishkaz
Guide
Jan 09, 2017

DarrenM, I ended up having to buy another companies Modem and router and everything works perfectly.  Haven't had a drop out in weeks.  I am not sure what is up with this product but it is certainly not worth the money I paid for it and we should be refunded.  The thing worked in Bridge mode without dropouts but thats not what I bought it for.  Lesson learned, no more Netgear products.  

reustin's avatar
reustin
Initiate
Jan 27, 2017

We have this router as well - wanted to add my complaint to the list and also ask some questions.  I'm a little surprised no one has included this info: what kinds of machines/operating systems do you guys have?

 

We have two MacBook Airs running El Capitan (10.11.6).  These are our main computers and they both drop the internet connection every 3-15 minutes.  It's MADDENING.  We have the 2.4 and the 5 GHz networks set up, so when it freezes, we just switch to the other one and it gets us another 3-15 minutes.  

 

But on our other devices the connection is fine and never drops out:

Toshiba PC running Win 7

2 iPhones running iOS 9.3

Apple TV 

...so it seems to just be the mac computers.

 

Do you guys that are having problems also experience them on Macs or only on Macs or on other types of devices?  

 

Thanks.

  • NCsandhills's avatar
    NCsandhills
    Guide
    Jan 27, 2017

    The "wi-fi" connection depends on two pieces of hardware. The PC's adapter and the Modem/Router.

    Since some of the connected units remain "connected" while the MacBooks tend to disconnect - you may need to check the adapter's hardware and settings.

    Maybe the adapter's "energy or sleep setting" is allowing the adpater to turn-off when transmission is inactive??  Otherwise, check if the adapter's drivers are up to date, and if the settings are correct. The situation you are experiencing suggests that the problem is most likely the Mac PC's, and their adapter hardware and/or settings -- or possibly some other MacBook setting that causes the disconnect. 

    • reustin's avatar
      reustin
      Initiate
      Jan 27, 2017

      Thanks for your reply!

      Absolutely agreed–it must be something about the MacBooks' ethernet adapters or their firmware/drivers/software specifically.  However, neither of us experience this issue with any other WiFi access points, so it's also something about the combination of our computers AND this particular make & model of router (and we had no issues until we got this router recently). Neither Apple or Netgear is off the hook!

      I was hoping to see if other people here were experiencing this correlation of it happening specifically with Macs as well.

      PS: As to sleeping/inactivity; this happens while we are in the middle of streaming or browsing etc. 

      P.P.S. I'm also an NC native (triangle area) :)

       

  • 8th_Day's avatar
    8th_Day
    Aspirant
    Jan 27, 2017


    We us both Mac and Windows on our network.  They are wired and not wireless.  We have issues with both. 

     

    Windows 10 Pro - Toshiba

     

    Macintosh ElCapitan 10.11.6 - Imac 27in

     

    This is getting so bad, that we almost couldn't use the internet yestserday at all.  Here is the log taken this morning at 9:30.

     

    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Fri Jan 27 09:00:48 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Fri Jan 27 09:08:34 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.76.76, port 53Fri Jan 27 09:12:52 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 09:35:18 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 09:41:30 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 09:47:58 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.76.76, port 53Thu Jan 26 10:01:31 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 10:10:58 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 10:15:15 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.76.76, port 53Thu Jan 26 10:22:44 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.76.76, port 53Thu Jan 26 10:38:43 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 10:52:31 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 11:10:30 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.76.76, port 53Thu Jan 26 11:37:25 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.76.76, port 53Thu Jan 26 11:45:00 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 11:50:11 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.76.76, port 53Thu Jan 26 11:55:33 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 12:05:37 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 12:10:07 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 12:13:58 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 12:15:18 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 12:20:37 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 12:25:32 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 12:38:58 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 12:46:40 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.76.76, port 53Thu Jan 26 12:48:57 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 12:54:22 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 12:58:07 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 13:08:37 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 13:16:09 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 13:35:50 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 13:54:54 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 14:09:41 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.76.76, port 53Thu Jan 26 14:24:34 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 14:25:47 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 14:34:35 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 14:37:45 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.76.76, port 53Thu Jan 26 14:38:32 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 14:45:13 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 15:20:04 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 16:38:44 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 17:13:46 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.76.76, port 53Thu Jan 26 17:14:01 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 17:15:56 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 17:20:04 2017
    [DoS attack: TCP- or UDP-based Port Scan] from 75.75.75.75, port 53Thu Jan 26 17:43:39 2017
    • polishkaz's avatar
      polishkaz
      Guide
      Jan 27, 2017

      Mac's, Iphones, Smart Tv's, Playstation 4's everything loses.  Going on a month now, not a single disruption to my internet with the new Modem and Router.  Do yourselves a favor, buy some new equipment and let me know when that class action lawsuit happens, I'll sign on board.  

      • garybaird's avatar
        garybaird
        Tutor
        Jan 28, 2017

        I don't know if I need to be notified when the class action happens. I am comfortable to know that I will never purchase another Netgear product EVER. I have save all of my many devices over the years for some dumb reason. But, I threw this Netgear device and all previous devices in the trash. I have replace this setup with ASUS and it works great. Since then, I have bought other equipment like wireless extenders. Even though Netgear claims to have good stuff in these areas, I did not buy theirs and NEVER EVER will again EVER>