Authentication issue - DSL connection

[#1]

Hoping someone from PlusNet may be able to assist. At 6.40PM tonight my connection dropped and I’ve had no luck connecting since. Spoke with a CS staff member who ran a line test and looked through some other authentication checks, he said it showed from his logs that multiple PlusNet users are trying to connect to my service? I’ve left it with him that he’s going to speak to others tomorrow to follow up but I thought posting here may help to get me back online quicker.

I use a TP-Link router in bridge mode, which shows a successful DSL connection, along with an ASUS 86U as my main router. I’ve tried the original PN router with no luck, also tried the TP-Link router out of bridge mode as a standard router with no luck.

I’m fairly confident this isn’t an issue on my side, and that it’s an authentication problem on PN side.

Has anyone had this before and if so how was it rectified, alternatively if a PN technical staff member sees this could they take a look?

Thanks

[#2]

Bit late in the day for PN staff (or most Community members). I suggest you wait until you hear back. This sounds like it needs PN to do a bit of investigating, as it just shouldn't happen and only they have the tools/facilities to do so.

[#3]

It is really strange indeed, my connection has been rock solid for years. I’ll wait till the morning and hopefully it can be looked into further then.

I’ve tried the test auth accounts out of interest and also got nothing, the posts detailing those seem to be quite old so I’m not sure if they’re still active.

[#4]

No idea about the 'test auth' accounts - never heard of them to be honest and they'd be no good to me as I'm not with PN these days.

[#5]

As I can’t edit my original post, for further reference I’ve tried the following with no luck.

bt_test@startup_domain - Does not connect
bt_test_user@plusdsl.net - Does not connect

[#6]

@piperstock   did you also add the password when you tried those accounts?

[#7]

I’ve tried with and without. Apparently those tests account do not require authentication? So that adds a little more confusion.

[#8]

It has been a while, but don't recall using them without a password.

Is there any major outage in the area?

And, back to basics, is the phone line working ok?

[#9]

Not that I’m aware of on the outages, and yes phone line works fine, I have a DSL connection showing in the TP-Link router, the line check came back without faults.

[#10]

Have you previously had a Plusnet Hub of some kind and given it away or sold it?  Do you have a static IP address?

If so, I wondering if that has auto configured on someone elses line, which would give them the same external IP address as you, which would then likely cause issues.

[#11]

I don’t have a static IP, I still have my original PlusNet hub which I’ve tested with, and it won’t connect. Tried a factory reset on it too. I haven’t sold or given away any Plus Net hubs, I’ve only had this one since I signed up.

[#12]

Ok, no problem.  I thought it worth ruling out.  Hopefully someone can get to the bottom of it quickly.

[#13]

Definitely, I appreciate any ideas/suggestion to fault find with.

It’s a really odd one, especially as the test accounts also do not connect, but I have a DSL sync!

[#14]

---

@piperstock wrote:
 I still have my original PlusNet hub which I’ve tested with, and it won’t connect. Tried a factory reset on it too.

---

After the factory reset did you log in and check that it repopulated with your Plusnet Username and Password, or was the username: setup@plusdsl.net?

Have you checked that you can log in to your Plusnet account using the router username and password?

[#15]

I cannot confirm that it repopulated and I'm at work today so unable to check until later. I can confirm I can login to my Plusnet account with the same details I am entering into the router (excluding @plusdsl.net)

To be honest I don't think I have any working authentication on my line, I found a previous post on this forum with the same issue and it turned out to be an authentication issue at the exchange OR fixed.