"There's no internet" is a symptom, not a diagnosis. The issue could affect one application, one device, a wireless network or an entire site. A useful Network+ habit is to narrow the scope before changing settings.

Consider a laptop that cannot open a website. Other laptops on the same Wi-Fi network work normally. What should you check first?

Establish the scope

Ask whether the issue affects only one website, all websites, one device or many devices. Check whether the laptop can reach a local resource and whether other users report the same problem. A fault isolated to one laptop points you towards its connection, addressing and local configuration. A fault affecting every device calls for a different investigation.

Do not jump straight to replacing equipment. A quick scope check can prevent unnecessary changes and preserve clues about the original fault.

Work from the connection towards the service

A practical sequence is:

1. Check the local link. Is Wi-Fi connected to the expected network, or is the cable connected and the interface enabled?
2. Inspect the address. Does the device have an appropriate IP address, subnet information, gateway and DNS configuration?
3. Test a local destination. Can it reach the default gateway or another known device on the network?
4. Test name resolution. If connectivity works with an IP address but not a hostname, investigate DNS.
5. Check the application. A proxy, VPN, browser setting or service-specific fault can affect access even when the network itself works.

These checks are a reasoning order, not a guarantee that every fault will appear in that exact sequence. Adapt to the evidence you gather.

Keep track of what changed

Suppose the laptop has an address that does not match the expected network. Investigate how it obtained the address before manually replacing it. Was the device connected to a guest network? Did a DHCP request fail? Did a static configuration remain from a previous site? Each possibility suggests a different correction.

Once you fix the issue, confirm that the user can reach the original website and that other services still work. Document the cause and action so a recurring fault is easier to recognise.

Use this approach in revision

For every missed Network+ troubleshooting question, note the observed symptom, the smallest affected area and the next test that would distinguish two possible causes. That habit is more transferable than memorising a single command for every question.

You can use the ICT Exam Academy Network+ course to reinforce networking concepts and practise scenario-based decisions.