Slow speeds after power cut

Started by Glenn, Jan 26, 2009, 13:40:25

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Rik

I know just how you feel, I'm just below a 3M profile right now, another 96k would do it. :(
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

I wonder if removing the 2 phone extensions (I use cordless phones) would improve things? The only problem there is, the BT engineer hard wired them to the back of the master socket, not the removable front plate.
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

Quote from: Glenn on Jan 26, 2009, 15:28:10
Yes it's manually set at 12, I got back onto the BT speedtester, it still shows a 1250 profile ???

Out of interest is this manually set by yourself or by BT
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Quote from: Glenn on Jan 30, 2009, 10:38:38
I wonder if removing the 2 phone extensions (I use cordless phones) would improve things? The only problem there is, the BT engineer hard wired them to the back of the master socket, not the removable front plate.

It could well do, Glenn. As they are wired 'unconventionally' I suspect you could get away with doing it yourself.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

Quote from: stevethegas on Jan 30, 2009, 10:39:02
Out of interest is this manually set by yourself or by BT

BT Steve, it was at 6, then 9 now 12, the last engineer said he would get it done to stabilise my line, along with turning on Interleaving
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

One of the extensions runs behind my plasma TV, it generates a lot of ADSL frequency noise when turned on.
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

In that case, definitely remove them.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

OK I'm going in, don't call me for the 20 minutes, I don't want a 48v DC shock
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Call you what, Glenn? ;D (I thought it was nearer 80V, btw.)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Simon

It might clear your head, Glenn!  ;D
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

OK all the extensions are disconnected, the router has resync'd a little higher at 2784kbs
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

BTW we were both wrong, it's 50v
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Baz

mines back to

Your DSL connection rate: 8128 kbps(DOWN-STREAM),  448 kbps(UP-STREAM)
    IP profile for your line is - 7150 kbps
    Actual IP throughput achieved during the test was - 4782 kbps

congestion??


BTW got this test done using FF  :o :o :o :o   amazing first time in ages that its worked in FF for me  :)

Rik

Congestion is most likely, Baz. IDNet's got masses of extra capacity today, so I can be certain it's not an issue there.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

I agree, it looks like exchange congestion.

Glenn

Since removing both extensions, the number of errors over 24hr seems lower than before :fingers:

DSL
Cumulative Seconds w/Errors:       795       795       5       0:03:30
Cumulative Sec. w/Severe Errors:       127       127       0       2:28:40
Corrected Blocks:       13377       13377       56       0:00:35
Uncorrectable Blocks:       7734       7734       6       0:03:30
DSL Unavailable Seconds:       0       0       0       0:00:00
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Every little helps, to coin a phrase. :)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Baz

Quote from: Rik on Jan 30, 2009, 18:57:15
Congestion is most likely, Baz. IDNet's got masses of extra capacity today, so I can be certain it's not an issue there.

just got my weekly email of router logs and it shows this, bit long sorry

