Wifi not working but the internet is fine: the local-layer checklist

What to answer first, ranked from the data

Score is sqrt(volume) x a difficulty allowance x an intent weight for pricing and outage wording. It is a ranking rule, not a promise - but it is why this page leads with what it leads with.

What people actually search here

This topic is 9 real phrasings carrying 280 tracked searches a month. The three that open it: etisalat wifi not working / du wifi not working / sony vaio e series laptop wifi not working in win10. They are grouped here instead of listed twice - the individual rows are in the coverage map below.

Intent mix inside this cluster: PROBLEM (9). People move from diagnosis wording to pricing wording in the same week, which is why the answer and the cost table sit on one page.

2 of these phrasings sit at KD 25 or below - "etisalat wifi not working" among them - which is why this page is written as an answer rather than a list of links

Wi-Fi not working while the internet is fine

Steps

1. Forget the network on the affected device, then re-enter the password on the sticker (case-sensitive, no trailing space).
2. Reboot the router - the DHCP pool is the usual culprit when a device says "obtaining IP address" forever.
3. Move the router out of the cabinet/metal box; vertical position, one metre up, away from the TV.

source: verified resources · full guide

This section is filtered to the phrasings inside "Wifi not working but the internet is fine: the local-layer" - which is why it reads shorter than the full guide on etisalat wifi not working. Follow the link when you need the whole procedure, not just the part that applies here.

du home internet not working - the 5-minute check

Steps

1. Restart once - unplug the router for 30 seconds, not 5, then wait 3 minutes for the ONT to re-register.
2. Still red after a reboot? Open the du app and raise a fault so the ticket timestamp starts now; escalate to us on WhatsApp and we will chase the job number.

source: verified resources · full guide

This section is filtered to the phrasings inside "Wifi not working but the internet is fine: the local-layer" - which is why it reads shorter than the full guide on etisalat wifi not working. Follow the link when you need the whole procedure, not just the part that applies here.

Plans and what they cost over the term

Ordered by how well each tier answers the wording here - "etisalat wifi not working" first among 12 published tiers. A tier that cannot be delivered to your unit is not cheaper for being a lower number.

Arithmetic on the published tier price only. It excludes installation, device instalments and any credit specific to your account - which is exactly what the free check settles.

Reading the phrasings themselves

For “etisalat wifi not working” (170 searches a month, KD 14): it is a fault report, so the timestamp and the indicator state matter more than any setting you might change first.

For “du wifi not working” (110 searches a month, KD 19): it is a fault report, so the timestamp and the indicator state matter more than any setting you might change first.

For “sony vaio e series laptop wifi not working in win10” (0 searches a month): it is a fault report, so the timestamp and the indicator state matter more than any setting you might change first.

For “after i change etisalat wifi password internet not working” (0 searches a month): it is a procedure question, so the value is in the order of the steps rather than their existence - doing the right one first is what saves the callback; it is a fault report, so the timestamp and the indicator state matter more than any setting you might change first.

For “etisalat elife wifi not working” (0 searches a month): it is a fault report, so the timestamp and the indicator state matter more than any setting you might change first.

For “etisalat wifi is not working for google home” (0 searches a month): it is a comparison, and at one address a comparison is between what can actually be delivered there, not between two adverts; it is a fault report, so the timestamp and the indicator state matter more than any setting you might change first.

For “etisalat wifi password change not working” (0 searches a month): it is a procedure question, so the value is in the order of the steps rather than their existence - doing the right one first is what saves the callback; it is a fault report, so the timestamp and the indicator state matter more than any setting you might change first.

What the wording of these searches tells you

• These phrasings describe a total loss, so start at the indicator lights and the account status, not at the wifi settings; a red WAN light is not a channel problem.
• Router questions are usually configuration or placement, so change one variable at a time and note the result before you conclude anything about the line itself.

Coverage map: every phrasing this page answers

Every row is a real query inside Wifi not working but the internet is fine: the local-layer with its measured volume and difficulty. A guide that cannot answer all of them is not a guide for the topic, which is why the list is printed.

Checklist before you act

• Keep a single ticket reference for the whole event
• Reproduce it once, deliberately, and write the time down
• One wired test at the moment of failure
• Note every indicator light, in order, with a photo
• Check whether anyone else on the network sees the same thing
• Name the exact phrase you searched - "etisalat wifi not working" - in your first message, because it selects the queue your case belongs to.

Mistakes that cost people money

• Accepting a fix confirmed in the morning for a fault that happens at night
• Opening a second ticket instead of reopening the first
• Describing drops as slowness, which routes you into the wrong diagnosis
• Resetting to factory settings while a technician is still investigating
• And the structural one for etisalat wifi not working: writing advice for 9 phrasings under a problems & fixes heading and leaving the account-specific number unverified.

How to read the numbers on this page

9 phrasings and 280 searches a month is not one question but a family of them, opening on after, du, etisalat, sony, why, wifi. That mix is why a price table alone fails here: each phrasing asks about a different stage of the same decision.

Average difficulty across the tracked phrasings is 16, with 2 of them at KD 25 or below. Low difficulty at this volume usually means the ranking pages are thin listings, so a page that walks through the check order competes on usefulness rather than on tricks.

Read the cost table as arithmetic, not as an offer: it multiplies the published tier price by the contract length and shows what a VAT-inclusive quote would add. Installation, device instalments and account credits are not in it, because only your address and account can settle those.

If you need to escalate

1. If the committed time passes, ask for a supervisor and for the operator response in writing, naming the missed commitment and requesting the credit schedule.
2. Only then move to the formal complaint route with the whole thread attached. Keep the invoice, the log and every reference number together.
3. Take the evidence, not the adjective: one measurement taken at the hour the fault happens, with the indicator state photographed and the date on it.
4. Ask for a fault record and a written reference, and ask what the committed resolution time is for that record. Do not accept a callback promise as an outcome.

The same ladder applies to every problems & fixes case on this site, because the order is what changes the outcome - not the words you happen to use.