|
|
After persevering with Orange I managed to get a stable and good connection ~14Mbps/1.2Mbps. The line has stayed connected for over 30 days without dropping.
Here is a screenshot of my stats after 20 days of uptime:
Over the last few days the connection has been lousy and now i'm down to 2496Kbps and the good old 443Kbps upload 
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
| Status
Configured CurrentLine Status --- SHOWTIME
Link Type --- Fast PathOperation Mode Automatic G992.5(ADSL2+)
Data Rate InformationStream Type Actual Data Rate
Upstream 443 (Kbps.)Downstream 2496 (Kbps.)
Defect/Failure IndicationOperation Data Upstream Downstream
Noise Margin 9.5 dB 6.6 dBLine Attenuation 21.7 dB 34.5 dB
Indicator Name Near End Indicator Far End IndicatorOutput Power 10.1 dBm 0.0 dBm
Fast Path FEC Correction 0 0Interleaved Path FEC Correction NA NA
Fast Path CRC Error 2779 95Interleaved Path CRC Error NA NA
Loss of Signal Defect 3 0Fast Path HEC Error STR 650 25
Interleaved Path HEC Error NA NAError Seconds 4596 5384 |
The logs:
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
2829
3031
3233
3435
3637
3839
4041
4243
4445
4647
4849
5051
5253
5455
5657
5859
6061
6263
6465
6667
6869
7071
7273
7475
7677
7879
8081
8283
8485
8687
8889
9091
| Sat Jun 8 00:54:51 2013 admin login success from 192.168.1.102
Fri Jun 7 23:24:21 2013 PPP connection up (VC1)Fri Jun 7 23:24:19 2013 PPP: IPCP up
Fri Jun 7 23:24:19 2013 PPP: IPCP received CONFACKFri Jun 7 23:24:19 2013 PPP: IPCP sending CONFREQ
Fri Jun 7 23:24:18 2013 PPP: IPCP received CONFNAKFri Jun 7 23:24:18 2013 PPP: IPCP sending CONFREQ
Fri Jun 7 23:24:18 2013 PPP: IPCP received CONFREJFri Jun 7 23:24:18 2013 PPP: IPCP sending CONFACK
Fri Jun 7 23:24:18 2013 PPP: IPCP received CONFREQFri Jun 7 23:24:18 2013 PPP: IPCP sending CONFREQ
Fri Jun 7 23:24:18 2013 PPP: CHAP authentication succeededFri Jun 7 23:24:18 2013 PPP: LCP up
Fri Jun 7 23:24:18 2013 PPP: LCP received CONFACKFri Jun 7 23:24:18 2013 PPP: LCP sending CONFACK
Fri Jun 7 23:24:18 2013 PPP: LCP received CONFREQFri Jun 7 23:24:17 2013 PPP: LCP sending CONFREQ
Fri Jun 7 23:24:17 2013 PPP: Starting daemonFri Jun 7 23:24:13 2013 WAN link up (ADSL)
Fri Jun 7 23:23:29 2013 PPP: Stopped daemon(0,1,5)Fri Jun 7 23:23:29 2013 PPP connection down (VC1)
Fri Jun 7 23:23:29 2013 PPP: LCP sending TERMREQFri Jun 7 23:23:29 2013 PPP: IPCP down
Fri Jun 7 23:23:29 2013 PPP: LCP downFri Jun 7 23:23:29 2013 WAN link down (ADSL)
Thu Jun 6 17:24:29 2013 PPP connection up (VC1)Thu Jun 6 17:24:26 2013 PPP: IPCP up
Thu Jun 6 17:24:26 2013 PPP: IPCP received CONFACKThu Jun 6 17:24:26 2013 PPP: IPCP sending CONFREQ
Thu Jun 6 17:24:26 2013 PPP: IPCP received CONFNAKThu Jun 6 17:24:26 2013 PPP: IPCP sending CONFREQ
Thu Jun 6 17:24:26 2013 PPP: IPCP received CONFREJThu Jun 6 17:24:26 2013 PPP: IPCP sending CONFACK
Thu Jun 6 17:24:26 2013 PPP: IPCP received CONFREQThu Jun 6 17:24:26 2013 PPP: IPCP sending CONFREQ
Thu Jun 6 17:24:25 2013 PPP: CHAP authentication succeededThu Jun 6 17:24:25 2013 PPP: LCP up
Thu Jun 6 17:24:25 2013 PPP: LCP received CONFACKThu Jun 6 17:24:25 2013 PPP: LCP sending CONFACK
Thu Jun 6 17:24:25 2013 PPP: LCP received CONFREQThu Jun 6 17:24:25 2013 PPP: LCP sending CONFREQ
Thu Jun 6 17:24:25 2013 PPP: Starting daemonThu Jun 6 17:24:21 2013 WAN link up (ADSL)
Thu Jun 6 17:23:37 2013 PPP connection down (VC1)Thu Jun 6 17:23:37 2013 PPP: Stopped daemon(0,1,5)
Thu Jun 6 17:23:37 2013 PPP: LCP sending TERMREQThu Jun 6 17:23:36 2013 PPP: IPCP down
Thu Jun 6 17:23:36 2013 PPP: LCP downThu Jun 6 17:23:36 2013 WAN link down (ADSL)
Thu Jun 6 16:34:54 2013 PPP connection up (VC1)Thu Jun 6 16:34:52 2013 PPP: IPCP up
Thu Jun 6 16:34:52 2013 PPP: IPCP received CONFACKThu Jun 6 16:34:52 2013 PPP: IPCP sending CONFREQ
Thu Jun 6 16:34:52 2013 PPP: IPCP received CONFNAKThu Jun 6 16:34:52 2013 PPP: IPCP sending CONFREQ
Thu Jun 6 16:34:51 2013 PPP: IPCP received CONFREJThu Jun 6 16:34:51 2013 PPP: IPCP sending CONFACK
Thu Jun 6 16:34:51 2013 PPP: IPCP received CONFREQThu Jun 6 16:34:51 2013 PPP: IPCP sending CONFREQ
Thu Jun 6 16:34:51 2013 PPP: CHAP authentication succeededThu Jun 6 16:34:51 2013 PPP: LCP up
Thu Jun 6 16:34:51 2013 PPP: LCP received CONFACKThu Jun 6 16:34:51 2013 PPP: LCP sending CONFACK
Thu Jun 6 16:34:50 2013 PPP: LCP received CONFREQThu Jun 6 16:34:50 2013 PPP: LCP sending CONFREQ
Thu Jun 6 16:34:50 2013 PPP: Starting daemonThu Jun 6 16:34:46 2013 WAN link up (ADSL)
Thu Jun 6 16:34:02 2013 PPP connection down (VC1)Thu Jun 6 16:34:02 2013 PPP: LCP sending TERMREQ
Thu Jun 6 16:34:02 2013 PPP: Stopped daemon(0,1,5)Thu Jun 6 16:34:02 2013 PPP: IPCP down
Thu Jun 6 16:34:02 2013 PPP: LCP downThu Jun 6 16:34:01 2013 WAN link down (ADSL)
Wed Jun 5 23:50:11 2013 PPP connection up (VC1)Wed Jun 5 23:50:08 2013 PPP: IPCP up
Wed Jun 5 23:50:08 2013 PPP: IPCP received CONFACKWed Jun 5 23:50:08 2013 PPP: IPCP sending CONFREQ
Wed Jun 5 23:50:08 2013 PPP: IPCP received CONFNAKWed Jun 5 23:50:08 2013 PPP: IPCP sending CONFREQ
Wed Jun 5 23:50:07 2013 PPP: IPCP received CONFREJWed Jun 5 23:50:07 2013 PPP: IPCP sending CONFACK
Wed Jun 5 23:50:07 2013 PPP: IPCP received CONFREQWed Jun 5 23:50:07 2013 PPP: IPCP sending CONFREQ
Wed Jun 5 23:50:07 2013 PPP: CHAP authentication succeededWed Jun 5 23:50:07 2013 PPP: LCP up
Wed Jun 5 23:50:07 2013 PPP: LCP received CONFACKWed Jun 5 23:50:07 2013 PPP: LCP sending CONFACK
Wed Jun 5 23:50:06 2013 PPP: LCP received CONFREQWed Jun 5 23:50:06 2013 PPP: LCP sending CONFREQ
Wed Jun 5 23:50:05 2013 PPP: Starting daemonWed Jun 5 23:49:58 2013 WAN link up (ADSL) |
I'm absolutely dreading having to deal with customer services yet again and the pointless resetting of the router and waiting a week for it to 'settle down'
EDIT: My IP profile is 2.2Mbps down, 0.83Mbps up. Currently achieving 0.14Mbps down and 0.34Mbps up!
Edited by deleted (Fri 07-Jun-13 23:29:48)
|
|
|
Try test socket, swap filters, Quiet Line Test (17070)?
No reason not to just reboot router, in daylight preferably.
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC - BQM
|
|
|
|
Hi
It really is a case of ruling things out.
For sync speed to suddenly drop so much there can only be a few causes:
1) Faulty line. Make sure you have a dial-tone, check the line is quiet and free from crackles. If you hear crackles then try the test socket behind the main face-plate, if still crackling call your phone provider and tell them it crackles on voice calls, don't mention broadband. Once the line is fixed your broadband will return to normal. If no crackles in the test socket but there is when plugged in normally then you have a local issue which is your responsibility to sort out, either yourself or taking a hit on an engineer fee.
2) Faulty modem/router or filters. Try a different modem, try different filters. As long as you can log into an alternative modem or router and see line stats that is all you need, you don't have to actually enter in ISP details, a router/modem will always sync regardless of ISP settings. If an alternative router/modem shows normal sync speeds your hardware is at fault. Note you must try swapping everything out including the RJ11 cable that goes to the modem/router to be certain you have no faults your end.
If you are sure 1 and 2 shows no issues, all you can do is contact your ISP. There can be faults on the line that will cause ADSL issues but not necessarily cause audible noise on voice calls. You could have a local issue with RF noise which can be hard to track down. It could just take one person with a faulty older TV to cause problems for people locally. Any neighbour been away for a month? Long shot but might identify someone with equipment causing issues.
The line card at the exchange may be faulty, I've had that twice before, took several days of me constantly stating nothing wrong my end before it was taken seriously by the ISP who then sent a card reset command and all came back to life.
Good luck.
Regards
Phil
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
I had similar experience with my connection speed but not so extreme as yours, the upstream collapsed and I found BBC iPlayer would not work. Try hard reboot the BrightBox router (switch power off then on) every morning, it took about a month for my connection to right itself.
http://forums.thinkbroadband.com/unhappiness/t/42432...
|
|
|
I have done a quiet line test. I'm pretty sure it's the same as it's always been, a few crackles in the background but nothing serious.
I am now plugged into the test socket and have changed: filter, RJ11 cable and modem. I'm still having problems, the noise margin seems to have plummeted and i'm getting lots more errors, error seconds and even loss of signal which i don't think i've ever had before.
I'm sure that there are no internal problems, this seems like a real BT fault. Should I ring EE and tell them I have a crackly line?
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
24 | Line Status --- SHOWTIME
Link Type --- Fast PathOperation Mode Automatic G992.5(ADSL2+)
Data Rate InformationStream Type Actual Data Rate
Upstream 775 (Kbps.)Downstream 3712 (Kbps.)
Defect/Failure IndicationOperation Data Upstream Downstream
Noise Margin 2.4 dB 4.9 dBLine Attenuation 21.7 dB 35.0 dB
Indicator Name Near End Indicator Far End IndicatorOutput Power 12.7 dBm 0.0 dBm
Fast Path FEC Correction 0 0Interleaved Path FEC Correction NA NA
Fast Path CRC Error #10 17Interleaved Path CRC Error NA NA
Loss of Signal Defect 1 0Fast Path HEC Error STR 10 13
Interleaved Path HEC Error NA NAError Seconds 158 124
StatisticsReceived Cells 334517
Transmitted Cells 29924 |
Log:
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
2829
3031
3233
3435
3637
3839
4041
4243
4445
4647
4849
5051
5253
5455
5657
5859
6061
6263
6465
66 | Sat Jun 8 11:33:25 2013 PPP connection up (VC1)
Sat Jun 8 11:33:23 2013 PPP: IPCP upSat Jun 8 11:33:23 2013 PPP: IPCP received CONFACK
Sat Jun 8 11:33:23 2013 PPP: IPCP sending CONFREQSat Jun 8 11:33:23 2013 PPP: IPCP received CONFNAK
Sat Jun 8 11:33:23 2013 PPP: IPCP sending CONFREQSat Jun 8 11:33:23 2013 PPP: IPCP received CONFREJ
Sat Jun 8 11:33:23 2013 PPP: IPCP sending CONFACKSat Jun 8 11:33:23 2013 PPP: IPCP received CONFREQ
Sat Jun 8 11:33:23 2013 PPP: IPCP sending CONFREQSat Jun 8 11:33:22 2013 PPP: CHAP authentication succeeded
Sat Jun 8 11:33:22 2013 PPP: LCP upSat Jun 8 11:33:22 2013 PPP: LCP received CONFACK
Sat Jun 8 11:33:22 2013 PPP: LCP sending CONFACKSat Jun 8 11:33:22 2013 PPP: LCP received CONFREQ
Sat Jun 8 11:33:22 2013 PPP: LCP sending CONFREQSat Jun 8 11:33:22 2013 PPP: Starting daemon
Sat Jun 8 11:33:18 2013 WAN link up (ADSL)Sat Jun 8 11:32:34 2013 PPP connection down (VC1)
Sat Jun 8 11:32:34 2013 PPP: Stopped daemon(0,1,5)Sat Jun 8 11:32:34 2013 PPP: LCP sending TERMREQ
Sat Jun 8 11:32:34 2013 PPP: IPCP downSat Jun 8 11:32:34 2013 PPP: LCP down
Sat Jun 8 11:32:33 2013 WAN link down (ADSL)Sat Jun 8 11:31:02 2013 PPP connection up (VC1)
Sat Jun 8 11:31:00 2013 PPP: IPCP upSat Jun 8 11:31:00 2013 PPP: IPCP received CONFACK
Sat Jun 8 11:31:00 2013 PPP: IPCP sending CONFREQSat Jun 8 11:31:00 2013 PPP: IPCP received CONFNAK
Sat Jun 8 11:31:00 2013 PPP: IPCP sending CONFREQSat Jun 8 11:31:00 2013 PPP: IPCP received CONFREJ
Sat Jun 8 11:31:00 2013 PPP: IPCP sending CONFACKSat Jun 8 11:30:59 2013 PPP: IPCP received CONFREQ
Sat Jun 8 11:30:59 2013 PPP: IPCP sending CONFREQSat Jun 8 11:30:59 2013 PPP: CHAP authentication succeeded
Sat Jun 8 11:30:59 2013 PPP: LCP upSat Jun 8 11:30:59 2013 PPP: LCP received CONFACK
Sat Jun 8 11:30:59 2013 PPP: LCP sending CONFACKSat Jun 8 11:30:59 2013 PPP: LCP received CONFREQ
Sat Jun 8 11:30:59 2013 PPP: LCP sending CONFREQSat Jun 8 11:30:59 2013 PPP: Starting daemon
Sat Jun 8 11:30:55 2013 PPP: Stopped daemon(0,1,5)Sat Jun 8 11:30:55 2013 PPP connection down (VC1)
Sat Jun 8 11:30:55 2013 PPP: LCP sending TERMREQSat Jun 8 11:30:55 2013 PPP: IPCP down
Sat Jun 8 11:30:54 2013 PPP: LCP downSat Jun 8 11:30:26 2013 admin login success from 192.168.1.22
Sat Jun 8 11:30:04 2013 admin timeout from 192.168.1.22Sat Jun 8 11:29:44 2013 PPP connection up (VC1)
Sat Jun 8 11:29:41 2013 PPP: IPCP upSat Jun 8 11:29:41 2013 PPP: IPCP received CONFACK
Sat Jun 8 11:29:41 2013 PPP: IPCP sending CONFREQSat Jun 8 11:29:41 2013 PPP: IPCP received CONFNAK
Sat Jun 8 11:29:41 2013 PPP: IPCP sending CONFREQSat Jun 8 11:29:40 2013 PPP: IPCP received CONFREJ
Sat Jun 8 11:29:40 2013 PPP: IPCP sending CONFACKSat Jun 8 11:29:40 2013 PPP: IPCP received CONFREQ
Sat Jun 8 11:29:40 2013 PPP: IPCP sending CONFREQSat Jun 8 11:29:40 2013 PPP: CHAP authentication succeeded
Sat Jun 8 11:29:40 2013 PPP: LCP upSat Jun 8 11:29:39 2013 PPP: LCP received CONFACK
Sat Jun 8 11:29:39 2013 PPP: LCP sending CONFACKSat Jun 8 11:29:39 2013 PPP: LCP received CONFREQ
Sat Jun 8 11:29:39 2013 PPP: LCP sending CONFREQSat Jun 8 11:29:38 2013 PPP: Starting daemon
Sat Jun 8 11:29:32 2013 WAN link up (ADSL) |
Edited by deleted (Sat 08-Jun-13 11:40:46)
|
|
|
Why are you telling me in an essay what I already told OP in 10 words?
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC - BQM
|
|
|
a few crackles in the background but nothing serious.
There should be no noise at all, so this may well be a symptom.
Should I ring EE and tell them I have a crackly line?
No, 'cos they will just have you ring BT, and you'll most likely get stuck in a loop between them and EE.
I'd suggest ringing them and reporting slow speeds, jump through their hoops, don't mention the noise on the line, as this will be their 'get out of jail free' card, to fob you off.
Take a deep breath, and be brave. 
|
|
|
No, 'cos they will just have you ring BT Unlikely OP is with BT Retail for phone. Orange/EE have only sold phone/BB packages for ages, so unless OP is legacy cust like me ...
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC - BQM
|
|
|
I hardly ever use the landline, in fact, the last time I used it was probably when I was sorting out problems when I first moved to Orange 9 months ago. I'm pretty sure it had the same background noise when it was working properly.
I reported the problem yesterday, had to hang up on the first customer services agent because she was getting very stroppy. The second person was much better, so will hopefully get a call from 2nd line tomorrow.
Edited by deleted (Sun 09-Jun-13 17:21:14)
|
|
|
|
Really really sorry, of course it wasn't meant for yourself, I just got confused about where I was replying to, this forum works differently to most others.
Didn't mean to intrude on the thread, if you are unhappy at my comments please request a moderator deletes it, I have no objections to that.
|
|
|
S'OK!
Mods don't delete posts just cuz they are wrong in some way; only if they break rules.
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC - BQM
|
|
|
|
Still having problems. It took until Wednesday before I was allowed to speak to the fault management, every time I ring another story gets spun that always has the same ending "we will know something in 24 hours".
|
|
|
How does your contract stand with them ? If getting no joy, vote with your feet, and migrate to a service provider who will deal with your issues, is this not what you pay them for ?
|
|
|
How does your contract stand with them ? If getting no joy, vote with your feet, and migrate to a service provider who will deal with your issues, is this not what you pay them for ?
I still have 6 months left. The openreach engineer didn't bother to turn up yesterday. I understand that EE having shocking customer service that over-promise and under-deliver. However
I can now see that a major problem is the link between Openreach and the ISPs. All they have is an e-chat system to communicate with Openreach, it can take a very long time for Openreach to respond and then a new shift of people start at EE and then nobody rings back.
Another thing that really annoyed me is the list of charges that's read out when you book an engineer (faulty equipment, not being in) yet there's nothing for when the engineer doesn't turn up! Worse still the engineer didn't update the system to say that they were a no-show which meant that EE couldn't book a new engineer until the old booking had been closed.
I thought BT was split up to make it less wasteful and more efficient!?
|
|
|
Now we have warmer weather it might improve your line connection speed. With the drop in line speeds I�m surprised your connection is still on fastpath. Have you tried switching the router off over night, in the morning when you switch back on I think it gives the exchange MSAN a good old kick each time. 
http://en.wikipedia.org/wiki/Multi-service_access_node
http://en.wikipedia.org/wiki/Asymmetric_digital_subs...
|
|
|
I just want my connection back to how it was for 6/7 months. I'm not sure doing anything with the router will do much good.
It seems I have way too many errors and even loss of 'signal defects'.
EDIT: And to take the maximum wee-wee there are four Openreach vans parked up opposite my house right now! I had a chat with them and they're working on someone elses line fault.
Edited by deleted (Wed 19-Jun-13 12:36:12)
|
|
|
You don�t do anything to the router its all-automatic and controlled by the exchange MSAN (Multi-service access node). You just switch off the power to the router last thing at night then next morning switch back on and see if it makes any difference to your connection speeds. By now with all the errors your connection should have changed to Interleaved.
Edited by deleted (Wed 19-Jun-13 12:34:13)
|
|
|
I just want my connection back to how it was for 6/7 months. I'm not sure doing anything with the router will do much good.
It seems I have way too many errors and even loss of 'signal defects'.
EDIT: And to take the maximum wee-wee there are four Openreach vans parked up opposite my house right now! I had a chat with them and they're working on someone elses line fault. Maybe there is a fault in your street cabinet that is affecting everyone in your street.
|
|
|
Maybe there is a fault in your street cabinet that is affecting everyone in your street.
I'm pretty sure it isn't a larger fault, otherwise the engineers would have told me.
|
|
|
I'm pretty sure it isn't a larger fault No, it can't be; it only takes 4 OR vans.
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC
|
|
|
I'm pretty sure it isn't a larger fault No, it can't be; it only takes 4 OR vans.
Well they've all gone and my connection's still [censored]. You missed out the most important part of the quote, I had asked them if it was an area fault that they were working on and they said it wasn't. They were probably waiting to take their lunch break together, only one of them seemed to be doing something.
Edited by deleted (Wed 19-Jun-13 14:04:40)
|
|
|
The engineer said something was broken on the pole and water had been leaking onto a connection. That was replaced, so I'm back up and running now. The speeds are not great at all, I had a follow up call from EE and they've reset my profile, was give the usual 10 day spiel so will see what happens. I seem to remember last time there was an immediate jump in speeds after the fault was repaired.
Connected for ~10 minutes:
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
| Line Status --- SHOWTIME
Link Type --- Interleaved PathOperation Mode G992.5(ADSL2+) G992.5(ADSL2+)
Data Rate InformationStream Type Actual Data Rate
Upstream 759 (Kbps.)Downstream 4626 (Kbps.)
Defect/Failure Indication
Operation Data Upstream DownstreamNoise Margin 5.8 dB 5.9 dB
Line Attenuation 20.7 dB 34.0 dB
Indicator Name Near End Indicator Far End IndicatorOutput Power 10.1 dBm 0.0 dBm
Fast Path FEC Correction NA NAInterleaved Path FEC Correction 1923 0
Fast Path CRC Error NA NAInterleaved Path CRC Error 0 0
Loss of Signal Defect 0 0Fast Path HEC Error STR NA NA
Interleaved Path HEC Error 0 0Error Seconds 0 0 |
Edited by deleted (Wed 19-Jun-13 21:05:36)
|
|
|
Well it's better but only just. Not what I'd expect, 12+ Meg, and wouldn't expect it to change over 10 days.
PS: You missed the most important part, , of my previous post
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC
|
|
|
Well it's better but only just. Not what I'd expect, 12+ Meg, and wouldn't expect it to change over 10 days.
Why won't it change over the next 10 days? Is there anything that I can or should do? (preferably not involving ringing EE!)
Will the modem re-sync on its own? Or does it have to be disconnected to then try and connect at a faster speed? Will it automatically change to fastpath?
|
|
|
Cuz as you said "I seem to remember last time there was an immediate jump in speeds after the fault was repaired" and that is my experience.
The router will re-sync on its own if deemed necessary, but there is no harm in giving a prod, say once a day in daylight, by rebooting. Fast Path will be decided auto by the DLM.
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC
|
|
|
Cuz as you said "I seem to remember last time there was an immediate jump in speeds after the fault was repaired" and that is my experience.
The router will re-sync on its own if deemed necessary, but there is no harm in giving a prod, say once a day in daylight, by rebooting. Fast Path will be decided auto by the DLM.
I've read that it's a good idea to leave it off for a while 10 minutes or more so that the DLM doesn't think that it's disconnecting because of a dodgy connection, is this correct?
|
|
|
Think it's an urban myth. It's more the frequency of discons rather than their lengths. I just switch it of for a few seconds; seems to do the trick.
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC
|
|
|
I left the connection off all night and it's reconnected at exactly the same speeds
I think the last time I was in this situation UKDoc helped but I don't think he's around anymore.
|
|
|
I tried a quiet line test today and noticed that it disconnected my BB as soon as the call went through. If I listen to the phone whilst the BB reconnects I can just about hear what sounds like old dialup noises.
I have reported this to EE and was told that it will take 48 hours for someone to get back to me about the problem!
Just to make sure, I have tried a spare brightbox and filter (through the test socket). I'm at a loss as to what's happening especially seeing as the engineer that came yesterday said he'd cleared the high resistance fault.
Any ideas what the problem could be? Nothing has changed with my setup since I had the great connection for 6/7 months.
Edited by deleted (Thu 20-Jun-13 20:41:20)
|
|
|
After three weeks, one engineer no show and three engineers my broadband is back up and running at full speed. The problems got so bad that every time the landline was used the broadband would disconnect.
The first engineer said there was a high resistance fault, replaced a bag and some connections at the pole. This didn't do anything and I got stuck on interleaved.
Second, said there was faulty EE equipment at the exchange and changed the ports that I was connected to. Had a slight increase in speed but no real joy.
Third, said there were definitely problems with the line at multiple points. Fixed everything and stuck a new filtered fibre socket for me!
Uptime 8:30
Stats:
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
24 | Line Status --- SHOWTIME
Link Type --- Fast PathOperation Mode Automatic G992.5(ADSL2+)
Data Rate Information
Stream Type Actual Data RateUpstream 1167 (Kbps.)
Downstream 15705 (Kbps.)
Defect/Failure IndicationOperation Data Upstream Downstream
Noise Margin 5.5 dB 5.0 dBLine Attenuation 18.9 dB 32.5 dB
Indicator Name Near End Indicator Far End Indicator
Output Power 12.0 dBm 0.0 dBmFast Path FEC Correction 0 0
Interleaved Path FEC Correction NA NAFast Path CRC Error 2693 40
Interleaved Path CRC Error NA NALoss of Signal Defect 1 0
Fast Path HEC Error STR 2175 15Interleaved Path HEC Error NA NA
Error Seconds 518 32 |
|
|
|
Success!
Note line has "shortened", i.e attn. decreased.
ES might be high if you've only been up for 8.5 mins but OK for 8.5 hrs.
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC
|
|
|
Success!
Note line has "shortened", i.e attn. decreased.
ES might be high if you've only been up for 8.5 mins but OK for 8.5 hrs.
It was 8.5 hours, should have made that more clear. Interestingly this morning it had switched to ADSL G. 992.1, I have now forced it to ADSL2+ and the stats have gone back to what I had posted earlier.
Edited by deleted (Sat 29-Jun-13 09:28:30)
|
Pages in this thread: 
Print Thread
