Thomson BEbox permanently "contacting DHCP server"

I was apparently migrated from BE to Sky on 23rd Jan. For a while, the next day, the "internet" light was out on the BEbox but I was still connected to net. I restarted the box and the light came back on. But logging into the Thomson TG585 v7, the "Internet" section always has red cross on it, and permanently says "contacting DHCP server". I seem to be accessing the net ok, albeit with slightly slower download speed and more than slightly slower upload speed than with BE. I phoned the Sky support number BE gave me, and the guy just said if I'm on the net, then there's no problem.

I also told him i have this in 2 days: FEC Errors (Up/Down): 1 / 6,319,606

..he said something about 'line shaping'(?) going on and causing that.

Is he right that I have no issues?

Need to post the full set of stats for connection speeds, attenuation and noise margins along with the errors and the uptime of the connection.

FEC Errors are errors that interleaving has corrected. Did you have these before?

In short interleaving is doing its job, but if you could tidy up wiring and reduce the number of errors you might get a better performing line.

In reply to a post by Chocolate_cake:

I phoned the Sky support number BE gave me, and the guy just said if I'm on the net, then there's no problem.

Pretty much correct - the old BE box is working with the Sky service, but Sky haven't provided new firmware (it would cost too much) so the screen display is not "nice". It has no functional issue.

The FEC numbers should be similar to those you had on the BE network as the physical wiring to the exchange is the same.

Thanks for the replies, MrSaffron and jchamier

fwiw:
DSL Connection

Uptime:
1 day, 22:47:34

DSL Type:
G.992.5 annex A

Maximum Bandwidth (Up/Down) [kbps/kbps]:
1,000 / 6,940

Bandwidth (Up/Down) [kbps/kbps]:
838 / 5,782

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

Output Power (Up/Down) [dBm]:
10.5 / 1.5

Line Attenuation (Up/Down) [dB]:
27.5 / 46.5

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

Vendor ID (Local/Remote):
TMMB / GSPN

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):
6 / 0

FEC Errors (Up/Down):
1 / 6,344,855

CRC Errors (Up/Down):
1 / 1,949

HEC Errors (Up/Down):
0 / 1,332

I don't remember seeing any number as big as the FEC error before. The box is straight into the main BT socked with nothing else at all connected.

it is possible the FEC was errors induced when the line was switched over.

The CRC is low so not a worry.

See if the FEC clock up at the rate of thousands an hour or not now.

In reply to a post by MrSaffron:

it is possible the FEC was errors induced when the line was switched over.

The CRC is low so not a worry.

See if the FEC clock up at the rate of thousands an hour or not now.

I've just checked and it was ~30,000 FEC errors in 20mins

Edited by deleted (Tue 28-Jan-14 00:09:00)

FEC = Forward Error Correction. They're corrected errors.