Case Studies / Latest Case A Brand-New Router Nobody Could Log In To: the Password on Its Own Label Was Rejected and a Factory Reset Changed Nothing (Superloop 250M, Zetland)
On-site · ZetlandSuperloop250 Mbps planOld DSL wiring upgraded by OpticommNew D-Link: admin login rejectedConfigured on a TP-Link instead
Almost everything about this job had already been done by somebody else. The plan was active, the line had been upgraded, the socket that worked had been identified. What nobody had done was the last twenty minutes of work that turns all of that into internet — and when we sat down to do it, the router the customer had just bought turned out to be the only thing in the flat we could not get into.
Two half-finished networks and no internet
The request that came in over chat described two things at once: a Superloop connection that needed to be brought up, and a speed problem. Those usually turn out to be one problem wearing two hats, and on arrival that is roughly what it was — but not in the shape the messages had suggested. This is normal. What a customer can see and describe is the symptom; the layout that produces it only becomes visible when you are standing in the room. The first useful thing we did here was throw away the remote picture and rebuild it from what was actually in front of us.
What was actually there: the flat had been running on a router with a phone SIM in it, which is a legitimate way to be online and a poor way to stay online, because it generally tests in the tens of Mbps. Separately, the customer had taken out a Superloop plan, and Opticomm had already been out to upgrade the premises away from the old DSL wiring. That crew had done their part and told the customer which socket the service now landed on. They do not configure routers, so that is where it stopped.
What was already done, and where it stopped
Superloop 250M plan
active
→
Opticomm line upgrade
done
→
Working wall socket
pointed out, not configured
Gap
→
Router configuration
nobody’s job
Gap
→
An upgrade order and a working line are not a connection. An infrastructure crew is contracted to make the physical path good and to tell you which socket it now lands on; configuring a router is explicitly outside that, and it is not something the retail provider sends anyone out to do either. The gap is small measured in hours and total measured in outcome: this customer had paid for a 250 Mbps service that had been correctly delivered to the wall, and could not use a byte of it.
Step one is proving the socket is live — with a router you already trust
There were two unknowns in this flat at the same time: whether the upgraded socket really carried a service, and whether the customer's equipment worked. Testing both at once is how people lose an evening. If you plug an untested router into an untested socket and nothing happens, you have learned nothing at all.
So the first thing through the socket was a router we knew was good. It came up, which settled the line question permanently: the upgrade had been done properly, the socket the crew named was the right one, and nothing further up the chain needed investigating. Every problem discovered after that point was, by definition, on the customer's side of the wall — which is exactly where the next one was.
What we actually did on site
1
Re-established what was actually in the flat
What had been described online did not match
2
Tested the wall socket with a router known to be good
Confirm the line before touching any settings
3
Started configuring, and could not get into the new D-Link
The username and password on its base were rejected
4
Factory reset, tried the label credentials again
Same rejection — advised asking for a refund
5
Configured the TP-Link the landlord had left instead
Left a spare TP-Link of ours in the flat as well
6
Speed tested, renamed the WiFi, kept a single network
1b1b flat — splitting the bands helps nothing here
The router that rejected its own password
The customer had bought a new D-Link for this. To configure any router you first log in to its admin page, and the username and password for that are printed on a label on the base of the unit. Those were entered exactly as printed and came back as an error. That is not, on its own, alarming — labels get read wrong, characters get confused, and there is a standard answer for it: hold the reset button, put the unit back to factory state, and the credentials on the label become correct by definition, because a factory reset is what makes them true.
It was reset, and they were still rejected. In over a hundred jobs this was the first time we had seen it, and there is no clean diagnosis to offer: the most likely explanation is simply that the unit shipped with the wrong label on it, so the printed credentials never matched the ones inside. It is not worth an evening either way. A router you cannot log in to is a router you cannot configure, and a brand-new unit in that state is a warranty matter, not a repair. We advised the customer to return it for a refund and moved on with hardware that worked: the landlord's TP-Link was already in the flat and took the configuration without complaint, and we left a spare TP-Link of ours there as well so the customer was not left depending on a single borrowed unit.
The practical lesson is about sequencing rather than brands. Log in to a new router and change its admin password before you need it under pressure — at the kitchen table on a quiet evening, not at the point where it is the last thing standing between a flat and its internet. If the label credentials are going to fail, it is much better to find that out while the shop's return window is the only thing at stake.
The two networks running in this one flat
| Router with a phone SIM in it | Superloop on the upgraded line |
|---|
| How it connects | Over the mobile network, through the router’s SIM | Over the fixed line to the wall socket |
| Speed seen in this flat | A few tens of Mbps, typically | The plan’s speed, on the day |
| What it costs to keep | A second service, running in parallel | Already paid for and unused |
| Why it was still the one in use | Because it was the only thing that worked | Because nobody had configured it |
What the line gave once somebody configured it
With the TP-Link configured, the connection came up and tested at the speed of the plan. Worth putting the three numbers side by side, because they describe why this job was worth doing at all: the SIM router the flat had been living on ran in the tens of Mbps; the old DSL wiring, before Opticomm came out, topped out around a hundred; the upgraded line on the Superloop plan delivered its rated speed the same afternoon it was finally set up.
One last decision, which is a judgement call rather than a rule: this is a 1b1b apartment, so the whole flat is within a few metres of the router. In that footprint there is no coverage problem to solve and no benefit in splitting the 2.4 GHz and 5 GHz bands into two separate network names — it just gives the occupant two things to choose between and a chance to pick the wrong one. We kept a single network name, set it to what the customer wanted, and left it there.
What this address could actually deliver, before and after
The old DSL wiring, before the upgrade
Superloop 250M, once configured
250Mbps — the plan speed, reached on the day, on a line that had been sitting ready and unconfigured.
What to take from this one
- An infrastructure upgrade being finished does not mean you have internet. Somebody still has to configure a router, and that somebody is not the crew who did the line.
- Test an unknown wall socket with a router you already know works. Two unknowns at once tell you nothing.
- Log in to any new router and change its admin password on the day you buy it, not on the day you depend on it.
- If a reset router still rejects the credentials on its own label, stop. That is a return, not a repair.
- A router running on a phone SIM is a reasonable stopgap and a poor permanent plan — it usually tests in the tens of Mbps.
- In a one-bedroom flat, one network name is better than two. Splitting the bands solves a coverage problem you do not have.
Result
The upgraded wall socket was live all along and the line needed nothing but configuration, which is what nobody had been contracted to do. The new D-Link never accepted its own printed credentials even after a factory reset and went back for a refund; the TP-Link already in the flat took the settings and came online at the plan's speed, with a second TP-Link left on site as a spare, a single network name suited to a 1b1b layout, and the SIM-card router no longer needed.