PLusnet - very high/low SNR/ Loop att

ADSL 512k, Draytek 2500 router

SNR is averaging at 12.9 but often drops closer to 10, Loop att is
currently 59.8, but goes above 60 and this figure then turns red, I
assume a warning of sorts?

User is getting a lot of 404's, and generally sluggish connection when
it does work.

Would the above figures be indicative of these types of symptoms, along
with a fault on the line perhaps?

Have changed the MTU, currently 1430, but this has made no difference
across the board.

ISP is Plusnet

Tx2 <(E-Mail Removed)> wrote in
news:(E-Mail Removed) t:

> Would the above figures be indicative of these types of symptoms, along
> with a fault on the line perhaps?

Sounds like it to me. SNR etc would be either a line or exchange fault or
could be CPE (Customer Premises Equipment) as in extensions, filters and
modem.

--
Colin
*Drop DEAD from the email address to reply*

On Wed, 20 Oct 2004 21:31:52 +0100, Tx2
<(E-Mail Removed)> wrote:

>SNR is averaging at 12.9 but often drops closer to 10, Loop att is
>currently 59.8, but goes above 60 and this figure then turns red, I
>assume a warning of sorts?

60 dB is the old BT limit, may be why its there. 10-13 dB of margin is
quite decent though. Is the upstream noise margin ok and the speed 288
kbps ?

>User is getting a lot of 404's, and generally sluggish connection when
>it does work.
>
>Would the above figures be indicative of these types of symptoms, along
>with a fault on the line perhaps?

does it count CRC errors or similar, or loss of sync or retrains -
these are better indications or ideall y alog file showing loss of
connection.

>Have changed the MTU, currently 1430, but this has made no difference
>across the board.

changed on the PCs, the router, both ?

Phil
--
spamcop.net address commissioned 18/06/04
Come on down !

In article <(E-Mail Removed)>,
(E-Mail Removed), a.k.a Phil Thompson says...


> does it count CRC errors or similar, or loss of sync or retrains -
> these are better indications or ideall y alog file showing loss of
> connection

There is loss of sync i *think*, the front panel LED's indicate the
state, but i haven't been able to confirm such.

In the config panel of the router however, there is indication that the
line has been lost, and is retraining.

I wasn't at the router last night when all these issues were occurring,
but on the end of the phone giving instruction, and being told what was
going on.

I got the user to disconnect all phone equipment in the premises, remove
all filters, try each filter in turn etc etc. I am waiting for him to
tell me if there was any change, but i suspect there won't be.

> >Have changed the MTU, currently 1430, but this has made no difference
> >across the board.
>
> changed on the PCs, the router, both ?

On both PC and NIC

Tx2 wrote:
> In article <(E-Mail Removed)>,
> (E-Mail Removed), a.k.a Phil Thompson says...
>
>
>> does it count CRC errors or similar, or loss of sync or retrains -
>> these are better indications or ideall y alog file showing loss of
>> connection
>
> There is loss of sync i *think*, the front panel LED's indicate the
> state, but i haven't been able to confirm such.
>
> In the config panel of the router however, there is indication that
> the line has been lost, and is retraining.
>
> I wasn't at the router last night when all these issues were
> occurring, but on the end of the phone giving instruction, and
> being told what was going on.
>
> I got the user to disconnect all phone equipment in the premises,
> remove all filters, try each filter in turn etc etc. I am waiting
> for him to tell me if there was any change, but i suspect there
> won't be.

Try removing all extension wiring & only connecting to the test socket at
the back of the NE5, if this improves the matter wire up the extensions as 2
wire (pins 2 & 5) & see if everything is still ok.

It does sound like a SNR problem which could be being caused by 'pickup'
through the bell wire, especially if it happens later in the day & then
stops again in the morning, but remote diagnosis is very much a poke in the
dark so I may be wildly out.