HEC Errors upon re-sync

[#1]

I have noticed that when my Thomson TG585v7 re-syncs I immediately get a large amount or HEC errors on the upstream side of things.
The data here shows that in the 12 seconds since syncing and I have already had 32,589 errors. Doesn't that seem high. I use my connection purely for gaming so slightly concerned that my upstream connection might be suffering from something.
Router data
DSL Connection
Link Information


Uptime: 0 days, 0:00:12

DSL Type: G.992.5 annex A

Bandwidth (Up/Down) [kbps/kbps]: 872 / 8,602

Data Transferred (Sent/Received) [kB/kB]: 0.00 / 0.00

Output Power (Up/Down) [dBm]: 12.0 / 20.5

Line Attenuation (Up/Down) [dB]: 18.5 / 34.0

SN Margin (Up/Down) [dB]: 6.0 / 9.5

Vendor ID (Local/Remote): TMMB / TSTC

Loss of Framing (Local/Remote): 0 / 0

Loss of Signal (Local/Remote): 0 / 0

Loss of Power (Local/Remote): 0 / 0

Loss of Link (Remote): 0

Error Seconds (Local/Remote): 0 / 0

FEC Errors (Up/Down): 0 / 0

CRC Errors (Up/Down): 0 / 0

HEC Errors (Up/Down): 32,589 / 0

What could be the problem?

[#2]

Hi there, are these affecting your use in any way?
Jojo

[#3]

As a gamer I am trying to mitigate the lag I am suffereing when gaming online. Not sure why I should have so many errors when syncing with the network.
My pings aren't currently any good either usually I have a ping of about 14m/s. Could you check to see if I have lost my fastpath flag ?

C:\Documents and Settings\HP_Owner>ping www.bbc.co.uk
Pinging www.bbc.net.UK [212.58.246.158] with 32 bytes of data:
Reply from 212.58.246.158: bytes=32 time=80ms TTL=55
Reply from 212.58.246.158: bytes=32 time=66ms TTL=55
Reply from 212.58.246.158: bytes=32 time=61ms TTL=55
Reply from 212.58.246.158: bytes=32 time=87ms TTL=55
Ping statistics for 212.58.246.158:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 61ms, Maximum = 87ms, Average = 73ms
C:\Documents and Settings\HP_Owner>tracert www.bbc.co.uk
Tracing route to www.bbc.net.UK [212.58.246.158]
over a maximum of 30 hops:
  1    57 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
  2    87 ms    86 ms    91 ms  lo0-central1.pcl-ag04.plus.net [195.166.128.241]
  3    88 ms    88 ms    87 ms  gi1-10-411.pcl-gw01.plus.net [84.92.6.224]
  4    91 ms    92 ms    95 ms  te2-1.pcl-gw02.plus.net [212.159.1.114]
  5    99 ms  101 ms    96 ms  te2-2.thn-gw2.plus.net [212.159.0.190]
  6    83 ms    82 ms    87 ms  rt0.thdo.bbc.co.uk [212.58.239.25]
  7    84 ms    86 ms    79 ms  212.58.238.133
  8    97 ms    97 ms  102 ms  te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
  9    97 ms    99 ms    91 ms  212.58.255.12
10    79 ms    74 ms    73 ms  fmt-vip01.cwwtf.bbc.co.uk [212.58.246.158]
Trace complete.
C:\Documents and Settings\HP_Owner>

[#4]

Hi Danplusnet,
If you try reconnecting to a different gateway, making sure you have no data transferring at the time and run it again, that would be useful.
As for your interleaving, it is not currently on but the status is set to auto so this means that it can be applied if necessary.
Jojo

[#5]

Hi
To connect to a different gateway do I just re-boot by powering down  the router or is there another way?

[#6]

you can just go to disconnect/reconnect in the router console, that'll do just as well
Jojo

[#7]

I tried your way but the router GUI locked up so I had to manually reboot anyway. No improvements but have sync at a lower rate too now
Still showing 33,034 HEC errors with noting else connected to the router whilst syncing.
Link Information
Uptime: 0 days, 0:01:58
DSL Type: G.992.5 annex A
Bandwidth (Up/Down) [kbps/kbps]: 880 / 8,335
Data Transferred (Sent/Received) [kB/kB]: 0.00 / 0.00
Output Power (Up/Down) [dBm]: 12.0 / 20.5
Line Attenuation (Up/Down) [dB]: 18.5 / 34.0
SN Margin (Up/Down) [dB]: 6.0 / 10.0
Vendor ID (Local/Remote): TMMB / TSTC
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): 0
Error Seconds (Local/Remote): 0 / 0
FEC Errors (Up/Down): 1 / 0
CRC Errors (Up/Down): 1 / 1
HEC Errors (Up/Down): 33,034 / 1
Ping and tracert still not good.
C:\Documents and Settings\HP_Owner>ping www.bbc.co.uk
Pinging www.bbc.net.uk [212.58.246.161] with 32 bytes of data:
Reply from 212.58.246.161: bytes=32 time=116ms TTL=56
Reply from 212.58.246.161: bytes=32 time=93ms TTL=56
Reply from 212.58.246.161: bytes=32 time=87ms TTL=56
Reply from 212.58.246.161: bytes=32 time=86ms TTL=56
Ping statistics for 212.58.246.161:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 86ms, Maximum = 116ms, Average = 95ms
C:\Documents and Settings\HP_Owner>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.246.161]
over a maximum of 30 hops:
 1     6 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
 2    80 ms    82 ms    80 ms  lo0-central2.thn-ag2.plus.net [195.166.128.230]
 3    76 ms    75 ms    82 ms  gi1-14-221.thn-gw1.plus.net [84.92.6.200]
 4   102 ms   102 ms    99 ms  te2-3.thn-gw2.plus.net [212.159.1.58]
 5   103 ms   108 ms   111 ms  rt0.thdo.bbc.co.uk [212.58.239.25]
 6   113 ms   111 ms   112 ms  212.58.238.133
 7   107 ms   102 ms   115 ms  te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
 8   113 ms   117 ms   119 ms  212.58.255.12
 9   122 ms   110 ms   107 ms  fmt-vip04.cwwtf.bbc.co.uk [212.58.246.161]
Trace complete.
You mention that interleaving is on auto but I had an order on my account to stay on fastpath so shouldn't this be set to off?

[#8]

Hi Danplusnet,
This needs to be looked at further so I suggest raising a fault through http://faults.plus.net including the stats you have given here and we will check it further. It is important that you make sure that you are not running anything in the background, it may be useful to use a bandwidth monitor to check this before you raise the fault.
As for the interleaving it is off at the moment, the auto is just keeping the option open to put it on if need be. Have you ever used interleaving before, if so how was it? It may turn out you get better performance with it on. It's easy enough for us to turn it off again if you wanted to try it.
Jojo

[#9]

Ive been through three fault checks recently and they always find nothing - pings were fine first thing this morning.

[#10]

I'd suggest the bandwidth monitor, you may unwittingly have something running. There's plenty of capacity at the exchange and there have been no outages.
Jojo

[#11]

There is nothing connected to the router whilst it boots up to cause the HEC errors. I am not a techie so unfortunately have no idea how to run a band width monitor although I am not running anything on the laptop other than the ping test

[#12]

Hi, if you follow this link
http://www.thinkbroadband.com/tbbmeter.html
you can download think broadband's monitor. I doubt you'll have much trouble using it, as although you say you are not a techie, you do seem to know a thing or two!
Jojo

[#13]

I googled it and found one - simple as you siad. Currently says I am using next to no bandwith.

[#14]

Great, if you run your pings while it's like that we can definitely rule that out.
Jojo

[#15]

Ping and tracert still awful whilst bandwidth monitor continued to show next to no usage.
I also quickly upgraded the Thomson software to the latest version 8.2.65 and that has made no difference either.

C:\Documents and Settings\HP_Owner>ping www.bbc.co.uk
Pinging www.bbc.net.uk [212.58.246.159] with 32 bytes of data:
Reply from 212.58.246.159: bytes=32 time=116ms TTL=55
Reply from 212.58.246.159: bytes=32 time=113ms TTL=55
Reply from 212.58.246.159: bytes=32 time=138ms TTL=55
Reply from 212.58.246.159: bytes=32 time=137ms TTL=55
Ping statistics for 212.58.246.159:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 113ms, Maximum = 138ms, Average = 126ms
C:\Documents and Settings\HP_Owner>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.246.159]
over a maximum of 30 hops:
  1    36 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
  2  135 ms  124 ms  118 ms  lo0-central2.pcl-ag04.plus.net [195.166.128.242]
  3  125 ms  121 ms  127 ms  gi1-12-421.pcl-gw01.plus.net [84.92.6.232]
  4  125 ms  127 ms  134 ms  te2-1.pcl-gw02.plus.net [212.159.1.114]
  5  149 ms  218 ms  212 ms  te2-2.thn-gw2.plus.net [212.159.0.190]
  6  139 ms  134 ms  124 ms  rt0.thdo.bbc.co.uk [212.58.239.25]
  7  133 ms  122 ms  117 ms  212.58.238.133
  8  122 ms  111 ms  107 ms  te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
  9  118 ms  107 ms  112 ms  212.58.255.12
10  122 ms  115 ms  121 ms  fmt-vip02.cwwtf.bbc.co.uk [212.58.246.159]
Trace complete.
I noticed last night that my usual BT profile (through the BT Speedtester) had jumped up from 7150kbps to 10000kbps last night but as of this morning it had fallen to 7000kbps. Could they have been messing  around on my line?