Phones Joined the WiFi Instantly, the Desktop Just Spun Forever: a Misconfigured Second Router (Superloop 100M, Zetland)

Student · ZetlandSuperloop 100MDSL connectionTwo routersPhones fine, desktop cannot joinGaming LAN port used

This is one of those faults where the symptom points you at the wrong device. The desktop was the thing that would not connect, so the desktop looks like the problem. It was not. The problem was a second router sitting quietly in the living room, doing its job badly enough to affect one type of device and not another.

The setup

Location: Zetland. Provider: Superloop. Plan: 100 Mbps. Connection: DSL.
Two routers in the flat — a main unit that supports DSL and handles the dial-up, and a second ASUS connected to it by its WAN port, providing the WiFi everyone actually used.
Reported fault: phones and other mobile devices connected to the WiFi normally, but the desktop spun forever and never joined.
Handled as an on-site visit.

How the flat was actually wired

Superloop DSL line

100M plan

→

Main router (dial-up)

→

Second ASUS via WAN port

misconfigured

Bottleneck

→

Phones

joined fine

→

Desktop

spins, never joins

Two routers in series is a normal arrangement: the first one dials the connection, the second provides the WiFi you actually use. But the second one has to be set up for that role. When it is not, address allocation can go wrong, and the failure often shows on one class of device while others look fine — which is exactly why people blame the computer.

Reading the symptom correctly

Why the phone was fine and the desktop was not

	Phones and tablets	Desktop
Symptom	Joined the WiFi normally	Spun indefinitely, never joined
What that tells you	The radio and the SSID are working	The problem is after association, not before
Common wrong conclusion	—	The computer's network card is broken
Actual cause here	—	Second router not configured for its role

The split between device types is the most useful clue in this fault, and it is worth understanding why.

If the WiFi name is visible and phones join it, the wireless side of the second router is working. That rules out a lot.
A device that associates and then hangs is usually stuck waiting for an address, not struggling with signal.
Which is why the natural conclusion — that the desktop's network card has failed — is usually wrong. The desktop is the messenger.
The first thing worth checking in any two-router household is whether the second router has actually been configured for the job it is doing.

What we did on site

How it was isolated on site

Map the setup: which router does what

Main = DSL dial-up, ASUS = daily WiFi

Reproduce the fault with the desktop

Cannot join the ASUS network

Form the hypothesis: second router misconfigured

Suspect address allocation

Factory-reset the ASUS

Clean configuration

Relocate it from the living room to his bedroom

Closer to where he uses it

Use its gaming LAN port, wired to the desktop

Wired path for gaming

Rejoin with the desktop and restore the old SSID

Joins normally

Moving the router was not part of the fault, but it was worth doing while we were there.

The ASUS has a dedicated gaming LAN port, and he games regularly, so putting it in his room let us wire the desktop directly to that port.
A router in the room he actually uses also gives him better wireless than one sitting in the living room.
The network name was set back to what it had been, so nobody in the flat had to re-enter credentials on every device.

If you have two routers at home

Frequent disconnections, or devices that cannot join at all, are a common sign that one of the routers is not correctly configured for its role.
Check that the second router is set up as the device that hands out addresses, or as one that deliberately does not — but not accidentally somewhere in between.
If only some devices are affected, that is a clue, not a coincidence. Note which ones work and which do not before you change anything.
A reset on the second router is a reasonable early step, as long as you know the connection details for the main one.

Result

Root cause: the second ASUS router, connected to the main DSL router by its WAN port and serving as the household WiFi, had not been correctly configured for that role, causing address allocation to fail for the desktop while phones connected normally. We reset the ASUS, relocated it from the living room to his bedroom to make use of its dedicated gaming LAN port for a wired connection to the desktop, and restored the original network name. The desktop then joined the WiFi normally.

Zetland service area Superloop guide Router setup service Gaming home network setup Why there is no internet and how to recover WiFi repair service

Phones Joined the WiFi Instantly, the Desktop Just Spun Forever: a Misconfigured Second Router (Superloop 100M, Zetland)

The setup

Reading the symptom correctly

What we did on site

If you have two routers at home

Related

Facing something similar?