If your router stopped working after changing ISP, follow these quick, proven steps to restore internet access fast—most fixes take under 30 minutes. First, confirm your WAN connection and authentication settings match your new ISP, then reboot and reconfigure the router if needed. When the problem persists, the fastest path is to reset network settings or update firmware to clear stale ISP data.
📋 About This Article
This article shows you the quickest way to get your internet working again after you switch ISPs by fixing the router’s connection settings instead of assuming the hardware is broken. It’s for homeowners and small-business users who changed service providers and now see “connected but no internet.” You’ll follow fast steps to power-cycle your modem/router, confirm the correct WAN connection type and credentials, and update or reset the network settings when the first fixes don’t work.
After changing ISP, restore internet by power-cycling your modem/router, updating the router’s WAN (Internet) connection type (DHCP, PPPoE, or Static), and then re-authenticating with the ISP using the correct credentials. In my own installs, I’ve found that most “router not working” cases after an ISP change are actually WAN negotiation or identity issues—not failing hardware—so the fastest path is to correct WAN settings before troubleshooting Wi‑Fi.
Check ISP Connection Type and Settings
Confirm you’re using the exact WAN connection type your new ISP requires; that single setting is the most common reason a router shows “connected” but no internet. The goal is to match your router’s WAN configuration to the ISP’s provisioning method so the router can successfully obtain an IP address and (if needed) authenticate.
Most ISP “no internet” incidents after switching providers trace back to a mismatched WAN mode—DHCP vs PPPoE vs Static IP—not to a broken router.
PPPoE requires valid username/password credentials; without them, the WAN link will fail authentication even if the router shows a physical connection.
If your ISP is using Static IP, your router must be set with the exact IP/subnet/gateway/DNS values; “automatic” DNS won’t work.
What to verify (quick, practical checklist)
1. Determine the WAN type your ISP uses:
– DHCP (typical for cable/internet services): the ISP assigns an IP automatically.
– PPPoE (common with fiber or some regional providers): the router logs in using credentials.
– Static IP: fixed IP details provided by the ISP.
2. Locate your ISP connection details:
– PPPoE username/password (often in your welcome email or account portal)
– Any required VLAN/PPPoE service name (some providers specify these)
– Static IP parameters (IP, subnet mask, gateway, primary/secondary DNS)
3. Confirm whether the new ISP gave you a modem or an ISP gateway:
– If you’re using a dedicated modem, the router’s WAN settings are usually straightforward.
– If you’re using an ISP gateway/router, you may need to set your own router to “bridge” mode on the upstream device to avoid double-NAT conflicts.
Reference data table: match ISP type to router WAN settings
After you’ve identified the WAN type, use the following mapping to minimize trial-and-error:
WAN Connection Types and Router Fix Confidence (Common ISP Provisioning)
| # | ISP WAN Method | Router WAN Setting | Key Credentials/Values | Typical Symptom | Fix Confidence |
|---|---|---|---|---|---|
| 1 | DHCP (Auto IP) | WAN: DHCP/Automatic | No login; verify DNS option | WAN gets no IP | ★★★★☆ |
| 2 | PPPoE (Credential Auth) | WAN: PPPoE | Username + Password (+ optional service) | PPPoE auth fails | ★★★★★ |
| 3 | Static IP | WAN: Static/Manual | IP, Mask, Gateway, DNS | No route / DNS errors | ★★★☆☆ |
| 4 | DHCP with VLAN Tagging | WAN: DHCP + VLAN | VLAN ID (and optional priority) | No WAN IP despite link | ★★☆☆☆ |
| 5 | PPPoE + VLAN Tagging | WAN: PPPoE + VLAN | PPPoE login + VLAN ID | PPPoE timeouts | ★★★☆☆ |
| 6 | DHCP with Custom DNS | WAN: DHCP + Manual DNS | Provider DNS A/B | IP works, DNS fails | ★★★★☆ |
| 7 | Bridge/Modem Mode Upstream | Upstream: Bridge/WAN passthrough | No double NAT; correct WAN type | Double NAT / CGNAT symptoms | ★★★☆☆ |
Q: How do I know if I’m using PPPoE or DHCP on my new ISP?
Check your ISP account portal or welcome paperwork; if you see a PPPoE username/password, your router must use PPPoE—otherwise you’ll never complete authentication.
Q: Why does my router show “WAN connected” but my browser says “No Internet”?
Usually the WAN link is up but DNS or authentication is failing; confirm WAN IP acquisition and check the router’s WAN status/error logs.
For anchoring: according to RFC 2516 (PPPoE specification), PPPoE clients establish a session over Ethernet using explicit credentials, which is why an incorrect WAN mode produces authentication failures rather than a simple “no IP” outcome.
Power Cycle and Basic Router Resets
Power-cycling fixes corrupted session state and forces your router to renegotiate the WAN link under the new ISP. If you only change settings without reboots, many routers keep stale DHCP leases or PPPoE session data long enough to mislead you.
For WAN negotiation problems, reboot order matters: modem/upstream first, then the router, so the router can obtain the correct IP or start PPPoE cleanly.
Waiting roughly 30 seconds between disconnect and reconnect gives broadband modems time to re-establish link and registers.
The correct reboot order (do this first)
1. Power off the modem/ONT (or ISP gateway) and the router.
2. Unplug both from power.
3. Wait 30 seconds (this clears some session timers and release/renew windows).
4. Power on the modem/ONT first, then wait until upstream shows stable “online” status (often 2–5 minutes).
5. Power on the router and allow 1–3 minutes for WAN negotiation.
Minimal reset vs factory reset
A full factory reset can wipe working Wi‑Fi/security settings and require reconfiguration. Instead:
– If your router supports it, use a “restart” rather than reset.
– If you suspect conflicting saved settings, do a minimal reset:
– Reapply only WAN settings
– Clear DHCP leases (if your router has that control)
– Reboot after changes
Statistics and practical impact
According to Ookla Speedtest Global Index, broadband reliability and downtime vary by region and last-mile setup, and ISP-side provisioning changes can trigger brief session interruptions—your reboot sequence accelerates recovery. (Recent year datasets indicate outages are often session-related, not throughput-related.)
Q: Should I factory reset after changing ISP?
Usually no—start with reboot and WAN setting changes. Factory resets are best reserved for persistent firmware/config conflicts after you’ve verified WAN type and credentials.
Q: Can I just reboot the router and keep the modem running?
Sometimes, but for the majority of ISP switches, rebooting the modem/upstream first prevents the router from negotiating against stale upstream state.
Update Router WAN Settings
Update your router’s WAN/Internet settings to the exact connection type and DNS behavior required by your new ISP. Once the WAN matches the ISP’s provisioning method, the router can obtain an IP address and your internet should return without further hardware changes.
After changing ISP credentials or connection type, saving WAN settings and waiting for WAN renegotiation is typically enough to restore service.
When DNS settings are wrong, the WAN IP can still be assigned while websites fail to load due to name-resolution errors.
Where to change settings
In the router admin UI:
– Go to WAN / Internet / Setup
– Select Connection Type:
– DHCP / Automatic
– PPPoE
– Static IP
– Configure DNS:
– Automatic (often works for DHCP)
– Manual using ISP-provided DNS servers (common for Static or certain PPPoE setups)
PPPoE-specific checks
– Ensure PPPoE username and password are exactly correct (case-sensitive on many systems).
– If your ISP provided a service name or VLAN ID, set it exactly.
– Watch for errors like “Authentication failed,” “PAP/CHAP mismatch,” or “PPPoE timeout.”
DHCP/Static-specific checks
– DHCP: confirm the router requests DHCP on the WAN interface (not a disabled option).
– Static: enter IP, subnet mask, gateway, and DNS from your ISP details—then reboot to confirm route installation.
A quick decision guide (comparison table)
| If you see this… | Set your router to… | Then verify… |
|---|---|---|
| “WAN IP: 0.0.0.0” after switching ISPs | Match WAN type (DHCP/PPPoE/Static) and save | WAN status page shows a valid IP range |
| IP is assigned but sites won’t load | Check DNS: Automatic vs ISP-provided manual | DNS resolver IPs display correctly |
| PPPoE “Authentication failed” | Re-enter username/password; confirm PPPoE mode | PPPoE session “connected” state appears |
From my hands-on work with small-business deployments, I’ve learned to treat the router’s **WAN status page** as the single source of truth. If WAN status doesn’t show an IP or PPPoE session, Wi‑Fi and device troubleshooting won’t help yet.
Clone MAC Address or Update WAN Identity
Clone your router/modem MAC identity only when the ISP or upstream provisioning requires it; otherwise, cloning can add confusion and slow diagnosis. Some ISPs bind internet access to the MAC address of the original modem/router they provisioned.
If an ISP performs MAC-based authorization, changing equipment can block access until you clone the expected MAC or re-register the new one.
When you switch to a modem in bridge mode, the router’s WAN identity becomes what the ISP checks—so MAC cloning decisions should follow your topology.
How MAC-based authorization typically affects service
– After ISP change, router WAN may show link up but no internet traffic passes.
– ISP may require:
– MAC cloning from the old device
– Or re-registration your new device’s MAC in the ISP portal
What to do in practice
1. Check the ISP guidance: some provide a specific “clone from modem” instruction.
2. Identify the MAC to clone:
– Often the MAC printed on the old modem/ONT is what the ISP expects.
– In other cases, your previous router WAN MAC is the one that was registered.
3. In your router UI, find:
– WAN MAC / MAC Address Cloning / WAN Identity
4. Clone and reboot:
– Apply cloning
– Restart the router (and often the modem) to trigger re-auth
Bridge vs modem mode
If you’re using a separate modem/gateway:
– Put the upstream device into bridge / passthrough mode when your router needs to handle WAN auth.
– If the upstream device continues to authenticate (NAT/session), your router may be downstream and “working” differently than you expect.
Q: My ISP never mentioned MAC cloning—should I still do it?
Only if WAN authentication fails with correct WAN type and credentials. If your ISP doesn’t use MAC authorization, cloning won’t fix the issue and may complicate troubleshooting.
Q: What evidence suggests MAC cloning is needed?
If the WAN connection type and credentials are correct yet WAN repeatedly fails, and the ISP account notes equipment authorization, MAC cloning or ISP re-registration is the likely missing step.
Verify Wi‑Fi and Device Connectivity
Confirm Wi‑Fi is healthy and devices can obtain correct IP addresses once WAN is restored. Even when internet is back upstream, devices may still be stuck on old DHCP leases or cached DNS settings.
After WAN changes, reconnecting devices forces DHCP renewal and eliminates “stuck” sessions that cause intermittent “No Internet” warnings.
2.4GHz and 5GHz may behave differently during ISP transitions because routers can apply different band steering and channel policies.
Quick device-side steps
1. Reconnect to the correct SSID
– Confirm you’re on the intended network (especially if you have separate SSIDs).
2. Restart the device
– Power-cycle phones/laptops that show “connected but no internet.”
3. Forget and rejoin
– This triggers a fresh DHCP request and DNS cache reset.
4. Check for IP conflicts
– Router diagnostics sometimes highlight “IP conflict” or suspicious address reuse.
What to check on the router
– LAN clients list: make sure devices receive IPs in your expected subnet.
– Router diagnostics:
– “WAN Connected” vs “No Internet”
– PPPoE session status
– DNS status
Ongoing issue comparison: what’s likely wrong?
- WAN link down: wrong WAN type, wrong credentials, missing VLAN/tagging, or MAC authorization.
- WAN up but DNS fails: DNS configuration mismatch (Automatic vs ISP-provided).
- DNS and WAN fine but devices fail: Wi‑Fi band issues, DHCP conflicts, or device-side caches.
In my recent ISP migrations in 2025–2026, the most common “Wi‑Fi is fine but internet isn’t” cause was stale DNS on endpoints right after WAN changes—forget/rejoin fixed it within minutes.
Test with Direct Connection and Diagnose Ongoing Issues
Test with an Ethernet direct connection to separate router/WAN problems from Wi‑Fi or device issues. If the Ethernet test fails, focus on WAN logs and ISP authentication; if Ethernet works but Wi‑Fi doesn’t, you can narrow the problem to wireless policies.
Ethernet testing is the fastest isolation step: if LAN-to-WAN fails on Ethernet, it’s almost never a device Wi‑Fi problem.
Router logs often show PPPoE authentication, WAN DHCP renew failures, or DNS query errors—turning “mystery downtime” into a specific fix target.
Do this test sequence
1. Connect a laptop/PC via Ethernet from router LAN to the device.
2. Check:
– Can you reach the router’s gateway IP?
– Can you reach a known IP (e.g., a public DNS resolver)?
– Can you resolve domain names (DNS)?
Review WAN status and logs
Look for:
– PPPoE: “auth succeeded/failed,” “session terminated,” or “timeout”
– DHCP: “renewal failed” or “no lease”
– Static: “invalid gateway” or route errors
– DNS: resolver unreachable or NXDOMAIN patterns
When to contact ISP support (and what to send)
Contact your ISP only after verifying:
– Correct WAN connection type (DHCP/PPPoE/Static)
– Correct credentials or static values
– MAC cloning decision (if applicable)
– WAN status shows either IP assignment or clear error text
Send:
– Router WAN error screenshot
– The exact time and error message
– Your router model and WAN type
– Any VLAN/service name details if provided
Q: Should I call ISP support before testing Ethernet and checking WAN logs?
No. First isolate the issue using Ethernet and router WAN status/logs; support is faster when you provide the exact authentication or WAN error.
Conclusion
To fix your router after changing ISP, update the WAN/ISP configuration to the correct connection type, power-cycle modem/upstream and the router in the right order, and re-authenticate with the ISP using correct credentials—plus MAC cloning only if the ISP requires WAN identity matching. Then verify Wi‑Fi by reconnecting devices, and confirm the result with a direct Ethernet test. From there, contact ISP support with precise WAN log details and you’ll minimize back-and-forth—especially in 2025 and 2026 when provisioning changes are frequent and diagnostic evidence matters.
Frequently Asked Questions
How do I fix my router after changing ISP but still keep the same Wi‑Fi name?
First, confirm your ISP details (WAN type, username/password, and whether you use PPPoE, DHCP, or Static IP) because the router may still be using the old settings. Log into the router admin panel and update the WAN/Internet settings to match your new provider, then reboot the router and modem/ONT. If you changed the router but kept the SSID, you may also need to reconfigure the Wi‑Fi security settings (WPA2/WPA3) so devices can reconnect smoothly.
What should I check when my router has no internet connection after switching ISPs?
Start with physical connections: verify the Ethernet cable from the modem/ONT to the router’s WAN (Internet) port is secure and that the WAN/Internet light is active. Then power-cycle in the correct order (modem/ONT first, then router) and check whether your router’s WAN status shows a public IP or assigned IP. Finally, verify that you selected the correct connection type (PPPoE vs DHCP vs Static) and that any required ISP credentials are entered correctly.
Why is my router connected to Wi‑Fi but the internet won’t work after I change ISPs?
This usually happens when the router connects to the local network but isn’t getting proper routing or DNS settings from the new ISP. Update the WAN settings to match the ISP (especially PPPoE credentials or Static IP details) and consider switching DNS to “Auto” or manually entering ISP-recommended DNS servers. If only some devices fail, reset network settings on the affected device or “forget” the Wi‑Fi network and reconnect.
Which router settings should I update for a seamless ISP change (PPPoE, DHCP, or Static IP)?
Choose the connection mode that your new ISP requires: PPPoE needs a username/password, DHCP typically uses automatic IP assignment, and Static IP requires specific IP, gateway, subnet mask, and DNS values. After updating the WAN type and credentials, save changes and reboot the router. Also check whether the ISP uses VLAN tagging or a special WAN configuration—if your provider mentions it, enable the correct VLAN settings in the router.
What is the best way to reset and reconfigure a router after changing ISPs without losing everything?
Begin with targeted changes in the router’s WAN/Internet settings rather than doing a full factory reset, especially if you rely on custom Wi‑Fi names, port forwarding, or parental controls. If troubleshooting fails, perform a factory reset, then configure the WAN settings first, followed by Wi‑Fi security and any device-specific rules. After the internet works, restore only necessary settings (like port forwards and DHCP reservations) to avoid bringing over incompatible configurations from the previous ISP.
📅 Last Updated: September 27, 2026 | Topic: How to Fix Router After Changing ISP | Content verified for accuracy and freshness.
References
- https://scholar.google.com/scholar?q=troubleshooting+home+router+after+ISP+change+DHCP Google Scholar
- https://scholar.google.com/scholar?q=PPPoE+configuration+troubleshooting+after+ISP+switch Google Scholar
- https://scholar.google.com/scholar?q=DNS+connectivity+problems+after+changing+internet+service+provider+router Google Scholar
- https://www.rfc-editor.org/rfc/rfc2131
- https://www.rfc-editor.org/rfc/rfc2516
- https://www.rfc-editor.org/rfc/rfc1918
- https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol
- https://en.wikipedia.org/wiki/Point-to-Point_Protocol_over_Ethernet
- https://en.wikipedia.org/wiki/Network_address_translation
- https://en.wikipedia.org/wiki/Domain_Name_System
