Greetings,
This was as I suspected. The xFinity gateway is performing NAT and acting as a DHCP server. It's handing out addresses 10.0.x.x.
The Google Nest system is also performing NAT and DHCP and is handing out IP's on 192.168.1.x.
These two LAN segments cannot communicate, and anything connected to the nest system is being subjected to double NAT thought the Nest firewall and the xFinity firewall.
Here's what you need to do. Connect directly to the xFinity gateway. Log into its admin portal. Put this gateway into Bridge or Pass-through mode. Disable its wireless broadcasts.
Leave the Nest system as is. Let it perform NAT and DHCP. You can manage it through the Google Home App.
After this is done, the Xfinity gateway will simply be acting as a modem. It will not be performing NAT or attempting to manage IP addresses.
All of this will be done by the Nest mesh. Once your computer and printer are connected to the Nest they will be able to communicate.
Optional, if you want to take things a step further, assign the printer a static IP on the Google Nest system.
Now you're ready to install drivers. If you have any failed installation attempts, or multiple instances of the printer that don't work, I'd remove them and restart your system.
The drivers you should install are the Imageclass MFDrivers UFRII/Fax/ScanGear package v4.803 (dated 11/26/21) and the MFScan Utility v1.21.0.2, dated 10/18/23.
Let us know how things go 🙂
~Rick
Bay Area - CA
~R5 C (1.0.6.1) ~RF Trinity, ~RF 100 Macro, ~RF 100~400, ~RF 100~500, +RF 1.4x TC, +Canon Control Ring, BG-R10, 430EX III-RT ~DxO PhotoLab Elite ~DaVinci Resolve ~Windows11 Pro ~ImageClass MF644Cdw/MF656Cdw ~Pixel 8
~CarePaks Are Worth It
