Technicolor TG582n & Windows 10

Just had an interesting chat with a friend.

Appears there is a known fault with the PlusNet supplied Technicolor TG582n routers when using windows 10 PC's.

Basically DNS stops working resulting in all addresses being looked up as 198.18.1.x

PlusNet admit there is a fault, PlusNet know they cannot fix it..


Yet refuse to replace the routers, forcing people to sign new contracts to replace the router or make them pay £50 for a replacement.

Guessing people just cancel and go elsewhere ... seems a weird scenario they are putting people in.

or buy one off ebay for 10-20£

Yes, but all costs the end user money for something the ISP knows they have supplied and knows is faulty.

They'll still happily take £17 a month of you for a service which no longer works... and to make it work means spending your own money or committing to a new 24 month contract.

For a end user it makes it easier to just move to another supplier on a deal at £15 a month for a year and get a new router with the move.

Does not setting Google DNS 8.8.8.8 as the primary on the PC not fix it?

Given the number of things Windows 10 is alleged to have broken, maybe Microsoft has to provide the solution.

equally does setting the DNS servers in the router manually instead of automatically fix it

I've got a TG582n and am running Windows 10. There have been no problems with the initial Windows 10 nor with the Anniversary version. Everything works OK with DNS servers in the router and from the PC. (The router GUI displays the Plusnet servers. I haven't bothered changing them manually, which requires a telnet session.)

Setting them to 8.8.8.8 does resolve it yes, although then you are telling google everything you do .... but that is a different conversation all together.

Problem is though when you go to a different network (say your work network with internal DNS servers) then you have to switch back..

I can replicate the issue at their house on 3 different W10 laptops.

It breaks within 30 seconds of being connected, so it seems it may be limited to specific versions of that model then if you are OK

could it be firmware related - this gives the options http://products.plus-payh.co.uk/firmware/

In reply to a post by Tam:

I can replicate the issue at their house on 3 different W10 laptops.

By chance do these W10 laptops all use the same security software product?

In reply to a post by Oldjim:

could it be firmware related - this gives the options http://products.plus-payh.co.uk/firmware/

100% firmware related, a google of TG582n and 198.18.1 results in lots of noise about it.

Seems strange how PN just turn existing customers away rather than fix the issue.

Edited by deleted (Thu 22-Sep-16 22:48:22)

I should mention since looking into it more this thread over which has had posts about this issue for the last 2 years clearly shows the issue at PN.

https://community.plus.net/t5/Broadband/198-18-1-x-a...

Although reading the thread it also shows that PN have a fix for it... eventually

I wasn't privy to the conversation that went on between the end user and PN, I just know the result was that the only option was buy a router, or sign up to a new 24 month contract and get a free router, and that because of that they took the option to just leave for another provider at a much cheaper "new user" price and were supplied a new router with only a 12 month contract.

The router they sent me never worked, I just used my old hh3 for maybe 2 years and when that packed up I got a tp-link wr841n at Argos for less than £20. I can hardly believe how good this router is considering how little it cost.

I've had no problems at all with a TG582n on Windows 10 but I use OpenDNS. I'm struggling to understand what the Operating System version has to do with it.

The suggested google search reveals problem reports from before windows 10 and from ISPs worldwide.

Was that using the ADSL version of the router, or the FTTC version where one port connects to a VDSL modem?

According to that thread it looks like it's worth putting this into telnet:

"dns server config WANDownSpoofing=disabled"

I'm not a fan of WAN Down DNS Spoofing in any case, "helpful" features like this have a habit of going wrong.