The household experienced a sudden and persistent network problem after a service visit. Before the technician arrived, multiple gaming consoles had connected to the internet reliably for over a decade. A field technician initially performed an internet speed test and concluded that a new modem was unnecessary. Later the same visit included work on the coax cabling, after which the consoles could associate with Wi‑Fi and Ethernet networks but would not actually access the internet. This paragraph frames the core issue: local link is present but end‑to‑end connectivity is absent.
Since that first visit, two additional technicians returned to troubleshoot the fault. Each performed different interventions: rewiring the coax, swapping the modem, and testing signal paths. Despite those efforts the consoles remain online at the local level yet show no external connectivity. The homeowner also attempted their own troubleshooting: buying new Ethernet cables, testing several gaming consoles, and installing a personal router. None of these actions restored internet access. The timeline emphasizes a change introduced by the technician that correlates with the failure.
Technician actions and immediate impact
The first technician began with diagnostics and a speed reading that suggested the connection was nominal, so no replacement modem was required. Later the same technician reworked the coax setup—possibly moving splitters, tightening connectors, or rearranging grounding. Immediately after that work the consoles reported a successful link to local networks but failed to reach external sites and services. The distinction between link state and internet access suggests a disruption in either signal quality, provisioning, or a layer where the ISP hands off traffic. Identifying what changed at the physical and provisioning layers is crucial to isolating the fault.
Troubleshooting timeline
Two follow-up technicians performed broader troubleshooting: they swapped hardware, checked wiring, and attempted to reconfigure equipment. Although they tried replacement modem units and adjusted the cabling again, the symptom persisted. The household owner supplemented those efforts by swapping cables and adding a personal router to remove the ISP router as a potential single point of failure. Because multiple consoles and multiple routers still fail to access the internet, the problem likely sits between the premises network boundary and the ISP network, or with provisioning that authorizes devices to carry traffic.
Tests performed
Technicians performed the usual diagnostics: signal level checks, modem swaps, and physical wiring inspections. The consoles can obtain an IP at the local level and show an active connection to Wi‑Fi or Ethernet, but cannot communicate beyond the local gateway. This pattern rules out simple cable faults and points toward issues such as failed provisioning in the ISP’s system, misconfigured modem modes like improper bridge vs router mode, or a bad splitter introducing noise that prevents upstream registration. Each of these is a network layer or configuration problem rather than a hardware-only cable fault.
Devices and equipment tried
The homeowner tried multiple consoles, new Ethernet cables, and a personal router, and technicians installed different modem units. Because the same symptom persisted with different hardware, attention should shift to the physical coax run, the node or line causing signal degradation, and the ISP’s backend. Key things to verify are whether the modem shows correct DOCSIS sync (if applicable), whether the ISP has provisioned the modem’s MAC address, and whether any splitters or amplifiers were altered during the initial visit.
Likely causes and recommended next steps
Possible root causes include a damaged or misconfigured coax run, a splitter with degraded isolation, incorrect modem provisioning at the ISP, or a modem operating in the wrong mode (for example, incorrectly set to bridge or double NAT). Signal level problems—too low or too high—can let the modem link locally but prevent proper registration with the ISP. The homeowner should request that the ISP run an external signal and node check, confirm modem provisioning, and document any changes made during the initial visit. Ask for an escalation if field techs only perform hardware swaps without verifying provisioning and signal metrics.
Practical next steps: insist on a technician who will test the coax back to the tap and verify signal levels at the modem; request removal of any newly added or moved splitters to restore the previous wiring topology; test a direct, single coax run from the street tap to a known working modem to isolate premise wiring; and have the ISP verify that the modem’s MAC address is registered. Also capture logs from the modem if possible, and try a direct laptop connection to see if the issue affects nonconsole devices. If the ISP cannot resolve it, ask for escalation to a higher tier that can examine node‑level issues.
In summary, the problem began immediately after coax work and persists despite multiple technician visits and homeowner tests. The evidence points to signal or provisioning issues introduced during the visit rather than faulty consoles or home cabling alone. Clear documentation, escalation, and coordinated testing between the premises and the ISP network should restore service. Keep records of technician actions and test results to speed any escalation and resolution.
