thn-ag2 LLU Slowdown and Poor Ping responses frustrated of Hampton

[#1]

Just to log my problem and hopefully feed this back to Plus Net as there is simple  way I can do this once "question" has been closed.
I havent had a problem , and indeed the service has improved, since that terrible October I think it was when Plusnet's LLU service for some of us was intermittant slow and bursting around for about three months until it was traced to a faulty card in the gateway I think.
Anyway a similar experience occured out of the blue three weeks or more ago and has just been resolved by me going onto the thn-ag3 test gateway.
My ping responses dropped, my speed went down to a 150bps crawl and my rout showed thn-ag2.
At one point I couldn't even get the router to login which might have been a  red herring.
Nothing had changed literally on my network and after unplugging everything, leaving the router off for an hour here and there, changing the hardware to a newer router I was still frustrated.
Indeed I have had speeds up to and over 7M a huge improvement since I had been used to speeds of 1-1.5 - 2 at most until about 6 months ago.
So anyway - nothing had changed and I'd lost all reliability last week - the most frustrating thing was not having any response other than the usual 1st line have you tried.... which I had. MY 15 years as an IT and electronics engineer had prepared me for the frustration as a user at the end of deaf ears to my problem. I initiated the DSL fault checkser etc etc and was asked many irrelevant questions - can you get to a web page ...well yes....but....is you connection slow - well...no its 7Meg but... ...yes it's 150bps...but.....
My ping results to bbc were  great great - rubbish - timeout timeout - great great timeout - you know the ones. I forwarded these onto pusnet with tracert results etc and I even promised to take my router into work and try it on the backup adsl line but ran out of time - thought the tech supporting my question latched onto this and gave me all the settings for it again.
NOTHING HAD Changed on my network or my telepnone line - I just wanted some point to point diagnostic to say my end was ok! I'm only 1000ft from the green box after all.
Anyway I left a  neighbour connected to the network to see if anything got better while I went away for 2 weeks - nothing changed - and have just come back to find Plusnet have had a speed fault -.problem - I'm on thn-ag3 and it seems to be back to normal
This is just my experience I would like to feed back to plusnet.
I was effectively in a poor connection state for a week before I went on holiday and this after about 6 months with no problems. When nothing has changed and one has eliminated all the faults one can only expect it to be at the isp or local loop. Some easier segemented testing might help isolate the problems for us. I wonder of my problem will come back once I'm back on tng-ag2 again
I have included all the interaction and you can read my frustration in my responses.

Your comment  8:22pm, Thursday 14th June 2007
Broadband Fault Checker - Initial checks [ Completed ]
All initial checks have been completed without finding any problems. Detailed checks must now be completed. Please ensure that all questions are completed within 48 hours, otherwise this Question will be automatically closed with no fault reported
Your comment 10:56pm, Thursday 14th June 2007
Broadband Fault Checker - Detailed checks [ Completed ]
All questions have been completed by the user.
Your comment 10:58pm, Thursday 14th June 2007
The customer has provided the following contact details for the duration of the fault.
Daytime telephone number: xxxxxx
Evening telephone number: xxxxxx
Email address: xxxxxx@xxxxxx.plus.net
Additional contact info: all day and evening
Your comment 10:58pm, Thursday 14th June 2007
Broadband Fault Checker - Connection checks [ In progress ]
The tests on your broadband connection have now started. Please check this Question in about 2 minutes to see the results of the tests.
Script User Unused - ADC - Developers 10:58pm, Thursday 14th June 2007
Plus.net Heavy FRIACO dialup (0808 xxxxx) component added to account
Script User Unused - ADC - Developers 10:58pm, Thursday 14th June 2007
Broadband Fault Checker - Connection checks [ Completed ]
All diagnostic checks have now finished.
Script User Unused - ADC - Developers 10:59pm, Thursday 14th June 2007
Your support request has been escalated to the correct team for review.
Your comment 11:36pm, Thursday 14th June 2007
In response to a question about the reposrted up and down speed reported by the ADSL router results below
WAN Port Statistics:
Link Status: Up
Upstream Speed: 640 kbps
Downstream Speed: 8158 kbps
Node-Link
No physical changes have been made to the router or wiring.
The speed has gone unusably slow again (see oct 2006)
Was it the rain?
this is the only thing I can think of
Your comment 11:40pm, Thursday 14th June 2007
Still timeout on ping responses.
Speed test about 100k
please Currently swapped my dsl504 for a new
zyxel ADSL 2+ to see if it is that.
here is the model
System Name:
ZyNOS F/W Version: V3.40(ACI.6)| 04/27/2006
DSL FW Version:DMT FwVer: 3.4.1.0_A_TC, HwVer: T14F7_0.0
Standard:ADSL2
still no luck. very slow.
Your comment 11:45pm, Thursday 14th June 2007
Prev tracert and ping responses - latest at the bottom

8.40
Dead until tried again
Router logs in and DSL light constant
sporadic web pages loading - speedtest.net one minute 1.5meg next minute page timeout.
All was well before 14th June then today incredibly unusably solow
tracerout below

About 9.30pm Below

1 1 ms 1 ms 1 ms 192.xxxxxx.0.1
2 * 42 ms 40 ms lo0.plusnet.thn-ag2.plus.net [195.166.128.93]
3 * 41 ms 42 ms 84.92.4.161
4 88 ms 56 ms 52 ms ge1-0-0-23.ptn-gw1.plus.net [212.159.4.17]
5 * * * Request timed out.
6 61 ms 57 ms 63 ms rt0.thdo.bbc.co.uk [212.58.239.25]
7 70 ms * * 212.58.238.149
8 * * * Request timed out.
9 51 ms 54 ms 53 ms www7.rbsov.bbc.co.uk [212.58.227.77]

1 hour turned off router
22.43 onwards below
C:\Documents and Settings\Administrator>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.251.202]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.xxxxxx.0.1
2 29 ms 29 ms 31 ms lo0.plusnet.thn-ag2.plus.net [195.166.128.93]
3 28 ms 27 ms 28 ms vl603.thn-gw2.plus.net [84.92.4.162]
4 27 ms 28 ms * ge1-0-0-23.ptn-gw1.plus.net [212.159.4.17]
5 * 27 ms 28 ms gi1-1-22.ptn-gw5.plus.net [212.159.4.6]
6 28 ms 27 ms 28 ms rt0.thdo.bbc.co.uk [212.58.239.25]
7 28 ms 28 ms 27 ms 212.58.238.149
8 27 ms 28 ms 26 ms 212.58.239.62
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 *

