After Upgrade from Nest WiFi to Nest WiFi Pro - Chomecast Connectivity Issues

[collinsc]

Appreciate any help -

I recently upgraded our home from the old Nest WiFi (2019) to Nest WiFi Pro. I have the main router on center floor, and points on the floors above and below with wired backhaul. I have 3 older gen Chromecasts, again 1 on each floor, and my wife and I both have Pixel 6's.

My Pixel is able to connect to all 3 Chromecasts without issue; my wife cannot. In checking the connection, both are connected through 5 GHz now (that was the first issue, hers was picking up 6 GHz more), same gateway; however going to various apps to cast as well as direct screen mirroring, I can see all three Chromecasts and she cannot. I've rebooted her phone, the Chromecasts, the router, factory reset on the chromecast - nothing.

Any ideas? Thanks in advance!

[PatrickP_Viking]

Hey @collinsc .

What device is she using?

[collinsc]

Hi Patrick - we were both using Pixel 6's. I think I found the issue, but I don't quite understand it yet.

It appears that the wired backhaul on the points is the issue. Once I disconnected the ethernet connection on both points, it resolved her issue in accessing the Chromecasts, and also resolved an issue I was having with Sonos not finding the devices.

However, the wired backhaul for the points on the mesh was half the reason I upgraded in the first place - with a point in the basement and a point on the second floor, we were having latency issues, particularly in using the Chromecasts on those floors.

[PatrickP_Viking]

Thanks for the additional information @collinsc .

This article (Hardwire Wifi devices with Ethernet ) validates that connecting them as you did work and I have mine backhauled with switches so there's a few things I can think of that can cause what you described:

1. The Sonos and wife's phone don't recognize the network - When you changed the setup to the Pro and how the mesh was connected, some setting(s) on the devices didn't recognize the network as the same (don't go down that rabbit hole) and as a result, they're not seeing the Chromecast devices on the same network. To resolve, go into the devices' settings and completely forget the network and re-add it as new. If it still fails, compare the wife's settings to yours and see if there is a difference, fix, and move to a deep dive on the Sonos settings.
2. Devices are connecting differently on Ethernet backhaul vs. Wifi - The 5GHz and 6GHz bands are likely the strongest connection available when you have Ethernet connected and 2.4Ghz when they are connecting to the points in mesh via Wifi connection when you remove the Ethernet backhaul. Since the Chromecast can only use 2.4GHz (and maybe the Sonos) they will always use 2.4GHz. For some reason, even though the Chromecasts are on the same network, the Sonos and wife's phone are not recognizing 2.4GHz devices; disconnecting the Ethernet backhaul forces everything to connect 2.4GHz due to the aforementioned latency issues and the Sonos and phone see the Chromecasts. To resolve, try #1. You can also try removing the Chromecasts from the network and reconnecting again.
3. The points were set up on Wifi and then connected to Ethernet - This can cause issues with devices connecting in some cases. To resolve, you'll need to reset the points, connect Ethernet, power cycle them, and then set them back up with Ethernet connected from the start.

Let me know how it goes and if anything new occurs.

[AbigailF]

Hey folks, 

@PatrickP_Viking, appreciate your helpful response. 
@collinsc, chiming in to ensure everything is good here. Have you had the chance to try the suggestion above? If yes, how is it?

Best,
Abi

[collinsc]

Thanks Patrick! I'm going to try #1 - Was thinking down this line or a more nuclear option of starting from scatch with a new name and everything.

I did want to ask about #3 - You are correct, the points were set up on WiFi and then connected to ethernet, but because when I was going through the setup and did it the reverse (connected the point to the ethernet connection and then started setup) it was having issues during the setup and flagged that as the probably cause.

For reference, the connection comes into a Verizon router located in the absolute worst location possible in the basement of the house, where the Verizon gateway is then set up. The Verizon gateway then connects to all of the ethernet drops throughout the house. The Nest WiFi Pro & Points are in much more beneficial locations in the house, with the main router on the main floor and points in less confined spaces to allow for the best signal.

My latest theory was that the WiFi Points, when connected by ethernet are then going straight to the gateway, not to the router first, are not realizing they should be working together with the WiFi Pro router. So even though they recognize as points, it gets wonky.

