Can't use ADSL2+ :-(

lozcart · Dec 04, 2012, 21:58:10

Your sync will only get better when your target noise margin drops and the only way to get the margin to drop is a stable line. So best to leave your set up now untouched for a few days and see what happens. If you can set up a TBQM then if will help to identify any drops in sync.

Steve · Dec 04, 2012, 22:10:10

If you've no extensions on the front plate you could leave it off and just use one filter from the test socket for both phone and modem

RCS2K4 · Dec 04, 2012, 22:12:12

Hopefully it bumps up, but I will probably move this to LLU as soon as...? In the meantime, i've set up one of these:

Broadband Quality Monitor

Steve · Dec 04, 2012, 22:19:05

Having looked have you allowed your router to respond to ping on the wan port

RCS2K4 · Dec 04, 2012, 22:27:02

Ahhh, im looking but can't find anything in the settings that allows the WAN port to respond to pings...

Steve · Dec 04, 2012, 22:30:05

Quick google - do you have an advanced security page? Or this http://www.tp-link.com/en/article/?id=122

RCS2K4 · Dec 04, 2012, 22:36:34

Think were good to go - Thanks.

Check that graph again??? The packet loss has stopped...

Steve · Dec 04, 2012, 22:37:41

mervl · Dec 05, 2012, 07:42:43

I may be completely wrong but . . . unless the router is reporting wrongly having reversed the figures isn't the problem likely to be the downstream SNR Margin stuck on BT's max of 18.0 (and your first post shows 0 errors), when it should be 6 or lower on a good line. There seem to be a number of reports of this around the web with your sort of speeds so far below the attainable rate, when people are switched to the 21CN network, and the answer is an SNR reset by the ISP - which most of them seem readily prepared to get done if it gets "stuck" for 3 days, and you say yours has been for over 2 weeks! (EDIT: having seen your disconnect this AM on the TBBQM check the router first though to see if the problem is correcting and the SNR margin ~~rising~~ REDUCING (CORRECTED), when hopefully it will continue over the next couple of days).

Two things: I believe a disconnection by you for a time (at least for over 30 minutes, best perhaps for overnight) might enable to DSLAM to reset - reconnection in daylight can anyway help to ~~raise~~ REDUCE SNR margin a bit but it's marginal, and if there are frequent disconnections might also be best to connect to the test socket (behind the BT faceplate), with phones disconnected, if you can - to rule out anything in your premises causing a problem; and (ideally with nothing else connected) is the Quiet Line Test (no noise) OK - 17070 option 2 I hope (from memory, I've not needed it recently)!!

RCS2K4 · Dec 05, 2012, 07:55:57

Thanks - I've checked the router sync and I have no idea what it's up to now :-( The SnR is 22.5 (how, if BT set it to 18???) and downstream syncrate is a very pathetic 1653 kbps...

I guess this was after it's disconnect this morning, but I had hoped it would go faster, not slower. The router is the only thing pluged into the line, and it's right next to the phone socket - so no internal extention wires etc. I've removed the landline phone completly too and tried out the test socket yesterday night.

But you say the SnR increasing is normal??? This is also affecting my speed massively though - My mobile phone can connect to the internet a lot faster at the moment.

mervl · Dec 05, 2012, 07:59:21

My mistake SNR margin should definitely DECREASE, unless there's a line fault!

EDIT: If you make a lot of disconnections (one or two a day in total should be OK though) the DSLAM can interpret it as instability and raise the margin.

Steve · Dec 05, 2012, 08:15:30

There's a fault somewhere! Regarding margin if the margin rises with the same sync or increased sync the ambient noise affecting the line has fallen. If the margin falls with same sync or reduced sync the ambient noise has risen. What we'd like to see is a margin reduction with a corresponding rise in sync.

BT could cap the max sync of adsl2+ lines that where unstable which results in a high margin and a low sync.

My suggestion is use the test socket with filter and ask if IDNet can get the line reset.

RCS2K4 · Dec 05, 2012, 08:32:50

I'm agreed on the fault - It died again just now for no reason and it's sync rate is barely 1172.

It's getting lower.

It has been 2 weeks though, and so far i've seen very little done to fix this despite my insane level of complaining to IDNet...

mervl · Dec 05, 2012, 09:32:29

I can't recall whether you've yet tried the Quiet Line test - preferably with a corded phone if nec beg or borrow one, and if poss when router is disconnected. Any noise you can report to phone service supplier, not IDNet as ISP and DON'T mention broadband. In this weather (cold, snowy and damp) faults may show up more than usually.

andrue · Dec 05, 2012, 10:20:16

It's also worth noting that since this sounds like a line fault switching providers might not help. Even switching to LLU would still use the same line. There's a possibility it could be a card fault at the exchange though. IDNet could ask BT to do a 'lift and shift' to test that theory but you first have to persuade IDNet that there's a problem.

pctech · Dec 05, 2012, 12:21:18

I'd just ring and ask for your MAC as you are unhappy with the help you've been provided with.

Personally I've found O2 Wholesale's (through a different ISP) approach to DLM better on my long line.

Glenn · Dec 05, 2012, 12:49:19

I've had a chat with support on RCS2K4's behalf. BT haven't closed the order off yet, it's due to be closed tomorrow. Once that is done, they can do line checks etc and escalate the case to BT.

RCS2K4 · Dec 05, 2012, 13:38:27

Quote from: Glenn on Dec 05, 2012, 12:49:19
I've had a chat with support on RCS2K4's behalf. BT haven't closed the order off yet, it's due to be closed tomorrow. Once that is done, they can do line checks etc and escalate the case to BT.

Yes, this is a little frustrating. Closing the phoneline order 17 days after it was installed, but don't even get me started with Openreach!!! IDNet can't do an awful lot until Friday and I don't blame them. Their support is like it always has been if you don;t end up at their overflow and out of hours call centre. Oh well, we will enter a further weeks worth of testing, or wait the 7 days for a switch to LLU then? I'm at work though looking at the "sea of red" on my TBBQM and am curious as to whats happened since I left the house since this morning...

RCS2K4 · Dec 17, 2012, 17:23:43

So - We've gone full circle. I can safely now say "I Told you so BT" etc etc etc... IDNET moved us to LLU after countless BT checks and SnR resets not helping the situation.

Now lookie:

BT's 21CN round here is really, really messed up...

Glenn · Dec 17, 2012, 17:24:47

It's a good result, thanks for the update

Steve · Dec 17, 2012, 17:28:32

We'll keep our fingers crossed it stays that way!

RCS2K4 · Dec 17, 2012, 17:39:21

Thanks guys - I have every bit of confidence this will hold up. Within minutes the BT connection speed would always fluctuate, and there were a lot (30,000+) CRC errors on the downstream within hours. This has been up since about 12:30 according to router logs. Zero fluctuation, no errors at all - And this is with interleaving OFF (BIG yayyyyyyyyyyyyy for low latency!!!!).

I'll never know where the actual source of the problem lies, but this happened twice with separate lines connected to this exchange. Big clue right there I guess, but BT say's it's healthy...

Steve · Dec 17, 2012, 18:18:27

Well the only difference is that you've gone from BT's exchange equipment to Be*'s , the line between you and the exchange remains the same.

andrue · Dec 18, 2012, 13:46:40

At a guess I'd say your original line card was duff. If IDNet had got BT to do a lift and shift it'd probably have fixed it as well. Anyway Be's network should offer slightly more speed by virtue of not having a profile so it's all good.

Steve · Dec 18, 2012, 18:15:12

I agree the lift and shift has proved the point.