🌐 No Internet? Let’s Fix It.

🌐 No Internet? Don’t Panic — Let’s Fix It.

You sit down, open your browser and...

No Internet.

Great. Exactly what we needed today. 😅

Before restarting everything, blaming the router, or calling the ISP immediately, let’s troubleshoot this like IT Support actually would.

The idea is simple:

Find where the connection stops → fix that point → test again

Step 1 — Start With the Obvious

Yes, the obvious stuff matters.

Before opening Command Prompt and pretending we are hackers, check:

• Is Wi-Fi turned on?
• Is Airplane Mode off?
• Is the Ethernet cable connected?
• Are you connected to the correct Wi-Fi network?
• Are other devices also offline?

Why this matters

If every device in the house or office is offline, the problem is probably not your computer.

It could be:

Router → Modem → ISP

But if only one computer has the problem...

Perfect.

Now we know where to investigate.

Step 2 — Disconnect and Reconnect

Sometimes technology just needs the classic:

“Have you tried turning it off and on again?”

And yes...

There is a reason IT people say this. 😅

For Wi-Fi:

1. Disconnect from the network.
2. Wait a few seconds.
3. Connect again.

For Ethernet:

1. Unplug the cable.
2. Check if the connector looks damaged.
3. Plug it back in firmly.

Still no internet?

Good.

Now we get to the interesting part.

Step 3 — Check Your IP Address

Open:

Command Prompt

Then type:

ipconfig

Look for:

IPv4 Address

A normal private IP might look like:

192.168.1.25

or:

10.0.0.15

But if you see:

169.254.x.x

we found something important.

What is 169.254.x.x?

That is an APIPA address.

Basically, your computer tried to ask the DHCP server:

“Hey, can I get an IP address?”

And nobody answered. 😅

Windows then gives itself a temporary address starting with:

169.254

That usually points us toward a DHCP or network communication problem.

Step 4 — Can You Reach the Router?

Still in Command Prompt, find:

Default Gateway

It may look like:

192.168.1.1

Now type:

ping 192.168.1.1

Replace that address with your actual gateway.

If you receive:

Reply from...

Nice.

Your computer can communicate with the router.

If you get:

Request timed out

or:

Destination host unreachable

then the problem may be between:

Computer ↔ Router

Check Wi-Fi signal, cables, adapter status and IP configuration.

Step 5 — Can You Reach the Internet?

Now let’s go one step further.

Run:

ping 8.8.8.8

If you get replies:

🎉 Your computer can reach the internet.

But...

If websites still refuse to load, we may have a DNS problem.

If 8.8.8.8 also fails, the issue is probably further up the network.

Step 6 — Test DNS

Now type:

nslookup google.com

DNS is basically the internet’s phone book.

You type:

google.com

DNS finds the IP address for you.

Without DNS, you would have to remember numbers instead of website names.

Nobody wants that. 😅

Quick test

If this works:

ping 8.8.8.8

but this fails:

ping google.com

then DNS becomes one of our main suspects.

Step 7 — Get a Fresh IP Address

If the IP configuration looks suspicious, let’s ask DHCP for a new one.

Open Command Prompt as Administrator.

Run:

ipconfig /release

Then:

ipconfig /renew

What just happened?

/release

says:

“I’m giving up my current IP address.”

/renew

says:

“DHCP, can I have a new one please?”

Very polite troubleshooting. 😂

After that, run:

ipconfig

again and check the new address.

Step 8 — Flush DNS

Sometimes Windows has old or incorrect DNS information saved locally.

Run:

ipconfig /flushdns

You should see:

Successfully flushed the DNS Resolver Cache.

Then reopen the browser and test again.

This is a very common fix when:

• Some websites do not load
• A website recently changed servers
• DNS information became corrupted

Step 9 — Check the Network Adapter

Still broken?

Let’s check the hardware and driver side.

Open:

Device Manager → Network adapters

Look for:

• ⚠️ Yellow warning icons
• Disabled adapters
• Driver errors
• Missing adapters

You can also try:

Disable device → Enable device

If necessary:

Update driver

or reinstall the adapter driver.

If Windows cannot properly communicate with the network card, everything above it will fail too.

Step 10 — Router or ISP?

If multiple devices are having the same problem, your computer may actually be innocent for once. 😅

Restart the router or modem:

1. Turn it off.
2. Wait about 30 seconds.
3. Turn it back on.
4. Wait for the lights to stabilize.
5. Test again.

If every device still has no internet but the local network works, check for an ISP outage.

At this point, contacting the provider makes sense.

🧠 The IT Support Way of Thinking

When someone says:

“The internet is broken.”

That does not tell us much.

Our job is to figure out where it is broken.

Think like this:

Device → Network Adapter → IP → Router → Internet → DNS

Test one layer at a time.

That is much better than randomly changing settings and hoping something works.

⚡ Commands Worth Remembering

ipconfig

Shows your basic network configuration.

ipconfig /all

Shows the detailed version.

ping

Checks whether another device responds.

nslookup

Tests DNS resolution.

ipconfig /release

Releases the current DHCP address.

ipconfig /renew

Requests a new one.

ipconfig /flushdns

Clears the local DNS cache.

✅ Final Troubleshooting Flow

Next time someone says:

“My Wi-Fi is not working.”

Don’t panic.

Follow the path:

1. Check Wi-Fi / cable

↓

2. Check the IP

↓

3. Ping the Gateway

↓

4. Ping 8.8.8.8

↓

5. Test DNS

↓

6. Renew DHCP

↓

7. Flush DNS

↓

8. Check the adapter

↓

9. Check the router

↓

10. Check the ISP

💡 Ask Paulo Tip

One of the best first questions in networking is:

“Is this happening on one device or every device?”

That one question can save you several minutes of troubleshooting.

If it is one device, investigate the device.

If it is every device, investigate the network.

Simple question.

Big difference. 😎