I have a Netgear C7800 Nighthawk AC3200 WiFi Cable Modem Router. My ISP is Comcast with a 1 gigabit service and Outlook is used for email on a laptop. My Outlook client connects to an exchange server.
Once Outlook is started, it will send and receive for 5 minutes and then it hangs / freezes. It won’t send or receive email for 30 minutes (any emails I send sit in the Outbox). After that 30 minute delay is over, Outlook can send and receive emails for another 5 minutes followed by another 30 minute delay or pause in sending or receiving from the exchange server.
If I put the laptop to sleep or close Outlook and reopen Outlook, it will send/receive immediately. But the 5 minute/30 minute cycle starts over again. I’ve tried to force a send/receive by pressing send/receive, but that doesn’t make a difference with Exchange since everything should be instant. Essentially the only remedy is to close Outlook and restart.
I’ve reinstalled Outlook 3 times and have also made 6 calls to Comcast. The issue was escalated to Comcast’s security folks as well as Comcast’s senior tech folks. They all assure me that my Comcast gigabit service is not the issue and after hearing everything I’ve tried (below) they feel it must be something with the Nighthawk.
To eliminate my home wiring, I’ve tested my laptop connection using both a WiFi connection and a hard wired connection.
Prior to this C7800...I had a different Netgear router with a TP-Link modem and the issue didn't exist. Comcast has been my ISP for 15 years. The only change I made was to the C7800 to get the faster internet speed...and now I have this Outlook problem. Everything else works great and is fast! This is ONLY an Outlook issue related to the C7800. I can only assume there's some setting in the C7800 that needs to be changed to remedy the situation with Outlook that causes it to not be able to communicate with the Microsoft Exchange server after 5 minutes.
PLEASE HELP! I would really rather not return this C7800 because of this one issue with Outlook...but it is driving me crazy!
The original poster said this:
"The issue went to the developer. They provided a firmware fix which solved the problem. But I'm waiting for a hardware fix because the firmware fix is using the CPU to resolve what the hardware should be doing."
Can I get this firmware fix?
