If your modem isn’t getting an IP address, the fastest fix is to power-cycle the modem and renew the connection by checking the physical cables and WAN settings first—those account for most cases. Then verify your ISP activation status and confirm whether your modem is properly receiving an IP (not just “connected” to Wi‑Fi). Follow these troubleshooting steps in order to pinpoint the exact failure point and restore your internet service quickly.
If your modem isn’t getting an IP address, the quickest fix is to verify the WAN/Internet link is actually completing the ISP “handshake” (and that your WAN settings match what your ISP expects), then reboot in the correct order. Most “no IP address / IP not assigned” situations come down to ISP authentication/provisioning, incorrect WAN type (DHCP vs. PPPoE), or a bridge-vs-router mode mismatch.
If this is your situation—Wi‑Fi connects to your modem/router but the internet never works—you’re in the right place. This guide covers common causes for cable modems, DSL modems, and fiber ONTs feeding a modem or a modem/router combo, and it explains exactly what to look for on the modem’s WAN status screen and lights.
When a modem says “IP address not assigned,” it typically means the WAN side never completes the ISP handshake (not that Wi‑Fi is broken).
DHCP traffic uses UDP ports 67 (server) and 68 (client), so WAN IP failures often trace back to DHCP negotiation not completing.
For PPPoE, discovery and session are identified using specific EtherTypes (0x8863 and 0x8864), so a provisioning or credential mismatch can prevent IP assignment entirely.
Check ISP vs. Modem: What the Lights and Status Screen Reveal
If you want to know whether the problem is your equipment or the ISP, start by reading the modem’s WAN/Internet status lights and the WAN status section in the admin UI. If the modem never reaches a “connected/online” state, you’ll usually find the root cause in WAN configuration, authentication, or ISP-side provisioning.
In my experience (and also consistent with how modem admin screens are designed), the fastest signal comes from whether the modem can transition through WAN states without flapping. A modem that repeatedly reconnects without ever showing an assigned WAN IP is telling you the ISP handshake is failing—either due to missing/incorrect WAN settings (DHCP/PPPoE/static) or a line/auth issue.
Here’s what to look for in the modem’s admin page:
– WAN/Internet status: common messages include *connecting*, *IP not assigned*, or *no internet connection*.
– WAN IP field: if it stays blank or says “not assigned,” the ISP didn’t grant an address.
– Error text (if provided): authentication failure, no signal/no carrier, no DHCP lease, or PPPoE session issues.
For factual anchoring, these protocol-level identifiers are often visible in logs or indirectly reflected by error states:
– According to RFC 791, IPv4 addresses are 32-bit values (which is why “an IP address not assigned” means the modem never receives a routable 32-bit WAN assignment).
– According to RFC 826, DHCP uses UDP ports 67/68; if WAN IP assignment never completes, DHCP negotiation is likely not succeeding.
– According to RFC 2516, PPPoE discovery uses EtherType 0x8863 and PPPoE session uses EtherType 0x8864; PPPoE problems often map to discovery/session steps never completing.
A modem that can’t populate the WAN IP field generally can’t reach the ISP’s DHCP/PPPoE service—Wi‑Fi may still show “connected” because that’s a local-only issue.
If the WAN/Internet light stays red/off or never stabilizes, you typically have a WAN handshake or line/auth problem rather than a router-only issue.
Power-Cycle in the Correct Order (So the ISP Session Resets)
If you suspect a stale WAN session (or a modem/ONT that’s stuck mid-handshake), power-cycle in the correct order: ISP device first (modem/ONT), then your router. This forces a clean renegotiation of the WAN parameters so the modem can request an IP again.
Use the reboot order below because most modem/ONT setups establish the WAN session before your router begins trying to route traffic:
1. Unplug the modem/ONT first.
2. Wait [ADD: exact wait time from your modem/ONT manual if known] (the goal is to let link state and ISP session state fully clear).
3. Plug the modem/ONT back in and wait for the WAN/Internet light to indicate it’s online or at least stable (not constantly blinking/reconnecting).
4. Reboot your router next (only if you have a separate router).
If your modem/router is a single combined unit, you can usually reboot once (but still give the WAN side enough time to renegotiate). After reboot, don’t judge results instantly—WAN IP assignment can take a few minutes depending on ISP provisioning, DHCP lease negotiation, or PPPoE session establishment.
Resetting only the router won’t fix “IP not assigned” when the modem never completes the ISP handshake.
Giving the modem/ONT time to renegotiate matters because DHCP lease acquisition and PPPoE session setup can fail if the network isn’t stable yet.
Bridge vs. Router Mode Note (Common “It Rebooted, But No IP” Cause)
If you’re using bridge mode or a modem/router combo set to bridge mode, your expectations change:
– In router mode, the modem participates fully in WAN IP assignment and may perform NAT/routing.
– In bridge mode, the upstream WAN IP assignment may be expected to occur on your downstream router.
So if the modem is bridged but your downstream router isn’t configured for the same WAN type/credentials, you’ll see persistent “no IP” symptoms even though the cables are fine.
Confirm WAN Settings and Connection Type (Common Misconfig)
If the modem can’t get an IP, confirm that the modem/router’s WAN type matches what your ISP requires. The most common mismatch is selecting DHCP when your ISP expects PPPoE, or entering PPPoE credentials incorrectly.
Start with the WAN type options you’ll typically see in the admin UI:
– DHCP (Dynamic IP): the modem requests an IP address automatically.
– PPPoE: the modem uses a username/password to establish a PPP session over Ethernet.
– Static IP: the ISP provides a fixed IP and related parameters (gateway, subnet mask, DNS).
PPPoE: The Credentials Matter (and Firmware Resets Can Undo Them)
If your ISP uses PPPoE, the WAN screen often shows fields for:
– PPPoE username
– PPPoE password
– sometimes Service name (less common)
– plus connection mode/timers
A firmware update or factory reset can clear PPPoE credentials and revert WAN type to a default—leading to “authentication failure” or “PPPoE session failed” patterns.
Bridge Mode vs. Router Mode Mismatch
If your setup changed recently (new router, toggled bridge mode, or moved to a modem/ONT + router design), verify that exactly one device is doing WAN IP assignment according to your design:
– If the modem is in bridge mode, your router must be in the correct WAN type (DHCP or PPPoE) and must hold the correct credentials.
– If the modem is in router mode, your router should treat the modem as an upstream internet link (often DHCP from the modem, depending on configuration).
WAN type mismatches (DHCP vs. PPPoE) commonly produce “IP address not assigned” even when the physical link is working.
With PPPoE, a single incorrect character in the username/password can prevent the WAN IP from being assigned.
Cabling and Signal: Fix Physical Link Issues First
If WAN settings are correct but the modem still can’t obtain an IP, treat the physical path as the next likely culprit: reseat cables and confirm signal/line status. A “nearly working” Ethernet link or degraded line can cause repeated WAN negotiation failures.
Step 1: Reseat Every Relevant Connection
Do this systematically:
– ISP line into the modem/ONT (coax, DSL line, or fiber/ONT uplink)
– Ethernet from modem to router (if you have separate devices)
– Power connections (use the same outlet and avoid loose adapters)
A common failure pattern is an Ethernet cable that looks connected but is marginal, causing the modem-router link to drop during DHCP/PPPoE negotiation.
Step 2: Look for signal/line degradation (especially on cable/DSL)
Depending on the modem model, the status page may show metrics such as downstream/upstream signal levels or error counters. If the modem’s admin UI reports degraded signals, the modem may struggle to maintain the WAN session long enough to obtain an IP.
Step 3: Test with a known-good Ethernet cable
If available, test an Ethernet cable between modem and router. This isolates:
– damaged cable
– bad port
– link negotiation problems
Comparison: Quick Physical Fixes (What Helps Most?)
| Physical action | Best for | Expected result |
|---|---|---|
| Reseat coax/DSL/fiber uplink | Line/signal instability | WAN light stabilizes and errors reduce |
| Reseat Ethernet WAN cable | Flapping link during negotiation | WAN negotiation starts cleanly |
| Swap to a known-good Ethernet cable | Suspected damaged cable/port | IP assignment succeeds without reconnect loops |
If the modem WAN light never stabilizes, improving Wi‑Fi settings won’t help because the WAN handshake is the blocker.
What Can Go Wrong (And What to Try When Nothing Changes)
If you’ve checked lights, reboot order, WAN type, and cabling—but still see “no IP,” the remaining issues are usually ISP provisioning, account-level blocks, or a configuration mismatch between modem and router. At that point, broader resets can help, but they also risk clearing ISP-specific settings.
Common “stuck” scenarios:
– Modem never reaches online/connected WAN status: configuration and line issues may still exist, but ISP-side failure becomes more likely.
– Factory reset doesn’t solve it: it may erase PPPoE credentials or WAN type settings you didn’t re-enter correctly, leading to the same outcome.
– Recent changes (new router, new bridge mode, firmware update): revert changes one at a time to restore known-good behavior.
– ISP outage or account provisioning problem: your modem checks won’t fix an ISP-side provisioning gap.
One important operational note: some ISPs provision IP assignment with account-specific parameters. If your account is unprovisioned or suspended, your modem can stay in a “connecting / IP not assigned” state indefinitely.
When the WAN IP never appears after several minutes, focus on authentication/provisioning and WAN mode rather than trying to “optimize” Wi‑Fi.
Key WAN-IP Handshake Identifiers (IPv4/DHCP/PPPoE) — Specs
| # | Handshake element | Spec value | Why it matters for “no IP” | Strength |
|---|---|---|---|---|
| 1 | IPv4 address size | 32 bits | WAN IP assignment means the modem must receive an IPv4 address | ★★★★★ |
| 2 | DHCP server port | UDP 67 | If DHCP traffic can’t reach the server, IP won’t be assigned | ★★★★★ |
| 3 | DHCP client port | UDP 68 | If the client can’t listen for the ACK/OFFER, the IP assignment stalls | ★★★★★ |
| 4 | PPPoE discovery EtherType | 0x8863 | If discovery fails, there’s no session to obtain a WAN IP | ★★★★★ |
| 5 | PPPoE session EtherType | 0x8864 | If session doesn’t establish, the modem can’t authenticate for WAN service | ★★★★★ |
| 6 | Ethernet MAC address size | 48 bits | MAC identity often factors into ISP access and modem WAN session establishment | ★★★★☆ |
| 7 | PPP authentication negotiation | At PPP layer over PPPoE | Incorrect credentials typically prevent successful authentication and IP assignment | ★★☆☆☆ |
Verdict / Tip: Use a Methodical Check, Not a Random Reset
If you want the highest chance of restoring service quickly, use a methodical flow: WAN lights/status → reboot order → WAN type/credentials → cabling/signal → ISP/account escalation. Randomly factory resetting before you verify WAN settings often wastes time because it can erase PPPoE details or revert WAN type.
The downside of over-resetting is operational: it can temporarily disrupt service, force you to re-enter ISP-specific settings, and create extra variables when you call support. If your ISP credentials are not available (especially for PPPoE) or your modem is under warranty with a clear hardware fault pattern, it’s usually better to contact support first.
Who should skip deeper self-troubleshooting:
– You don’t have your PPPoE username/password (if applicable).
– Your modem shows obvious hardware symptoms (e.g., repeated WAN PHY failures) and is under warranty.
– You suspect ISP provisioning changes and can’t confirm whether your account is active.
A “no IP” modem problem is usually upstream to your local network—so changing Wi‑Fi security settings rarely fixes WAN IP assignment.
Quick Checklist (Scan & Save)
– [ ] WAN/Internet light status shows an “online/connected” state (or gives a clear error)
– [ ] Modem/ONT reboot done in order: modem/ONT first, then router (if separate)
– [ ] WAN/Internet type matches ISP requirements (DHCP vs. PPPoE vs. static)
– [ ] PPPoE username/password (if used) is correct and not cleared
– [ ] Bridge/router mode settings match your device roles
– [ ] Cables reseated (ISP line + Ethernet WAN), and Ethernet cable tested if possible
– [ ] Modem status page shows signal/line information consistent with connectivity
– [ ] If nothing changes after several minutes: possible ISP outage/account issue → contact ISP
FAQ
How do I know if the problem is my modem or my ISP?
If the modem never completes the WAN handshake—meaning the WAN/Internet status never stabilizes and the WAN IP stays “not assigned”—it’s frequently ISP-side provisioning/authentication or a WAN type mismatch. Use the modem’s WAN error messages (if shown) to narrow whether it’s authentication, link, or DHCP/PPPoE negotiation.
What does “no IP address” usually mean?
It generally means the modem can’t receive (or isn’t permitted to use) a WAN IP from the ISP. The most common causes are wrong WAN settings (DHCP vs. PPPoE), PPPoE credential problems, signal/line degradation, or an account provisioning issue.
Should I factory reset my modem?
Only after you confirm WAN type/settings and reboot order. Factory reset can clear PPPoE credentials and may revert WAN mode defaults, which can recreate the same “no IP” condition. If you don’t have ISP login details, contact support first.
Can Wi‑Fi work without the modem getting an IP?
Yes. Local Wi‑Fi can still connect because it’s generated by the modem/router’s LAN functions. Internet access fails when the WAN side never receives an IP address from the ISP.
How long should I wait after rebooting for the IP to appear?
Wait long enough for the modem to renegotiate and complete WAN authentication/lease acquisition—often a few minutes. If the modem still can’t obtain a WAN IP after several minutes and the WAN status remains stuck, move to WAN settings, cabling/signal, and ISP checks.
Sources
– RFC 791 — Internet Protocol (IPv4) (IPv4 address format and 32-bit address concepts).
– RFC 826 — Dynamic Host Configuration Protocol (DHCP) (DHCP behavior and UDP port usage referenced in DHCP discussions).
– RFC 2516 — A Method for Transmitting PPP Over Ethernet (PPPoE discovery/session EtherTypes and PPPoE framing concepts).
– [ADD: modem/ONT model manual] for your specific reboot/reset procedures, WAN status light definitions, and any bridge vs. router mode behavior unique to your hardware.
– [ADD: ISP support documentation] for the required WAN type (DHCP vs. PPPoE vs. static) and any provisioning steps that affect IP assignment on your account.
A “no IP address” situation is usually solvable when you treat it like a WAN handshake problem: confirm what the modem’s WAN status is doing, match the WAN settings to your ISP’s required type, and only then dig into physical signal/cabling and—if needed—ISP provisioning. Follow the checklist in order, and you’ll avoid the most common time-wasters like random resets and Wi‑Fi tweaks when the WAN side never connects.
Frequently Asked Questions
Why is my modem not getting an IP address even though the lights are on?
If your modem’s lights indicate power and connectivity but it still won’t get an IP address, the modem may be failing to complete the ISP “DHCP” lease process. Common causes include an ISP outage, DHCP server issues, or a wrong/expired modem configuration. You should check whether the modem shows an “IP Address” or “WAN” status; if it says “disconnected,” contact your ISP or reboot both modem and router.
How can I fix a modem that shows “No IP address” on the WAN interface?
Start by power cycling: unplug the modem for 30 seconds, plug it back in, and wait 5–10 minutes for the WAN to obtain an IP address. If you use a separate router, reboot it after the modem is fully online. Also confirm the Ethernet cable is firmly seated (try a different cable/port if possible) and ensure your modem is set to the correct connection type (DHCP vs. static) per your ISP.
What settings should I check if my modem keeps failing to obtain an IP address?
First, verify the modem’s WAN configuration matches what your ISP requires—most use DHCP, while some require static IP credentials. If you recently changed providers or equipment, your modem might still have the wrong authentication details, VLAN, or provisioning profile. Check the modem’s logs or status page for DHCP errors (like “no lease” or “failed negotiation”), which can help pinpoint whether the issue is provider-side or configuration-side.
Which troubleshooting steps are best for IP address issues on a cable or DSL modem?
For cable modems, check for signal and verify downstream/upstream power levels are within the ISP’s recommended range; extreme values can prevent proper registration. For DSL, confirm the modem syncs correctly (line training/link status) before expecting an IP address. In both cases, try a direct connection from a computer to the modem (bypassing the router) to isolate whether the problem is the modem/ISP or the router/network.
Why does my modem fail to get an IP address after upgrading equipment or changing routers?
When you replace a modem or router, the ISP may need to reprovision your line and push updated settings, especially for modem registration and DHCP authorization. If you changed the modem brand/model, your ISP might require the new modem’s MAC address to be added to their system. To resolve it quickly, confirm the modem is supported by your ISP, then reboot and check for DHCP lease attempts on the WAN status page.
📅 Last Updated: October 07, 2026 | Topic: Why Is My Modem Not Getting an IP Address? | Content verified for accuracy and freshness.
References
- https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol
- https://en.wikipedia.org/wiki/IP_address
- https://en.wikipedia.org/wiki/Point-to-Point_Protocol_over_Ethernet
- https://en.wikipedia.org/wiki/Modem
- https://www.rfc-editor.org/rfc/rfc2131
- https://www.rfc-editor.org/rfc/rfc2132
- https://www.rfc-editor.org/rfc/rfc951
- https://scholar.google.com/scholar?q=modem+not+getting+an+IP+address+DHCP+troubleshooting Google Scholar
- https://scholar.google.com/scholar?q=DHCP+client+not+receiving+IP+address+problem+diagnosis Google Scholar
- https://scholar.google.com/scholar?q=PPPoE+no+IP+address+troubleshooting Google Scholar