Practical digital skills

Troubleshoot computer Internet access

Separate connection, Wi-Fi coverage, browser and destination failures.

Step-by-step guideUpdated
Follow the method ↓
A laptop and organised documents on a desk

The answer in 30 seconds

A failure in one website is different from losing connectivity on every device. A repeatable comparison is more informative than changing many settings.

Check the active connection, open two known sites and compare another device. Use Ethernet where practical to distinguish Wi-Fi issues from access problems.

Examples to adapt

Ethernet works but Wi-Fi fails

Inspect the wireless coverage and settings before blaming the external line.

One browser fails on one page

Compare profile, extensions and the actual page action.

Follow the method

  1. 1
    Read network status

    Identify Wi-Fi or Ethernet and the intended network. Check whether the system reports an active connection.

  2. 2
    Test two destinations

    If only one fails, investigate that site. If both fail, compare another device on the same connection.

  3. 3
    Compare cable and Wi-Fi

    A practical Ethernet test can help isolate coverage or interference. Keep the destination and action the same.

  4. 4
    Check the browser separately

    Try another up-to-date browser or a private window. A difference suggests a context or extension issue; test extensions one at a time.

  5. 5
    Restart carefully

    Save work first. Follow the computer and router documentation, allowing the connection indicators to settle before retesting.

A checklist to keep

Use these checks to record what you found. The grid supports a decision; it does not make one for you.

Troubleshoot computer Internet access: checklist
CheckWhat to examineAction
NetworkActive route and statusInspect system information
DestinationOne or several sites affectedTest two known pages
CoverageEthernet compared with Wi-FiKeep the test consistent
BrowserProfile and extension contextChange one variable

Download the CSV checklist

Free, no sign-up. UTF-8 text with semicolon-separated columns.

What to check

Do not publish network credentials.

Record changes and reversal steps.

A private-window result is a diagnostic clue, not proof of one cause.

Common questions

Should I reset everything immediately?

No. Compare sites, devices and connection types first.

What should I tell support?

Device, connection type, symptoms and the tests already performed, without credentials.

Sources and documentation

Documentation consulted on . Examples are illustrative; interfaces and results may change.

Continue exploring

All English guides →