ADSL Line Noise

[l1ghtsp33d]

We have a few clienst who have ADSL lines.

Now some of the TERRIBLE connections.

Some have NO problems.

We use the same Router in every instance (NETGEAR).

Now Line Attenuation (distance from the exchange) and SNR(signal to Noise ratio) aka Noise Margin play a big role apparently.

our current problem is a client that drops after 5 mins. EVERYTIME.
We have done it ALL.

Telkom tech comes out, runs a little test and says its fine,then leave.
Now we have gone through this before with them with our OWN line for our business. In the end after many many hours of fights, it came done to corroded connections on the actual telephone POST! outside our premises.

Can anyone else shed some light??

 

[l1ghtsp33d]

there are no filters on the line. JUST the Netgear router that has been replaced, firmware upgraded, PC reinstalled and the Line Attenuation and SNR seem fine.

WTF is going on??

I understand that older area's have older cabling and could give problems, but this is a new subburb.

and the exchange is not the little Telkom Box on the pavement right?

 

[fluKe]

Get the filter they tell me, *plugs in filter*, more noise than before... retards

 

[swordfish1]

hmmm filter worked for me ... maybe you gave different "type" of noise ...

 

[PostmanPot]

the line drops every 5 mins and it gets disconnected so you have to reconnect again? i.e it displays "link to xxx has failed"...

have you tried BRIDGE mode instead of ROUTE mode on the router? bridge = you dial to the net with user and pass through winblows.

what is your packet loss like?

 

[Fyre]

In my experience the Netgear routers are more succeptable (sp?) to line noise. I had the same problem a while ago. It dropped all the time. Had Telkom out here many a time, and eventually had the problem bumped to SI (Special Investigation). They found the problem somewhere on the line. This was after I made them give me a Telkom router to run over the weekend to prove that it wasn't my router at fault. The Telkom router managed to "hold" the connection longer, but the underlying problem was still there. Luckily it's fixed now.