BT BB randomly dropping connection

mugenextreme

Was wondering had anyone been having any difficulty with BT broadband dropping connection. Recently on my netgear router i keep get brief loss of the internet connection. I gotta wait 10-20secs or so and the link is restablished, this is not a big issue if i was just browsing but i use it for some online gaming and of course it picks mid race or round to drop. I am on the Clontarf exchange.
For the techies out there, is there a program that you can use to monitor you connection as it is running to possibly pinpoint a cause for something like this.

Sponge Bob

line stats so !

mugenextreme

[IMG][/img]




Pinging www.boards.ie [89.234.66.107] with 32 bytes of data:

Reply from 89.234.66.107: bytes=32 time=52ms TTL=57
Reply from 89.234.66.107: bytes=32 time=53ms TTL=57
Reply from 89.234.66.107: bytes=32 time=51ms TTL=57
Reply from 89.234.66.107: bytes=32 time=51ms TTL=57

Ping statistics for 89.234.66.107:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 53ms, Average = 51ms


ADSL Link Downstream Upstream
Connection Speed 6816 kbps 640 kbps
Line Attenuation 27 db 15.5 db
Noise Margin 1 db 6 db

2qk4u

I got BT broadband last wednesday and it has no worked right for a whole day since. It just stops working clompletely. I have to turn of the router to get it working again.

branners69

I have the same problem with my BT connection just stopping. I then have to connect to my voyager and reconnect.

I contacted BT and they sent me out a new voyager but it didnt sort the problem!

I am on the belcamp exchange.

dub45

mugenextreme wrote: »

[IMG][/img]




Pinging www.boards.ie [89.234.66.107] with 32 bytes of data:

Reply from 89.234.66.107: bytes=32 time=52ms TTL=57
Reply from 89.234.66.107: bytes=32 time=53ms TTL=57
Reply from 89.234.66.107: bytes=32 time=51ms TTL=57
Reply from 89.234.66.107: bytes=32 time=51ms TTL=57

Ping statistics for 89.234.66.107:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 53ms, Average = 51ms


ADSL Link Downstream Upstream
Connection Speed 6816 kbps 640 kbps
Line Attenuation 27 db 15.5 db
Noise Margin 1 db 6 db

Your noise margin is disastrous and this will cause the constant drop outs.

Check that there are filters on all your lines and that your internal wiring is ok but the most likely solution is dropping your speed.

http://www.kitz.co.uk/adsl/lowSNR.htm

dub45

branners69 wrote: »

I have the same problem with my BT connection just stopping. I then have to connect to my voyager and reconnect.

I contacted BT and they sent me out a new voyager but it didnt sort the problem!

I am on the belcamp exchange.

Posting like this is absolutely useless no one can help you on the basis of the lack of information above. Line stats are essential.

Sponge Bob

(S)he posted the key stats in fairnes , noise margin of 1db explains everything.

now disconnect EVERYTHING from the line bar the dsl modem, and including the filters phones sky box etc , and run the stats again , the magic number is 6-8db to ensure stability.

after that plug them in one by one to see which one borks the stats

vibe666

Sponge Bob wrote: »

(S)he posted the key stats in fairnes , noise margin of 1db explains everything.

the OP did, but that's not who was quoted in dub45's post.

mugenextreme

Sponge , did a bit of investigation into this now that i know what to look to change. I have no sky or anything other then phone handset . I Disconnected it and noticed nothing change on the noise side. Only other thing i i though of was the cable running from the wall socket and the micro filter . Quite a long cable as it has to run from one side of the house to the other to reach the router, I move the router next to the micro filter and attached it with a 1meter phone cable and this was the resulting change in the stats from the first set bear in mind i have not connected to the router directly, rather using my lappy to connect to it wireless so it my still be affecting it slightly. there is a dramatic difference

Pinging www.boards.ie [89.234.66.107] with 32 bytes of data:

Reply from 89.234.66.107: bytes=32 time=45ms TTL=58
Reply from 89.234.66.107: bytes=32 time=45ms TTL=58
Reply from 89.234.66.107: bytes=32 time=44ms TTL=58
Reply from 89.234.66.107: bytes=32 time=45ms TTL=58

Ping statistics for 89.234.66.107:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 45ms, Average = 44ms

ADSL Link Downstream Upstream
Connection Speed 7616 kbps 672 kbps
Line Attenuation 10 db 4 db
Noise Margin 10 db 12 db

branners69

dub45 wrote: »

Posting like this is absolutely useless no one can help you on the basis of the lack of information above. Line stats are essential.

If you read my post I never actually asked for help????

What my post did was clarify to the op that replacing my router didnt help and that I am on the Belcamp exchange!

Sponge Bob

Good stuff OP , nothing like a bit of logic sometimes.

A margin of 10db should stabilise the line for you . The pings are a bit on the high side ...is it that 7.6mb package by the way which would explain that ??

Sierra Oscar

You think thats bad?



And I am on a 7.6MB connection. Ringing BT now.

vibe666

Sierra Oscar wrote: »

You think thats bad?