Unfortunately I haven't figured out a way to get around the fact that all of the drops are tucked away back in the utility room, and the Verizon gateway itself - which has both coax & ethernet service connections, so I potentially could see about grabbing another point and sticking it in front of the verizon gateway, and hope the connection from the ONT is ethernet and that the coax is just for the Fios TV stuff?

Appreciate the help!

[PatrickP_Viking]

Hey @collinsc .

In regards to #3, the first Nest Wifi Pro should be connected to the Verizon modem and the others connect from the now router to the rest of the points, whether through Ethernet or Wifi. By connecting each of them to the Verizon modem, they would all try to set up a new network and each act as a router themselves; essentially, you would have three different networks. That setup would also explain the connection issues the Sonos and wife's phone were having with not seeing the Chromecasts since they are connecting to different networks. When you disconnected the Ethernet from the points, they set up the mesh via wireless connections.

The best option, although maybe a little difficult with how the Ethernet is run, would be to connect the first Nest Wifi Pro to the modem and then a switch from that Nest Wifi (now the main/router). The Ethernet connections to the other two points could then be connected to the switch and you would just set them up as an Ethernet mesh point. It sounds like #3 is the way to go with the added details you provided like I described. I have mine set up similarly.

As far as the coaxial and Ethernet connections feeding into the modem, I'd have to see the connections they make to it. Fios should be fiber optic but coaxial will support speeds up to 1Gbps; I don't know of any provider that runs Ethernet into a home though.

[collinsc]

Thanks Patrick. If you'd like to see, here's the legit mess 🙂 I take only blame for not cleaning it up, as it was this spaghetti when we moved in but I haven't done much to fix it up.

https://photos.app.goo.gl/i3SFht8zf8cCvNyW9

It is FiOS / Ftth - but then to the GS3100 it's converted over to ethernet (pictures 4 and 5, where you see the blue service line going through the adapter to the cat6e cable into the wan port).

I'm going to go ahead and grab another point to try out putting the WiFi pro in front of the GS3100 and a larger switch to accommodate all of the drops and will report back in roughly a week when i've got it all set up.

Appreciate the help!

[AbigailF]

Hi collinsc,

We appreciate your update. Let us know once you've done the troubleshooting steps and if it helps with your issue. Feel free to let us know if you have any other questions or concerns for now.

Regards,

Abi

[PatrickP_Viking]

Hey @collinsc . Thanks for the pictures.

Here's the setup I'd recommend. This is similar to the one I use.

1. Put modem in bridge mode and make sure wifi is turned off. Disconnect any other devices connected to LAN ports on the modem
2. Connect the first Nest Wifi Pro to the first LAN port on the modem via Ethernet cable and configure; this will serve as the router now
3. Connect an Ethernet cable from the other Ethernet port on the Nest Wifi Pro to the input/Port #1 on the switch
4. Connect an Ethernet cable from the switch to the first point and configure as an Ethernet connected point
5. Connect an Ethernet cable from the switch to the second point and configure like above
6. Test connectivity to the network. If there are issues, unplug the modem and all points and reconnect power starting with the modem, then first Nest Wifi Pro, switch, first point, and lastly the second point.

From the pictures, it appears that you have a system similar to what was installed in my house by a previous owner. What I found out was that the system's native switches would not handle the network traffic well, if at all, and were a big point of failure. I disconnected the Ethernet cables from the system switch, mounted an unmanaged switch to the back of the box on the inside, and connected the existing Ethernet cables that were run throughout the house to the newly installed switch. Since bypassing the system's switch, I have not had any issues. 

Of note also, the coaxial splitter in the system may be another point of failure in the future if it isn't already. I made coaxial connections using external splitters to feed signals to cable boxes before I cut the cord years ago which eliminated those issues.

The whole house systems are great to have but unfortunately don't stay up to date with hardware over time; there are some that you can't even find new modules for now. And the mess you have is worse than I had with mine but is fixable. I used a cable tester and verified the labels and proper cabling as I was cleaning the box up which revealed some that were labelled wrong and some punch downs that had to be fixed. Just a thought as you try to straighten things up.

Good luck! Let me know how it goes!

[Jhonleanmel]

Hey folks, 

PatrickP_Viking, appreciate your helpful response. 
collinsc, chiming in to ensure everything is good here. Have you had the chance to try the suggestion above? If yes, how is it?

Best,
Mel

[AbigailF]

Hi collinsc,

We’d like to check in again in case you have any further questions or concerns. Feel free to reply to this thread and we’ll help you out.