ping response below
at 2253 thurs 14th June
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Request timed out.
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Reply from 212.58.224.116: bytes=32 time=30ms TTL=248
Reply from 212.58.224.116: bytes=32 time=25ms TTL=248
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Request timed out.
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Request timed out.
Request timed out.
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Request timed out.
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Reply from 212.58.224.116: bytes=32 time=28ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TTL=248
Request timed out.
Reply from 212.58.224.116: bytes=32 time=26ms TTL=248
Reply from 212.58.224.116: bytes=32 time=27ms TT
C:\Documents and Settings\Administrator>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.251.201]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.xxxxxx.0.1
2 29 ms 28 ms 29 ms lo0.plusnet.thn-ag2.plus.net [195.166.128.93]
3 28 ms 26 ms 25 ms vl603.thn-gw1.plus.net [84.92.4.161]
4 27 ms 27 ms 26 ms ge0-0-0-22.ptn-gw1.plus.net [212.159.4.1]
5 27 ms 27 ms 27 ms gi1-1-22.ptn-gw5.plus.net [212.159.4.6]
6 27 ms 28 ms 27 ms rt0.thdo.bbc.co.uk [212.58.239.25]
7 28 ms 27 ms 27 ms 212.58.238.149
8 28 ms 27 ms 27 ms 212.58.239.62
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * *
Your comment 6:41am, Friday 15th June 2007
FRIDAY MORNING
After leaving both of my modem/routers dsl504 (now my secondary) and my zyxel prestige600 disconnected.
The problem is the same . ping to bbc.co.uk works with good times then just stops.
Web browsing is the same.
STRANGE thing is, the dsl504 previously a great and reliable backup now says LCP No Response and doesn't even get as far as the zyxel does.
We are heavily reliant on this on a daily basis and I have to go away on Monday and my partner relying on this who has a great need to be connected. can you please help sort this out for us.
please call my mobile if necessary 07702 xxx xxxxxx
Thank
You
Your comment 7:13am, Friday 15th June 2007
Here is a what I found on the web with a similar "LCP Disconnect PRoblem - the blog is between the ****'s
This fault occurred out of the blue on a previously 7M connection. Can you escalate this to BT to check the line as soon as possible for us? I am ging to check my DSL504 at work today - if it works then it must be a line fault here.
LCP - Diconnect blog below......
***********************************************************
Just trying to set up a new ADSL connection for a mate using a Dlink DSL300G+ modem.
All settings are correct - same ISP as me. The modem reports the following error "LCP No Response". I now know that LCP is the Link Configuration Protocol.
Anyone got any ideas? The ISPs tech line is not manned on a Sunday.
LCP no response generally means that the ADSL device couldn't
get any response back from the router in the exchange.
Does the ADSL device show any signs of carrier detect? If not,
it may well be that BT haven't got it right yet.
If you can see the DSLAM's signal ok, but still get no LCP response
then it suggests either the ADSL device is faulty or there's a
problem with the exchange.
.............................
Sounds like something's chewing the ADSL signal somewhere, probably from the ADSL router upstream given that it can get as far as connecting.
Best thing you can probably try is removing the front plate from the
master socket (which should disconnect all the extensions if it's
wired properly!), and plugging the ADSL modem in on it's own.
..................................
A guy called round from the telecom firm and sure enough it was
a problem at their end - something not configured correctly.
*************************************************************
Your comment 8:04am, Friday 15th June 2007
Please find my Zyxel Router log below with the disconnects.
Please help, this is a genuine problem
No changes to my lan have been made or the phone line.
You can tell when we have no problems as we don't log calls unless there is a genuine isse.
There is one now -= please escalate this.
Thank you in advance for your help.
xxxx xxxxxx and xxxxxx