And I am on a 7.6MB connection. Ringing BT now.

do you have line stats for that?

Sierra Oscar

vibe666 wrote: »

do you have line stats for that?

Downstream Rate:7616 Kbps Upstream Rate:672 Kbps
Im using a Linksys modem, where would I find the noise info?

I rang BT, and they told me it was contention and they would do nothing for me - saying that it is only advertised to give me speeds up to 7.5MB.

kleefarr

Also been having random connection issues. Have noticed that the IP 212. is cropping up and seems to be worse on that IP number.



DSL Noise Margin: DOWN 5.8 dB / UP 18.8 dB
DSL Attenuation: DOWN 39.5 dB / UP 19.9 dB
DSL Transmit Power: DOWN 0.0 dBm / UP 12.8 dBm

Pinging www.boards.ie [89.234.66.107] with 32 bytes of data:

Reply from 89.234.66.107: bytes=32 time=31ms TTL=58
Reply from 89.234.66.107: bytes=32 time=37ms TTL=58
Reply from 89.234.66.107: bytes=32 time=37ms TTL=58
Reply from 89.234.66.107: bytes=32 time=42ms TTL=58

Ping statistics for 89.234.66.107:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 42ms, Average = 36ms

On 8MB BT and this is one of the better speeds I have had over the last couple of days.

horse7

and just what do you pay bt for.as far as i can find out they have no field technicians.sorry i cant help.

dub45

kleefarr wrote: »

Also been having random connection issues. Have noticed that the IP 212. is cropping up and seems to be worse on that IP number.



DSL Noise Margin: DOWN 5.8 dB / UP 18.8 dB
DSL Attenuation: DOWN 39.5 dB / UP 19.9 dB
DSL Transmit Power: DOWN 0.0 dBm / UP 12.8 dBm

Pinging www.boards.ie [89.234.66.107] with 32 bytes of data:

Reply from 89.234.66.107: bytes=32 time=31ms TTL=58
Reply from 89.234.66.107: bytes=32 time=37ms TTL=58
Reply from 89.234.66.107: bytes=32 time=37ms TTL=58
Reply from 89.234.66.107: bytes=32 time=42ms TTL=58

Ping statistics for 89.234.66.107:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 42ms, Average = 36ms

On 8MB BT and this is one of the better speeds I have had over the last couple of days.

Your noise margin is bad anything under 10 and you are most likely going to have disconnects. Check your internal wiring filters etc but usually the answer is a speed downgrade and increased speeds but a lot of pressure on snr.

Jackz

My line seems to drop every evening at 8pm, coincidence or these stats?

Line Mode ADSL2+ Line State Show Time
Line Power State L0 Line Up Time 00:00:23:30
Line Coding Trellis On Line Up Count 1

Statistics Downstream Upstream
Line Rate 20244 Kbps 1019 Kbps
Noise Margin 6.1 dB 14.0 dB
Line Attenuation 30.0 dB 14.0 dB
Output Power 11.6 dBm 0.0 dBm

Sponge Bob

BT ADSL2 LLU which is what you have Jackz will always try to adapt conditions to peg the margin at 6db so it could be a transient that catches them out before they can adapt the speed / margin metrics .

Other dsl users in the area can create noise on the line through crosstalk .

Is it once a day at 8pm and only then ??

jayflame

I got a new Voyager 2110 2 weeks ago and it kept dropping its connection.

I followed this link;

http://www.iol.ie/~drivers/upgrade2110.html

and upgraded the firmware to the latest on the site.
Everything has been fine since, apart from its 24hr connection refresh.

Suggest you do the same if you're having these problems

Good luck

Jackz

Sponge Bob wrote: »

BT ADSL2 LLU which is what you have Jackz will always try to adapt conditions to peg the margin at 6db so it could be a transient that catches them out before they can adapt the speed / margin metrics .

Other dsl users in the area can create noise on the line through crosstalk .

Is it once a day at 8pm and only then ??

Sorry was away from where I have this connection, the connection is disconnecting daily at 19:30, regardless of what I am doing the connection disconnects. I am prompted on the router homepage to reconnect. This make this useless for use with VOIP, leaving a download etc.

Bohrio

Jackz wrote: »

Sorry was away from where I have this connection, the connection is disconnecting daily at 19:30, regardless of what I am doing the connection disconnects. I am prompted on the router homepage to reconnect. This make this useless for use with VOIP, leaving a download etc.

I thought it was common knowledge but BT disconnects all their customers every 24 h, the problem with reconnection is due to your voyager and noise on your line coming from your internal wiring.

I have seen several posts around with people with this issue

Jackz

Bohrio wrote: »

and noise on your line coming from your internal wiring.

Why would noise from internal wiring be the problem? It connects fine at all other times apart from when it's reset by BT?

I only have it a few weeks so they are shipping them not to reconnect after the line is reset?

jayflame

Jackz wrote: »

Sorry was away from where I have this connection, the connection is disconnecting daily at 19:30, regardless of what I am doing the connection disconnects. I am prompted on the router homepage to reconnect. This make this useless for use with VOIP, leaving a download etc.