Regards, 
Abi

[AbigailF]

Hey collinsc,

I'm just checking in to make sure that you've seen our response. Please let us know if you have any other questions or concerns as I will be locking this in 24 hours.

Cheers, 
Abi

[collinsc]

Thanks for checking in! I am planning to do the switch over on Friday. If it's easier, I can start a new topic if that doesn't work, or otherwise will provide an update then.

[AbigailF]

Hello collinsc,

We can leave this thread open for a few days to give you time to update us. Let us know if you have any other questions or clarifications for now and we'll be happy to help out.

Thanks,
Abi

[collinsc]

@PatrickP_Viking - I really appreciate the help. I ran into a slight issue tonight that I'm looking for a workaround on.

It appears the Verizon G3100 does not have a bridge mode capability built in at all. I'm hoping the following will work, but wanted to run it by here:

1) before making any changes, go to the G3100 settings and disable IPv4 and IPv6 address distribution. (WiFi is already disabled)

2) Proceed as above, OR

3) Connect the Ethernet cable currently going from the ONT into the Verizon WAN port instead to the first WiFI Pro Router, and then connect another cable from the output port to the switch. Connect the G3100 to the switch as well as all of the drops from the home.

Again - Thank you!

[PatrickP_Viking]

Hey @collinsc .

I did a little digging around the Interweb and discovered that Verizon has a habit of "forcing" customers to use their own equipment  but the techie folks always find a way. I apologize for not catching this sooner.

Below are two articles that should get you up and running and eliminate the Verizon router altogether; you should be able to return it to Verizon and get the rental removed from your account. The first article should work if you have internet only with them. Article two covers the same as article one but takes it a step or so further if you have TV service also. If it is the latter, you will have to purchase a MoCA adapter but they are easy to find and range in price from $20+.

Use Own Router with FiOS ONT Ethernet 

How to Use Your Own Router With Verizon FiOS 

Let me know how it goes.

[AbigailF]

Hello folks,

Thanks for lending a hand, @PatrickP_Viking.
@collinsc, were you able to see PatrickP_Viking's response? Let us know if you have any follow-up questions and we'll be happy to help you out.

Best,
Abi

[collinsc]

@PatrickP_Viking, thank you for the help! Unfortunately I seem to be at an impasse for now - I'm probably going to have to try again with Verizon on the phone. I proceeded as above, but encountered a strange issue - the Nest WiFi Pro router would only setup in bridge mode. Upon completing the setup, I encountered the issue of "could not join your new network", and then in the settings, could not switch the WiFi Pro Router from Bridge Mode to NAT (Standard).

Steps I followed:

1. Factory reset the Nest WiFi Pro Access points and then the Router
2. Disconnected the WiFi Pro Access Points and Router
3. Disabled ipv4/ipv6 on the verizon G3100 (there is no dhcp release functionality in the UI that I can see)
4. Unplugged the G3100 from the network
5. Moved the WiFi Pro router down to the utility closet and replaced the G3100 with it
6. Proceeded with setup for the WiFi Pro
7. Unable to join after setup complete; upon looking in the Home app, see that the WiFi Pro is grabbing an unexpected IP address similar to the WAN IP (96.231.X.X) and shows itself in bridge mode, even though there are no other routers or access points on the network or plugged in
8. Waited two hours; tried again
9. No change ; rolled back everything to the previous setup and configured the network as it previously was

I'm guessing I need to be in contact with Verizon for them to recognize the change / do the dhcp release / provide some sort of blessing. I'm not sure when my next opportunity will be (i.e. a good window when nobody will yell at me for the WiFi not being available in the house!). If you have any thoughts on how this went wrong, I'd appreciate it, and then @AbigailF you can close the topic.

Thanks again for all of your help!

Sean

[AbigailF]

Hi everyone,

I wanted to follow up and see if you are still in need of any help. Please let me know if you are still having any concerns or questions from here, as I would be happy to take a closer look and assist you further.

Thanks,
Abi

[AbigailF]

Hey collinsc,

Checking back in should you still have some questions here. Let us know by replying to this thread. 

Regards, 
Abi

[AbigailF]

Hello collinsc,

We haven't heard from you in a while so we'll be locking this thread if there is no update within 24 hours. If you have any new issues, updates or just a discussion topic, feel free to start a new thread in the Community.

Best, 
Abi