06/15/2007 07:50:37 WEB Login Successfully User:admin
2 06/15/2007 07:46:51 ppp:IPCP Opening
3 06/15/2007 07:46:51 ppp:IPCP Starting
4 06/15/2007 07:46:51 ppp:CHAP Opening
5 06/15/2007 07:46:51 ppp:LCP Opening
6 06/15/2007 07:46:51 ppp:LCP Starting
7 06/15/2007 07:46:51 ppp:LCP Closing
8 06/15/2007 07:46:51 ppp:LCP Opening
9 06/15/2007 07:46:51 ppp:LCP Starting
10 06/15/2007 07:46:51 ppp:LCP Closing
11 06/15/2007 07:46:50 ppp:LCP Opening
12 06/15/2007 07:46:44 ppp:LCP Starting
13 06/15/2007 07:46:44 board 0 line 0 channel 0, call 9, C02 OutCall Connected 512000 CALL DETAIL RECORD
14 06/15/2007 07:46:44 Packet Trigger: Protocol=1, Data=Packet Trigger: Protocol=1, Dat PACKET TRIGGER
15 06/15/2007 07:46:44 board 0 line 0 channel 0, call 9, C01 Outgoing Call dev=5 ch=0 CALL DETAIL RECORD
16 06/15/2007 07:46:43 board 0 line 0 channel 0, call 8, C02 Call Terminated CALL DETAIL RECORD
17 06/15/2007 07:45:43 ppp:LCP Starting
18 06/15/2007 07:45:43 board 0 line 0 channel 0, call 8, C02 OutCall Connected 512000 CALL DETAIL RECORD
19 06/15/2007 07:45:43 Packet Trigger: Protocol=1, Data=Packet Trigger: Protocol=1, Dat PACKET TRIGGER
20 06/15/2007 07:45:43 board 0 line 0 channel 0, call 8, C01 Outgoing Call dev=5 ch=0 CALL DETAIL RECORD
Stephen Macdonald CSC Analyst 12:47am, Saturday 16th June 2007
Can you please check this customer account as its showing incorrect username or password.
Regards,
Stephen Macdonald
To administer your account and for all your help and support requirements visit http://portal.plus.net/index_nlp.html
Alex Tame CSC - TC Faults 3:22pm, Saturday 16th June 2007
Dear Ms xxxxxx,
Thanks for your contact, we have recieved your fault ticket however it appears that while testing you may have entered your password incorrectly as logs show you not currently online and disconnected. Please let us know when you have reconnected and we will look into the speed issue for you.
Regards,
Alex Tame
To administer your account and for all your help and support requirements visit http://portal.plus.net/index_nlp.html
The customer was notified of this update via SMS.
Your comment 7:11pm, Saturday 16th June 2007
Srange because it was true there was a password incorrect but that was on Thursday ans we have been logged on Through Friday and Today Saturday. Ireceived your message about incorrect password today at about 14:22.
We are connected but there are still timeout problems pinging but speed is up to 6.5mb when there is connection
Martin Cundell CSC Analyst 8:36pm, Saturday 16th June 2007
Dear Ms xxxxxx,
I can see that you are connected currently and a traceroute to your static IP address doesn't currently indicate any problems.
Tracing route to xxxxxx.plus.com [80.229.0.145]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 84.93.219.254.plusnet.pth-ag2.dyn.plus.net [84.9
3.219.254]
2 <1 ms <1 ms <1 ms fa0-5-6.fhw-cr01.plus.net [84.93.207.253]
3 6 ms 6 ms 6 ms at0-3-0.pte-gw1.plus.net [212.159.1.90]
4 6 ms 6 ms 6 ms vl22.thn-gw1.plus.net [212.159.4.3]
5 7 ms 7 ms 9 ms gi11-0-0-603.thn-ag2.plus.net [84.92.4.163]
6 33 ms 33 ms 34 ms xxxxxx.plus.com [80.229.0.145]
Trace complete.

Did you manage to test the router at work as you suggested earlier ?
If you haven't already tried I would perform a full factory reset of your router and then reconfigure it using the following settings:
Virtual Circuit Identifier (VCI) - 38
Virtual Path Identifier (VPI) - 0
Encapsulation Mode - VC Multiplexed (VCMux)
Authentication Type -CHAP
Protocol - RFC 2364: PPP over ATM (PPPoA)
Modulation Type - G.DMT or Auto
After the reset you should check the router manufacturers website to ensure you are using the latest firmware version.
When testing ensure your equipment is set up as follows as this will eliminate any internal wiring or cabling as been the cause of the intermittent problems you are seeing :
Connect the modem/router directly to the master socket (no use of extension cables) and ensure all other non broadband devices are disconnected from the line (phones, fax machines, Sky TV, alarm systems). Also try swapping the one filter used at that stage.