
Problem: After 6 months of perfection, Eero stopped connecting to Consolidated Communications Inc (CCI) fiber
I've had Consolidated Communications Inc (CCI) 50mbps fiber for nine months. Had Eero Pro (with two Beacons) for six months. Worked perfectly. Stopped working last night. I have ONT on the side of my house and an ethernet plug in home office. No router/modem inside. Took ethernet cable directly from my wall to my laptop and I have 50mbps connectivity. Pulled the Eero beacons out of the plugs. Unplugged Eero base station and replugged. Hard reset base station. Deleted app and reinstalled. Called Eero and CCI and neither could help. When I am using the app to set up the Eero base station it goes through this sequence:
Eero Pro detected - OK
Where is your Eero Pro -- OK
Connecting to the Internet - OK
Registering your Eero Pro -- this is where it hangs up, and gives we "We're having trouble connecting to the Internet."
-
Same exact setup and issue here with consolidated. Consolidated told me they have had many calls from eero customers. I did get one eero support person to tell me they were aware of the issue over the phone but I would have to wait for the next update to see if it gets fixed. Support over email has been terrible.
-
Hey all.
when this issue happened originally I ordered a new eero thinking mine had died. Since then I’ve used the double nat approach with success.
tonight I’m going to try the new eero that arrived, directly connected to the fiber line. This should give us more clarity on whether this is an eero issue or consolidated issue. I’ll report back!
-
I spoke to Eero just over a week ago further trying to resolve this. Long story short, a dude from CCI came out and has seen this issue multiple times between Eero / CCI. He was POSITIVE its on Eeros end and I believe him! He has been able to troubleshoot onsite and is 100% confident the Eeros have somehow stopped attaining an IP address due to firmware issues, not CCI
After speaking with Eero again, they raised the ticket to the next level and said they will contact CCI. I haven't heard anything back. -
I’ve had the same Eero CCI issue. I know at least since May 21. I had CCI out after Eero also said it was an issue on the CCI end, but when they arrived everything worked and when i plug Macbook directly in I had great speed. CCI phone tech told me before scheduling tech visit that they doubt it was going to fix the issue because they we seeing this with other Eero owners. After hours on the phone with Eero it was sent to the “escalations team”. I’m also running double nat waiting on an Eero fix. I reached out again June 9 and on June 11 was told still with engineering team. Last I’ve heard from Eero. Seems we may be a “small issue group” with no real concern for resolution.
-
Any update on this? Had the same problems at my parents I was originally told from eero (took 1hr20min to get to a tech that Consolidated switched to PPoE (even though it's still DHCP to my ASUS) and that's why this is happening. It's been double NAT since and would love to get back to the way it was.
-
I received a call from Consolidated Tech out of the blue yesterday, August 19, to update me. Impressed since it was three months ago they came to the house to assist in troubleshooting and I have not considered contacting Consolidated since. Double NAT was their recommendation until Eero makes a firmware change related to the DHCP issue. Consolidated said they have been working with Cisco, Eero, and other ISPs and have come to the conclusion it is the Eero software/firmware that is causing the current conflict.
In disappointment, Eero has not responded to my email requesting an update to the open ticket in over a month. I ended up connecting on Eero Twitter Support and received a response that it is still a problem and use double NAT.
-
I spent a few minutes to get a packet capture between my eero and my Nokia/Alcatel ONT as the eero boots. I can see the dhcp request/discover/offer/ack go through, and then the eero sends an arp to get the MAC address of the router from the dhcp offer, which it receives. The eero then sent a DNS request using a 192.168.4.75 address which corresponds to a device on my internal network, and continues attempting to send packets using internal addresses to the public internet.
I only had a single cable connected to the gateway eero when I was obtaining the capture so I’m reasonably sure it’s an eero firmware bug, possibly related to the Consolidated issue mentioned in this thread.
-
I registered just to post in this thread. I received my Eero Pros yesterday and I am also on CCI with their 100Mb service. My previous setup was a TP-Link Archer C9 router and a couple wireless extenders. I had 7 SSIDs to cover my house/yard and couldn't wait to consolidate it into one network.
First off, and not really relevant to the OP, but worth mentioning, the Bluetooth pairing/set up didn't work at ALL. I sat there for probably an hour re-trying it and letting it sit forever. Just got the spinning loading wheel the whole time. I got a 3-pack of Pros and tried them all; nothing. I was so annoyed and ready to return them at this point. Thankfully out of desperation I tried to disable Bluetooth on my phone and a button magically appeared that let me set it up by entering the serial number manually. Why that option didn't exist with BT enabled, I have no idea. That needs addressed because I was real close to returning my units at this point.
More to the point of the OP, once I got the gateway node set up, I received the same exact issues:
Eero Pro detected - OK
Where is your Eero Pro -- OK
Connecting to the Internet - OK
Registering your Eero Pro -- "We're having a problem" or something similar. No error message about not being able to see the internet despite progressing past the "connecting to the internet" phase without issue. It should have thrown an error at that point, but I'm guessing it doesn't actually try to hit the internet until it gets to the registering phase, for some odd reason.I sat there for probably another hour trying to figure out what the heck is going on. It wasn't until I found this thread via google search that I tried putting my original TP-Link router in between my incoming connection and the Eero gateway with wireless radios disabled. Boom, magically worked. This is super annoying, because I went from having a single router to having a TP-Link router, an Eero Pro, and a gigabit switch hanging off the Eero since it only has 1 output connection. I was trying to clean up my setup but made it way messier with more cables.
I'm hoping this is resolved via Eero firmware, since it seems to be an issue on Eero's end, but seeing as this issue has persisted for 6 months, I'm not hopeful at all. Especially since it seems to only be an issue with CCI, which I'm guessing is a tiny tiny fraction of it's users. This is a really annoying workaround and I'm really disappointed. If I didn't find this thread, I would have been returning my 3-pack today for sure.
-
I bought an Eero just to troubleshoot this (wanted to see what was happening on the wire) and I found a fix: if you power down your ONT after disconnecting your other router, it works. That means disconnecting the backup battery, typically in the garage, as well. The Eero needs to be the first router that the Zhone ONT sees.
Once fixed, it seems to persist through reboots. Hope this helps.
-
I just purchased the eero 6 pro as an upgrade to my orbi since I have gigabit from CCI. I spent 4 hours today trying to get it to work. Called eero first and got a rude CS which pretty much told me I am screwed. I call back and the other CS person was very helpful but still didn't fix the issue but gave me some information to call CCI with. He walked me through pretty much the steps listed above. Super disappointed and believe this is something to do with the eero unit and not my ISP. Not the experience I was expecting with $600 router. Time to return them. I really wanted them to work.