CHAP Authentication Problem

[#1]

Woke up this morning and went to go online and my router isnt connecting to the internet its getting chap authentication problem.
Rebooted it and reset it a number of times.
Any ideas?

[#2]

Hi there,
I've run a couple tests on your line and I'm seeing you as having synchronisation with the exchange but I'm not seeing any failed login attempts.  What happens if you manually go into your router and reenter the username and password details?

[#3]

Have you changed your password on PN's website at all?  If you change that you need to change the password in your router.
If it's not that then I'd firstly check to make sure that the user name and password are correctly set in the router.  You could then try powering everything down for 30 mins and reconnecting as you may have a stale session.
Failing all of the above - give support a call.

[#4]

thanks for the help. i had not changed it in ages. but after trying log into forum which i had not done i asked to reset my pass and i set it bk to what i thought it was. but forum isnt joined to plusnet login right?
anyway it works now. not sure why. thanks tho

[#5]

Not sure!  Glad it's working though

[#6]

We've just had a surge of authentication calls, normally when this happens there is an associated BT MSO (Major Service Outage) but we haven't received on yet. The amount of calls coming in are slowing down so the main issue seems to be clearing up. I'll let you know if we find out more details of what the problem was.

[#7]

http://usertools.plus.net/exchanges/mso.php?id=6234 ?

[#8]

Yup, could well be. We received that email at exactly midday.

[#9]

Quote from: Chris

We've just had a surge of authentication calls, normally when this happens there is an associated BT MSO (Major Service Outage) but we haven't received on yet. The amount of calls coming in are slowing down so the main issue seems to be clearing up. I'll let you know if we find out more details of what the problem was.

I had a phone call from my friend saying that they couldn't get a connetion  etc  so I did a tracerout and got theses figures.
Find route from: 192.######
            to: plus.net (212.159.8.2), Max 30 hops, 40 byte packets
Host Names truncated to 32 bytes
1 192.#######(192.###### 😞    1ms        0ms        0ms 
2 lo0-plusnet.pte-ag1.plus.net    (195.166.128.64 😞    13ms      13ms      13ms 
3 ge0-0-0-403.pte-gw2.plus.net    (84.92.4.2      😞    14ms      13ms      14ms 
4 te2-4.pte-gw1.plus.net          (212.159.1.101  😞  165ms      106ms      187ms 
5 atm1-0.ptb-gw1.plus.net          (212.159.1.89  😞    20ms      24ms      23ms 
6 vl427.pih-gw3.plus.net          (212.159.1.123  😞    20ms      23ms      20ms 
7 if25.pih-lb03.plus.net          (212.159.0.17  😞    20ms      30ms      25ms 
8 if25.pih-lb03.plus.net          (212.159.0.17  😞    21ms      70ms      22ms 
• Trace completed 18/3/08    11:32:04    •

Start: 18/3/08    11:45:33   
Find route from: 192.168.0.3
            to: plus.net (212.159.8.2), Max 30 hops, 40 byte packets
Host Names truncated to 32 bytes
1 192.####                        (192.####):    1ms        0ms        0ms 
2 lo0-plusnet.pte-ag1.plus.net    (195.166.128.64 😞    15ms      15ms      20ms 
3 ge0-0-0-403.pte-gw2.plus.net    (84.92.4.2      😞    14ms      13ms      13ms 
4 te2-4.pte-gw1.plus.net          (212.159.1.101  😞    15ms      12ms      12ms 
5 atm1-0.ptb-gw1.plus.net          (212.159.1.89  😞    19ms      19ms      18ms 
6 vl427.pih-gw3.plus.net          (212.159.1.123  😞    21ms      22ms      21ms 
7 if25.pih-lb03.plus.net          (212.159.0.17  😞    23ms      20ms      36ms 
8 if25.pih-lb03.plus.net          (212.159.0.17  😞    19ms      19ms      20ms 
• Trace completed 18/3/08    11:45:36    •

Hop 4 in the first trace caught my eye.. Could this be the reason?

[#10]

Nope.
High ping times within transit can be normal and in the majority of cases are to be expected. You have to take figures from end to end into account.
The job of these intermediate routers is to route data and responding to pings is normally treated as low priority.