Sun, 2009-01-25 02:00:01 - Send E-mail Success!
Sun, 2009-01-25 15:06:44 - Send out NTP request to 158.43.192.66
Sun, 2009-01-25 15:06:44 - Receive NTP Reply from 158.43.192.66
Wed, 2009-01-28 13:06:44 - Send out NTP request to 158.43.192.66
Wed, 2009-01-28 13:06:43 - Receive NTP Reply from 158.43.192.66
Wed, 2009-01-28 13:44:00 - LCP down.
Wed, 2009-01-28 13:44:07 - Initialize LCP.
Wed, 2009-01-28 13:44:07 - LCP is allowed to come up.
Wed, 2009-01-28 13:45:08 - Initialize LCP.
Wed, 2009-01-28 13:45:08 - LCP is allowed to come up.
Wed, 2009-01-28 13:46:08 - Initialize LCP.
Wed, 2009-01-28 13:46:08 - LCP is allowed to come up.
Wed, 2009-01-28 13:47:05 - CHAP authentication failed
Wed, 2009-01-28 13:47:05 - LCP down.
Wed, 2009-01-28 13:47:08 - Initialize LCP.
Wed, 2009-01-28 13:47:08 - LCP is allowed to come up.
Wed, 2009-01-28 13:48:08 - Initialize LCP.
Wed, 2009-01-28 13:48:08 - LCP is allowed to come up.
Wed, 2009-01-28 13:48:56 - CHAP authentication failed
Wed, 2009-01-28 13:48:56 - LCP down.
Wed, 2009-01-28 13:49:08 - Initialize LCP.
Wed, 2009-01-28 13:49:08 - LCP is allowed to come up.
Wed, 2009-01-28 13:50:08 - Initialize LCP.
Wed, 2009-01-28 13:50:08 - LCP is allowed to come up.
Wed, 2009-01-28 13:51:08 - Initialize LCP.
Wed, 2009-01-28 13:51:08 - LCP is allowed to come up.
Wed, 2009-01-28 13:51:35 - CHAP authentication success
Thu, 2009-01-29 12:21:38 - LCP down.
Thu, 2009-01-29 12:21:40 - Initialize LCP.
Thu, 2009-01-29 12:21:40 - LCP is allowed to come up.
Thu, 2009-01-29 12:22:40 - Initialize LCP.
Thu, 2009-01-29 12:22:40 - LCP is allowed to come up.
Thu, 2009-01-29 12:23:40 - Initialize LCP.
Thu, 2009-01-29 12:23:40 - LCP is allowed to come up.
Thu, 2009-01-29 12:24:30 - CHAP authentication failed
Thu, 2009-01-29 12:24:30 - LCP down.
Thu, 2009-01-29 12:24:40 - Initialize LCP.
Thu, 2009-01-29 12:24:41 - LCP is allowed to come up.
Thu, 2009-01-29 12:25:41 - Initialize LCP.
Thu, 2009-01-29 12:25:41 - LCP is allowed to come up.
Thu, 2009-01-29 12:26:32 - CHAP authentication failed
Thu, 2009-01-29 12:26:32 - LCP down.
Thu, 2009-01-29 12:26:41 - Initialize LCP.
Thu, 2009-01-29 12:26:41 - LCP is allowed to come up.
Thu, 2009-01-29 12:27:41 - Initialize LCP.
Thu, 2009-01-29 12:27:41 - LCP is allowed to come up.
Thu, 2009-01-29 12:28:41 - Initialize LCP.
Thu, 2009-01-29 12:28:41 - LCP is allowed to come up.
Thu, 2009-01-29 12:29:41 - Initialize LCP.
Thu, 2009-01-29 12:29:41 - LCP is allowed to come up.
Thu, 2009-01-29 12:30:41 - Initialize LCP.
Thu, 2009-01-29 12:30:41 - LCP is allowed to come up.
Thu, 2009-01-29 12:31:41 - Initialize LCP.
Thu, 2009-01-29 12:31:41 - LCP is allowed to come up.
Thu, 2009-01-29 12:32:41 - Initialize LCP.
Thu, 2009-01-29 12:32:41 - LCP is allowed to come up.
Thu, 2009-01-29 12:32:50 - CHAP authentication success
Fri, 2009-01-30 13:57:59 - LCP down.
Fri, 2009-01-30 13:58:01 - Initialize LCP.
Fri, 2009-01-30 13:58:01 - LCP is allowed to come up.
Fri, 2009-01-30 13:59:01 - Initialize LCP.
Fri, 2009-01-30 13:59:01 - LCP is allowed to come up.
Fri, 2009-01-30 14:00:01 - Initialize LCP.
Fri, 2009-01-30 14:00:01 - LCP is allowed to come up.
Fri, 2009-01-30 14:01:01 - Initialize LCP.
Fri, 2009-01-30 14:01:01 - LCP is allowed to come up.
Fri, 2009-01-30 14:02:01 - Initialize LCP.
Fri, 2009-01-30 14:02:01 - LCP is allowed to come up.
Fri, 2009-01-30 14:03:02 - Initialize LCP.
Fri, 2009-01-30 14:03:02 - LCP is allowed to come up.
Fri, 2009-01-30 14:03:22 - CHAP authentication success
Fri, 2009-01-30 14:03:57 - LCP down.
Fri, 2009-01-30 14:04:04 - Initialize LCP.
Fri, 2009-01-30 14:04:04 - LCP is allowed to come up.
Fri, 2009-01-30 14:04:58 - CHAP authentication success
Fri, 2009-01-30 14:05:05 - Initialize LCP.
Fri, 2009-01-30 14:05:05 - LCP is allowed to come up.
Fri, 2009-01-30 14:05:09 - CHAP authentication success
Fri, 2009-01-30 14:05:39 - LCP down.
Fri, 2009-01-30 14:06:05 - Initialize LCP.
Fri, 2009-01-30 14:06:05 - LCP is allowed to come up.
Fri, 2009-01-30 14:07:05 - Initialize LCP.
Fri, 2009-01-30 14:07:05 - LCP is allowed to come up.
Fri, 2009-01-30 14:08:05 - Initialize LCP.
Fri, 2009-01-30 14:08:05 - LCP is allowed to come up.
Fri, 2009-01-30 14:08:23 - CHAP authentication success
Fri, 2009-01-30 19:45:51 - Administrator login successful - IP:*********
Fri, 2009-01-30 21:30:12 - Administrator login successful - IP:*********
Fri, 2009-01-30 22:12:32 - Administrator login successful - IP:*********
Sat, 2009-01-31 11:06:43 - Send out NTP request to 158.43.192.66
Sat, 2009-01-31 11:06:42 - Receive NTP Reply from 158.43.192.66

is this anything to do with the recent work thats been done.

Steve

Baz,Not sure about Wednesday but the new router and related issues could possibly account for Thursday and Friday.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Baz

cheers Steve, will see if any one else has more ideas

Rik

Those times coincide with the outages on all three days, Baz.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.