Hi,

I had a problem with this affecting my usage, router was going through its 24hr connection refresh whilst I was online, then I used to get the error "cannot find server".
I was advised to power cycle my router when least using. I did this in the morning before going to work and have no problems since.
Fingers X'd

Bohrio

Jackz wrote: »

Why would noise from internal wiring be the problem? It connects fine at all other times apart from when it's reset by BT?

I only have it a few weeks so they are shipping them not to reconnect after the line is reset?

When I had BT I also used their Voyagers. Using a specific tool I managed to get the following logs: (will show just a few excerpts as the whole log is a bit too long)

The first one is from a successful PPPoE connection on my neighbors with a Voyager 2110 v3.63:

Oct 31 12:48:26 192.168.1.1 pppd[488]: PPP: Start to connect ...
Oct 31 12:48:27 192.168.1.1 pppd[488]: Sent packet: Ether addr: ff:ff:ff:ff:ff:ff (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0xa7 sid=0x0000 length=0x000c (PADT) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 10 04 61 00 PPPoE tag: type=0101 length=0000 (Service name)
Oct 31 12:48:28 192.168.1.1 pppd[488]: Sending PADI
Oct 31 12:48:28 192.168.1.1 pppd[488]: Sent packet: Ether addr: ff:ff:ff:ff:ff:ff (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x09 sid=0x0000 length=0x000c (PADI) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 10 04 61 00 PPPoE tag: type=0101 length=0000 (Service name)
Oct 31 12:48:28 192.168.1.1 pppd[488]: Recv'd packet: Ether addr: 00:19:55:cc:e5:3c (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x07 sid=0x0000 length=0x002e (PADO) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 10 04 61 00 PPPoE tag: type=0101 length=0000 (Service name) P
Oct 31 12:48:28 192.168.1.1 syslog: ebtables -F INPUT
Oct 31 12:48:28 192.168.1.1 pppd[488]: HOST_UNIQ successful match
Oct 31 12:48:28 192.168.1.1 pppd[488]: Got connection: 29b3
Oct 31 12:48:28 192.168.1.1 pppd[488]: PPPoE Session Established
Oct 31 12:48:28 192.168.1.1 pppd[488]: Connecting PPPoE socket: 00:19:55:cc:e5:3c 29b3 nas_8_35 0x10046100
Oct 31 12:48:28 192.168.1.1 pppd[488]: using channel 1
Oct 31 12:48:28 192.168.1.1 pppd[488]: Using interface ppp8_35_1
Oct 31 12:48:28 192.168.1.1 pppd[488]: Connect: ppp_8_35_1 <--> nas_8_35


Second one is the same type of router in my house, same time:

Oct 31 12:53:34 192.168.1.1 pppd[488]: PPP: Start to connect ...
Oct 31 12:53:36 192.168.1.1 pppd[488]: Sent packet: Ether addr: 00:19:55:cc:e5:3c (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0xa7 sid=0x29b3 length=0x000c (PADT) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 10 04 61 00 PPPoE tag: type=0101 length=0000 (Service name)
Oct 31 12:53:36 192.168.1.1 pppd[488]: Sent packet: Ether addr: 00:19:55:cc:e5:3c (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0xa7 sid=0x29b3 length=0x000c (PADT) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 10 04 61 00 PPPoE tag: type=0101 length=0000 (Service name)
Oct 31 12:53:36 192.168.1.1 pppd[488]: Sending PADI
Oct 31 12:53:36 192.168.1.1 pppd[488]: Sent packet: Ether addr: ff:ff:ff:ff:ff:ff (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x09 sid=0x0000 length=0x000c (PADI) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 10 04 61 00 PPPoE tag: type=0101 length=0000 (Service name)
Oct 31 12:53:36 192.168.1.1 pppd[488]: Recv'd packet: Ether addr: 00:19:55:cc:e5:3c (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x07 sid=0x0000 length=0x002e (PADO) PPPoE tag: type=0101 length=0000 (Service name) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 10 00 90 00 P
Oct 31 12:53:36 192.168.1.1 pppd[488]: HOST_UNIQ mismatch: 10009000 %i
Oct 31 12:53:36 192.168.1.1 pppd[488]: Failed to negotiate PPPoE connection: 2 No such file or directory
Oct 31 12:53:36 192.168.1.1 pppd[488]: Exit.

The router is sending a HOST_UNIQ of 10 04 61 00 but is receiving a 10 00 90 00,

The main reason why v3.63 creates this error is not yet know but it is likely to do with the TR069 protocol in conjunction with noise. Of all the tests that have been carried out, "so I have been told", the only common denominator is houses with an open connection on the far end and high noise. Most of the times the person affected has an alarm or a microfilter connected to an extension or sky, or all of them. Sometimes is just even a faulty socket, but always something internal and not line related.

The solution is to either change to an older fm (no TR069) version or to get a different brand, BT should have a few DLINKs or Zyxels lying around.

however this is just an opinion... I ended up buying a linksys router so I didnt bother looking for a solution anymore...