setup keeps failing on the 'connecting to internet' step, my modem works fine

Diagnosis

The failure at the "connecting to internet" stage on the Linksys Velop AX4200 is almost always a DHCP handshake failure. This occurs when the modem's internal ARP (Address Resolution Protocol) table is still locked to the MAC address of your previous router or a laptop used for testing. Because the AX4200 expects a dynamic IP assignment immediately upon boot, any delay or refusal from the modem to release the old lease causes the Velop to time out and report a connection failure. Furthermore, this often happens if you are using a "Gateway" (a combined modem/router) provided by your ISP. In these cases, the Gateway is trying to act as the DHCP server while the Velop is also attempting to initiate a routing sequence. This creates a "Double NAT" conflict where the Velop cannot verify an external WAN IP, leading the setup app to believe the internet is offline even though the modem is functioning perfectly.

How to Fix It

To resolve the handshake timeout, you must perform a strict sequential power cycle to clear the modem's MAC cache and force a new IP assignment to the AX4200.

1. Disconnect the Ethernet cable from the back of the Velop node and the modem.
2. Power down both devices by pulling the AC power cords from the wall outlets.
3. Wait a full 120 seconds. This ensures the capacitors in the modem are fully discharged and the ISP's head-end registers the line as disconnected.
4. Plug only the modem back into power. Observe the LED indicators; do not proceed until the "Online" or "Internet" light is solid green or white. This usually takes 3 to 5 minutes.
5. Connect the Ethernet cable from the modem's LAN port to the Velop's internet port (the port typically marked with a globe icon).
6. Plug the Velop node into power. Wait for the LED on top to transition from blinking purple to a solid purple or blinking blue.
7. Open the Linksys app and restart the setup process from the beginning. When prompted, ensure you select "Automatic Configuration" for the DHCP settings.

If That Didn't Work

• Enable Bridge Mode on the Gateway: If you have a modem/router combo, log into the gateway's admin panel (usually 192.168.0.1 or 192.168.1.1) and toggle "Bridge Mode" to ON. This disables the gateway's routing functions and passes the public IP directly to the Velop AX4200, eliminating the Double NAT conflict.
• MAC Address Cloning: Some ISPs (especially Cable providers like Xfinity or Spectrum) lock the connection to the first MAC address they see. If you have an old router that worked, log into that router, find the "MAC Clone" section, and copy the MAC address. In the Velop advanced settings (via the web browser interface at 192.168.1.1), manually enter that MAC address into the internet settings.
• Swap the Ethernet Cable: The AX4200 is sensitive to cable integrity for the initial handshake. Replace the current cable with a known-working Cat6 or Cat5e cable. A pin-out failure or a bent connector in a cheap cable can allow "link lights" to appear but prevent the actual data exchange required for the DHCP request.
• Hard Factory Reset: If the node was previously attempted to be set up, it may have a corrupted config file. Press and hold the Reset button on the bottom of the node for a full 10-15 seconds until the light turns red, then release. Wait for it to reboot to blinking purple before trying the app again.

Heads Up

• Avoid plugging the Velop into a network switch before the modem; the AX4200 must be the primary device directly connected to the modem to establish the WAN connection.
• Ensure your smartphone is connected to the Velop's temporary setup SSID and not your cellular data during the process, as this can confuse the app's connectivity check.
• If you are using PPPoE (common with DSL), you must manually enter your username and password provided by your ISP in the "Internet Settings" section of the app; "Automatic" will always fail in this scenario.
• Keep the main node within 10 feet of the modem during the initial setup to minimize interference and signal drops during the firmware update that usually follows a successful connection.