George wrote:
>>A neighbour is using AOL ADSL, and in the last couple of weeks has been
>>regraded from 576/288 to 2272/288 but now cannot get connected
>>reliably.
>>
SNIP
>
>
> An easy way to check for a line fault is by checking if the modem is in
> sync. If the DSL light on the modem is on solidly - the modem is in
> sync. If not, there is an issue with the physical connections at your
> end or a line fault. (Assumming that the drivers are okay etc). Some
> things to try - (Assuming the modem is in sync)
>
> Do the DUN tests - Double click the arrows in the systray, and do Test 1
> and 2. If these both pass, the line is fine. If not, post your error
> codes here!
>
> Check your line anntenuation - Double click the arrows, click status,
> press CTRL + F1, select DSL link. For a 2Mb/s line the local
> anntenuation should be below 43db. If it is above this contact AOL with
> this information - You have a respeed fault.
>
Just played with this trick on the BT Voyager - it shows loads of things!!
We had BT round to sort a 2dB signal to noise problem. He was using a BT
Voyager modem and had to connect to their test server each time to do tests.
It was a real problem as the 2dB s/n on the line meant he often couldn't
even connect to their server to do the tests.
Apparantly the BT acceptance level is about 7dB s/n but fortunately it
was so variable on our line that he investigated further.
It looks as if he didnt't know about this clever trick with the modem.
He found the fault was a faulty pair very close to the exchange and,
listening across the line, the data was very strange. He did comment
that sometimes ADSL will actually work on a very faulty line but you may
well have problems.
We had found that the line worked reasoanbly using a proper (Dreytek
Vigor) modem but the BT Voyager dropped out all the time.
Mike
|