Intermittent PPP connection drops --TP-Link TD-W8960N Router

[#1]

Hi
This seems to be every 2 days or so at random times. drops the connection and reconnects a few times then stays connected for another 2 days approx.  The router is not losing sync to the exchange it's just the PPP that's dropping and reconnecting.
The router only keeps a log for 12 hours so it's difficult to pin it down to specific times.  TP-LINK TD-W8960N Wireless router.
This happens when no computers are being used, I have a wireless laptop and a wired desktop.
When checking the log the RS uncorrectable errors  increase a lot and other errors as well, Is the the errors dropping the PPP or is it the PPP dropping thats causing the errors.
System Log
Date/Time Facility Severity Message
May 1 12:51:40 user crit kernel: ADSL G.992 started
May 1 12:51:42 user crit kernel: ADSL G.992 channel analysis
May 1 12:51:46 user crit kernel: ADSL link up, interleaved, us=448, ds=8128
May 1 12:51:55 daemon crit syslog: PPP LCP UP.
May 1 12:51:55 daemon crit syslog: PPP LCP UP.
May 1 12:51:56 daemon crit syslog: Received valid IP address from server. Connection UP.
May 1 12:53:39 user crit kernel: ADSL link down
May 1 12:53:41 daemon crit syslog: Clear IP addresses. Connection DOWN.
May 1 12:53:41 daemon crit syslog: Clear IP addresses. PPP connection DOWN.
May 1 12:53:41 user crit kernel: xDSL G.994 training
May 1 12:53:43 user crit kernel: ADSL G.992 started
May 1 12:53:46 user crit kernel: ADSL G.992 channel analysis
May 1 12:53:50 user crit kernel: ADSL link up, interleaved, us=448, ds=8128
May 1 12:53:58 daemon crit syslog: PPP LCP UP.
May 1 12:53:59 daemon crit syslog: PPP LCP UP.
May 1 12:54:03 daemon crit syslog: Received valid IP address from server. Connection UP.
May 1 12:55:21 user crit kernel: ADSL link down
May 1 12:55:23 user crit kernel: xDSL G.994 training
May 1 12:55:24 daemon crit syslog: Clear IP addresses. Connection DOWN.
May 1 12:55:24 daemon crit syslog: Clear IP addresses. PPP connection DOWN.
May 1 12:55:26 user crit kernel: ADSL G.992 started
May 1 12:55:29 user crit kernel: ADSL G.992 channel analysis
May 1 12:55:33 user crit kernel: ADSL G.992 message exchange
May 1 12:55:33 user crit kernel: ADSL link up, interleaved, us=448, ds=8128
May 1 12:55:41 daemon crit syslog: PPP LCP UP.
May 1 12:55:42 daemon crit syslog: PPP LCP UP.
May 1 12:55:42 daemon crit syslog: Received valid IP address from server. Connection UP.
May 1 12:56:31 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=41.196.216.202 DST=91.125.177.17 LEN=60 TOS=0x00 PREC=0x80 TTL=46 ID=29992 DF PROTO=TCP SPT=4298 DPT=23 WINDOW=5808 RES=0x00 SYN URGP=0
May 1 13:00:52 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=118.67.202.120 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=109 ID=45676 DF PROTO=TCP SPT=1643 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 13:01:44 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=217.114.229.44 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=119 ID=17529 DF PROTO=TCP SPT=2858 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 13:01:47 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=217.114.229.44 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=119 ID=18024 DF PROTO=TCP SPT=2858 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 13:18:13 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=128.68.110.105 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=116 ID=21873 DF PROTO=TCP SPT=4400 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 13:18:16 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=128.68.110.105 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=116 ID=22727 DF PROTO=TCP SPT=4400 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 13:27:55 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=211.117.47.163 DST=91.125.177.17 LEN=52 TOS=0x00 PREC=0x80 TTL=114 ID=17132 DF PROTO=TCP SPT=4951 DPT=8080 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 13:27:58 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=211.117.47.163 DST=91.125.177.17 LEN=52 TOS=0x00 PREC=0x80 TTL=114 ID=17513 DF PROTO=TCP SPT=4951 DPT=8080 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 13:36:56 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=121.245.208.34 DST=91.125.177.17 LEN=60 TOS=0x00 PREC=0x80 TTL=42 ID=19831 DF PROTO=TCP SPT=58500 DPT=23 WINDOW=5840 RES=0x00 SYN URGP=0
May 1 13:47:34 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=41.196.216.202 DST=91.125.177.17 LEN=60 TOS=0x00 PREC=0x80 TTL=46 ID=48402 DF PROTO=TCP SPT=4628 DPT=23 WINDOW=5808 RES=0x00 SYN URGP=0
May 1 14:01:51 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=41.196.218.83 DST=91.125.177.17 LEN=60 TOS=0x00 PREC=0x80 TTL=46 ID=20855 DF PROTO=TCP SPT=3263 DPT=23 WINDOW=5808 RES=0x00 SYN URGP=0
May 1 14:20:22 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=115.89.175.28 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=104 ID=52865 DF PROTO=TCP SPT=1069 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 14:20:25 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=115.89.175.28 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=104 ID=53180 DF PROTO=TCP SPT=1069 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 14:32:27 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=41.196.210.167 DST=91.125.177.17 LEN=60 TOS=0x00 PREC=0x80 TTL=46 ID=34207 DF PROTO=TCP SPT=4768 DPT=23 WINDOW=5808 RES=0x00 SYN URGP=0
May 1 14:39:48 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=151.80.64.117 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=118 ID=46107 DF PROTO=TCP SPT=2475 DPT=445 WINDOW=16384 RES=0x00 SYN URGP=0
May 1 14:48:18 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=114.37.31.39 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=110 ID=19413 DF PROTO=TCP SPT=3035 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 15:02:56 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=188.254.237.70 DST=91.125.177.17 LEN=60 TOS=0x00 PREC=0x00 TTL=111 ID=48230 DF PROTO=TCP SPT=2566 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 15:12:51 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=31.211.147.129 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=104 ID=56357 DF PROTO=TCP SPT=1235 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 15:18:11 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=184.106.253.228 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=108 ID=23185 DF PROTO=TCP SPT=1925 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 15:35:55 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=91.214.137.46 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=116 ID=58209 DF PROTO=TCP SPT=54034 DPT=445 WINDOW=16384 RES=0x00 SYN URGP=0
May 1 15:37:52 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=87.241.96.108 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=109 ID=4286 DF PROTO=TCP SPT=4334 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 15:47:23 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=132.100.100.100 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x80 TTL=113 ID=28267 DF PROTO=TCP SPT=1979 DPT=445 WINDOW=16384 RES=0x00 SYN URGP=0
May 1 15:57:07 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=95.67.196.49 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=31445 DF PROTO=TCP SPT=1453 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 16:06:39 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=115.115.129.130 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=111 ID=15036 DF PROTO=TCP SPT=52075 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 16:20:08 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=78.84.234.192 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=115 ID=53683 DF PROTO=TCP SPT=1622 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 16:27:04 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=103.23.33.13 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=106 ID=55396 DF PROTO=TCP SPT=24991 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 16:36:32 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=91.124.114.214 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=114 ID=27120 DF PROTO=TCP SPT=26718 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 16:50:52 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=113.198.167.67 DST=91.125.177.17 LEN=52 TOS=0x00 PREC=0x00 TTL=101 ID=20913 DF PROTO=TCP SPT=6503 DPT=49533 WINDOW=8192 RES=0x00 SYN URGP=0
May 1 16:57:13 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=113.198.167.67 DST=91.125.177.17 LEN=52 TOS=0x00 PREC=0x80 TTL=111 ID=27203 DF PROTO=TCP SPT=7025 DPT=49533 WINDOW=8192 RES=0x00 SYN URGP=0
May 1 17:09:16 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=114.236.160.93 DST=91.125.177.17 LEN=60 TOS=0x00 PREC=0x80 TTL=42 ID=41272 DF PROTO=TCP SPT=39278 DPT=23 WINDOW=5808 RES=0x00 SYN URGP=0
May 1 17:22:27 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=94.101.192.138 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=111 ID=1575 DF PROTO=TCP SPT=2693 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 17:27:47 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=92.253.19.232 DST=91.125.177.17 LEN=52 TOS=0x00 PREC=0x00 TTL=47 ID=39089 DF PROTO=TCP SPT=50751 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 17:41:04 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=79.111.89.248 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x80 TTL=115 ID=38 DF PROTO=TCP SPT=1350 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 17:46:38 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=129.9.200.12 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=105 ID=50219 DF PROTO=TCP SPT=3437 DPT=445 WINDOW=64000 RES=0x00 SYN URGP=0
May 1 17:56:59 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=187.56.82.220 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=29521 DF PROTO=TCP SPT=4833 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 18:09:21 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=177.125.187.252 DST=91.125.177.17 LEN=60 TOS=0x00 PREC=0x80 TTL=35 ID=18090 DF PROTO=TCP SPT=3045 DPT=80 WINDOW=5760 RES=0x00 SYN URGP=0
May 1 18:18:43 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=201.27.113.197 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=35712 DF PROTO=TCP SPT=3770 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 18:32:57 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=128.74.138.84 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=118 ID=17380 DF PROTO=TCP SPT=3505 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 18:37:31 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=217.24.71.132 DST=91.125.177.17 LEN=52 TOS=0x00 PREC=0x00 TTL=113 ID=13302 DF PROTO=TCP SPT=25881 DPT=445 WINDOW=47916 RES=0x00 SYN URGP=0
May 1 18:46:34 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=97.66.211.189 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x80 TTL=110 ID=33350 DF PROTO=TCP SPT=2348 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 19:01:02 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=84.54.121.119 DST=91.125.177.17 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=63160 DF PROTO=TCP SPT=3662 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
May 1 19:08:26 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=94.23.203.100 DST=91.125.177.17 LEN=60 TOS=0x00 PREC=0x80 TTL=55 ID=51902 DF PROTO=TCP SPT=37906 DPT=23 WINDOW=14600 RES=0x00 SYN URGP=0
May 1 19:16:36 user crit kernel: eth0 Link UP.
May 1 19:17:20 user crit kernel: eth0 Link DOWN.
May 1 19:17:22 user crit kernel: eth0 Link UP.
May 1 19:19:06 user alert kernel: Intrusion -> IN=pppoa0 OUT= MAC= SRC=91.117.149.79 DST=91.125.177.17 LEN=60 TOS=0x00 PREC=0x80 TTL=50 ID=53746 DF PROTO=TCP SPT=4902 DPT=23 WINDOW=5840 RES=0x00 SYN URGP=0
This is the log of the last time it happened, it's been stable since 12.55 today.
Is their anybody with more knowledge than me about routers and adsl can tell me what is causing this and maybe how to prevent it

[#2]

I take it you know whether or not you are losing sync with the exchange from the way you've posted, or is that a don't know?

[#3]

Hi
It is not the exchange sync that seems to drop
This is the router info.
Device Info

Firmware Version: 1.3.6 Build 100903 Rel.71418n
Hardware Version: TD-W8960N v1 0x00000001
This information reflects the current status of your DSL connection.
Line Rate - Upstream (Kbps): 448
Line Rate - Downstream (Kbps): 8128
LAN IP Address: 192.168.1.1
Default Gateway: 195.166.130.60(pppoa0)
Primary DNS Server: 156.154.70.1
Secondary DNS Server: 208.67.220.220
System Running time: 3 day(s) 01:21:04
Date/Time: Tue May 1 20:40:56 2012

[#4]

I think there's a couple of posters on this board that know about the TP-LINK TD-W8960N but I'm afraid I'm not one. It might be an idea to edit the title and add "TP-LINK TD-W8960N" which should then get the right attention, but maybe not until tomorrow if they aren't around.

[#5]

Thanks, i have edited the title and will wait and see if anybody who uses this router can help

[#6]

I also don't know the router in question to please take the next comments with that in mind and anyone please feel free to tell me I'm wrong.
To me when the router's logs say 'Channel analysis' that sounds like the unit IS loosing sync with the exchange equipment (the DSLAM) and this is the notification that the router is
running up and down the ADSL frequency channels looking at the various SNR's (and doing lots else besides) before agreeing with the DSLAM on a suitable sync speed and
sorting out the bit loadings per channel.
IF this is so, and it's clearly connecting at the same speed so it's not noise which as appeared as the sync would be lower.
Possibly you are seeing some short term noise spike which wipes out the ADSL signal so it does a re-connection, but by the time it starts the process the noise spike has gone:  ?causes?
Possibly also the line is about to fail totally.
Next
The router seems to being assaulted from a variety of sources all of which its blocking, the address from which the enquiry is being sent is listed (SRC=) and the "out" is blank signifying its being blocked.  DST - the destination is your own IP address - curious.

[#7]

Yep, from the log fragment the DSL dropped twice:
May 1 12:53:39    user    crit    kernel: ADSL link down
May 1 12:55:21    user    crit    kernel: ADSL link down
and probably at 12:51 too, as the first entries also relate to a restarted DSL link.
If your log has time limited entries you could always setup a syslog and use the remote log function in the router. Theres a free one here:
http://www.snmpsoft.com/downloads.html
Obviously your PC must be left on for it to log all the entries.

[#8]

Yes. I have to agree, it is losing sync. At first, I just glanced and thought don't know anything about that modem/router and didn't look in more detail, thinking someone else could have a look. Now having seen x47c's post I looked more closely

Quote

May 1 12:55:26    user    crit    kernel: ADSL G.992 started May 1 12:55:29    user    crit    kernel: ADSL G.992 channel analysis May 1 12:55:33    user    crit    kernel: ADSL G.992 message exchange May 1 12:55:33    user    crit    kernel: ADSL link up, interleaved, us=448, ds=8128

This repeats.
As you are losing sync, I wouldn't bother with those logs for the moment, I'd get monitoring with something like Routerstats, but again modem/router and Computer have to be on.

[#9]

Just a thought, if the router was losing sync at the exchange, when it reboots would the System Running Time still be showing as over 3 days and not start again at zero.
The last time i rebooted it before this it was showing as being up for over 8 days. If it was repeatedly losing sync would the sync rate not drop from 8128.
As i say just a thought, don't have enough knowledge about routers and broadband to know.
I think the router keeps a log for 24 hours not 12 so will try to check it more often.

[#10]

A reboot and a resync are different (as would be a factory reset different). A reboot resets all the statistics and clock (generally) whereas a resync may clear some stats but the LIne count will increment, the System Time & Line up time won't be reset, but the On-line time may be.
If you get too many re-syncs in a short time the noise margin may get raised but if you are close enough to the exchange the sync speed doesn't go down. Can't tell what's happening without seeing the modem/routers ADSL line stats - the things like the sync speed, attenuation & Noise Margin (SNRM) etc.

[#11]

Line Stats
Statistics -- xDSL

Mode: ADSL_G.dmt
Traffic Type: ATM
Status: Up
Link Power State: L0

Downstream Upstream
Line Coding(Trellis): On On
SNR Margin (0.1 dB): 89 220
Attenuation (0.1 dB): 290 105
Output Power (0.1 dBm): 198 121
Attainable Rate (Kbps): 9664 1136

Path 0 Path 1
Downstream Upstream Downstream Upstream
Rate (Kbps): 8128 448 0 0

K (number of bytes in DMT frame): 255 15 0 0
R (number of check bytes in RS code word): 20 16 0 0
S (RS code word size in DMT frame): 1.00 8.00 0.0 0.0
D (interleaver depth): 64 4 0 0
Delay (msec): 16.00 8.00 0.0 0.0
INP (DMT symbol): 2.33 0.13 0.0 0.0

Super Frames: 1458598 2265556 0 0
Super Frame Errors: 0 0 0 0
RS Words: 198369328 19256223 0 0
RS Correctable Errors: 5948 0 0 0
RS Uncorrectable Errors: 73 0 0 0

HEC Errors: 0 2 0 0
OCD Errors: 0 0 0 0
LCD Errors: 0 0 0 0
Total Cells: 738346793 0 0 0
Data Cells: 944517 0 0 0
Bit Errors: 0 0 0 0

Total ES: 3043 0
Total SES: 2018 0
Total UAS: 1156 1156

[#12]

It's a shame that page doesn't show the Line-up and System up times, always useful when looking at error counts.
It looks as though the Super Frame (CRC) errors get reset at a resync (not uncommon) along with some of the others. Totals & RS data don't usually reset on resync.
You're just about close enough to the exchange to almost certainly resync at 8128 IF you don't get too many drops.
I'd start trying to look for possible causes of the drops. Not getting mains dips are you, possibly disturbing the lead into the filter and socket etc.
It's not happening when you use the phone is it? Can you hear any crackling noises on the line when using the phone?
Have you altered anything lately. I assume the filter is plugged straight into a socket and the modem/router straight into the filter with a short lead
- no extension cables?

[#13]

Hi
No mains dips as far as i know, not happening when the phone is used, phone line silent on BT 17070 test. The only thing different is a SKY+ HD box has been installed recently, but their is no phone line connected to it yet. This is probably a silly question but would this affect the phone line? I know Sky check your box to see if their is a phone line connected to it.
Their is no filter at the socket, as i don't have a phone on this socket.  It's always been like this for years and it has never caused problems before, it's on a short RJ11 to BT cable, no extension cable.
Would a filter on this socket help even if their is no telephone connected to it?  The RS uncorrectable errors increase into the thousands when the line is dropping and reconnecting. It has been stable now for 24 hrs no drops.
Statistics -- xDSL

Mode: ADSL_G.dmt
Traffic Type: ATM
Status: Up
Link Power State: L0

Downstream Upstream
Line Coding(Trellis): On On
SNR Margin (0.1 dB): 93 220
Attenuation (0.1 dB): 290 105
Output Power (0.1 dBm): 198 121
Attainable Rate (Kbps): 9664 1136

Path 0 Path 1
Downstream Upstream Downstream Upstream
Rate (Kbps): 8128 448 0 0

K (number of bytes in DMT frame): 255 15 0 0
R (number of check bytes in RS code word): 20 16 0 0
S (RS code word size in DMT frame): 1.00 8.00 0.0 0.0
D (interleaver depth): 64 4 0 0
Delay (msec): 16.00 8.00 0.0 0.0
INP (DMT symbol): 2.33 0.13 0.0 0.0

Super Frames: 4273724 5080500 0 0
Super Frame Errors: 0 0 0 0
RS Words: 581226464 43184250 0 0
RS Correctable Errors: 7271 0 0 0
RS Uncorrectable Errors: 73 0 0 0

HEC Errors: 0 2 0 0
OCD Errors: 0 0 0 0
LCD Errors: 0 0 0 0
Total Cells: 1655759176 0 0 0
Data Cells: 1058170 0 0 0
Bit Errors: 0 0 0 0

Total ES: 3043 0
Total SES: 2018 0
Total UAS: 11
Thanks for your help.
 

[#14]

Hi Fifer,
on the 28th there were lots of resyncs between about 11am and 4.30pm and on the 29th between 2am and about 8.30am but none since then. Quick resyncs can pick up the same session so it's not always picked up.
As for the sky connection, as with anything connected to your internal phone network there should always be filters attached.
Jojo

[#15]

Hi Joanne,
Thanks for the information on the resyncs, I will put a filter on the phone socket and see if this helps.  As i said their is no phone connection to the Sky box but i will try a filter and see if it makes any difference.