Be Disconnections

kmufc77 · 19 Oct 2009 at 20:59

Hi im with BE Broadband and keep getting random disconnections that last around 1-3 mins been happening quiet often in the last 2 months has anyone else had any issues? That have been a brilliant isp upto now.

AbsenceJam · 19 Oct 2009 at 21:44

Disconnections are a issue at your end. Try changing your profile in the member centre.

kmufc77 · 19 Oct 2009 at 21:56

AbsenceJam said:
Disconnections are a issue at your end. Try changing your profile in the member centre.

can you explain what you mean please?

petemyster · 19 Oct 2009 at 22:05

kmufc77 said:
can you explain what you mean please?

check your router logs as soon as you connect back from the disconnects. Does it say "kernel warm restart", and does it also complain your DSL is down? If so, i've been stuck with this problem ever since I switched to BE who were apparently awesome, but in my case the 2nd router replacement i've got, still does repeated Kernal Warm Restarts.

AbsenceJam · 19 Oct 2009 at 22:29

kmufc77 said:
can you explain what you mean please?

Phone lines and other wiring are very subject to all manner of interference that can occur at different times and be caused by all sorts of things. Be are good about letting you maximise your synch speed but sometimes you need a more conservative SNR profile or to disable fastpath so you don't get disconnected during line fluctuations. You can play with this in the member centre.

Or it could be the above if you haven't seen that it is an actual disocnnection, the Speedtouch routers they supply are pretty poor and a little unstable. I ditched mine for a DG834GT years ago.

Five_Star · 20 Oct 2009 at 08:12

kmufc77 said:
Hi im with BE Broadband and keep getting random disconnections that last around 1-3 mins been happening quiet often in the last 2 months has anyone else had any issues? That have been a brilliant isp upto now.

I'm with o2 (although my IP is tagged as Be) and this has been happening at night for me. In Tomato I can watch the bandwidth graph go from max when a download is running, drop to zero for 1-2 minutes then continue back up to max again.

I’m using a AM200 fully bridged to a WRT54G and its previously been solid for over a year.

I work from home during the day and haven't experienced any of these drop outs 9-5, its only at night and weekends. Sunday night is especially poor both in terms of speed and dropouts.

Interestingly I have noticed that my max download speed has gone up very slightly from 1.1MB to 1.3MB so syncing that little bit higher must be causing the issue.

I’m too lazy to phone o2 to investigate and as far as I’m aware o2 don’t have a customer portal like Be* do?

Interesting that somebody else has reported this although how much of it is down to lines trying to sync at their absolute maximum and coincidence is unclear.

Xinn · 20 Oct 2009 at 08:17

Also happens to me on Be. Once every couple of days, tend to be around 9:30 - 9:30 PM when I happens but not always.

Rather annoying I must say.

XeNoN89 · 20 Oct 2009 at 15:54

I was getting multiple disconnects pretty much every day for around 2 months at the beggining of the year, it has been fine since then though, we never found out what caused it.

YoungBlood · 20 Oct 2009 at 16:08

I had a similar issue, BE raised my noise margin considerbly for me and all is fine and dandy now. I do have some terrible DNS issues lately though. Ebay, Google, etc all taking very long to connect.

Lost a few mb but I will take stability over speed anyday.

kmufc77 · 20 Oct 2009 at 16:13

Thanks guys for your suggestions,would getting a N series router improve any connection issues?

markyb · 20 Oct 2009 at 16:22

I've been getting the same for a couple of days since I joined BE, at first I thought it might be my line. But after heading over to the BE forums, it seems quite a few people are having the same issue.

Mines been getting better. It could also be down to the profile. You can set your profile if you log in via their website. There are three profiles :- Standard, Speed and Stable.

kmufc77 · 20 Oct 2009 at 16:33

markyb said:
I've been getting the same for a couple of days since I joined BE, at first I thought it might be my line. But after heading over to the BE forums, it seems quite a few people are having the same issue.

Mines been getting better. It could also be down to the profile. You can set your profile if you log in via their website. There are three profiles :- Standard, Speed and Stable.

im logged in now to my Be account but cant see any option for profile?

EDIT: Found it

Five_Star · 20 Oct 2009 at 17:10

kmufc77 said:
Thanks guys for your suggestions,would getting a N series router improve any connection issues?

No, it won't do a thing.

Getting a decent quality filtered faceplate for your master socket will (XTE-2005 springs to mind)

Axil · 20 Oct 2009 at 18:37

Actually the disconnects on Be's service are happening to a lot of people around the country and this seems to have started recently so it's unlikely to be totally the line

Nocky24 · 20 Oct 2009 at 20:38

YoungBlood said:
I had a similar issue, BE raised my noise margin considerbly for me and all is fine and dandy now. I do have some terrible DNS issues lately though. Ebay, Google, etc all taking very long to connect.

Lost a few mb but I will take stability over speed anyday.

Nice attenuation there mate

I'd imagine you'd get a higher sync than that looking at your snr. What package are you on?

Thunderbolt · 20 Oct 2009 at 22:08

Getting the same issue with O2 the last few days, has been driving me mad.

Been checking back in this section a lot waiting for this thread to turn up

kmufc77 · 20 Oct 2009 at 22:26

Five_Star said:
No, it won't do a thing.

Getting a decent quality filtered faceplate for your master socket will (XTE-2005 springs to mind)

Hi can you explain a little more will i have to buy different cable aswell or simply attach the cable trough the XTE-2005 sorry to be dumb

Windle · 20 Oct 2009 at 23:06

Try running these and see what you get...

Go to Start -> Run -> cmd.exe

-Please go to Start/Run, type cmd
Type ping bbc.co.uk -n 50
Please copy and update us with the final result.

- Please go to Start/Run, type cmd
Type tracert bbc.co.uk
Please copy and update us with the final result.

- Please go to Start/Run, type cmd
Type ping www.google.com -n 50
Please copy and update us with the final result.

- Please go to Start/Run, type cmd
Type tracert www.google.com
Please copy and update us with the final result.

I'm having problems with my Be line atm, just raised a ticket myself actually.

BBC Ping:-

Ping statistics for 212.58.224.138:
Packets: Sent = 50, Received = 31, Lost = 19 (38% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 35ms, Average = 33ms

BBC Tracert:-

C:\>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 11 ms 99 ms 99 ms bebox.config
2 * * * Request timed out.
3 * * * Request timed out.
4 * * bebox.config [192.168.1.254] reports: Destination host u
nreachable.

Trace complete.

C:\>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 21 ms 99 ms 99 ms bebox.config
2 * * * Request timed out.
3 * 35 ms 34 ms 10.1.2.169
4 36 ms 35 ms 35 ms 93-126-245-83.packetexchange.net [83.245.126.93]

5 35 ms 34 ms 34 ms 212.58.238.129
6 35 ms 34 ms 33 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Google Ping:-

Ping statistics for 209.85.227.105:
Packets: Sent = 50, Received = 26, Lost = 24 (48% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 41ms, Average = 40ms

Google Tracert:-

Tracing route to www.l.google.com [209.85.229.103]
over a maximum of 30 hops:

1 59 ms 99 ms 99 ms bebox.config
2 * * * Request timed out.
3 * * * Request timed out.
4 * 34 ms 34 ms 87-194-0-206.bethere.co.uk [87.194.0.206]
5 * 35 ms 35 ms 64.233.175.27
6 * 41 ms 42 ms 66.249.95.170
7 40 ms 40 ms 41 ms 72.14.236.191
8 43 ms 44 ms 54 ms 209.85.243.81
9 43 ms 41 ms 41 ms ww-in-f103.1e100.net [209.85.229.103]

Trace complete.

kmufc77 · 21 Oct 2009 at 00:14

BBC

Ping statistics for 212.58.224.138:
Packets: Sent = 50, Received = 49, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 29ms, Average = 27ms

Goggle

Ping statistics for 209.85.229.106:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 36ms, Average = 34ms

Ping statistics for 209.85.229.106:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 36ms, Average = 34ms

C:\Windows\system32> tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 6 ms 99 ms 99 ms bebox.config [192.168.1.254]
2 29 ms 29 ms 28 ms Unknown-00-00-5e-00-01-0a.config [93.97.241.1]
3 * * * Request timed out.
4 29 ms 29 ms 29 ms bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.
3]
5 29 ms 29 ms 29 ms 212.58.238.153
6 30 ms 28 ms 28 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

Azuse05 · 21 Oct 2009 at 00:36

If you opend something like, say, the free version of ping plotter you'd realise that there's always loss on the first couple hops.

There's a stick FAQ on the forum explaining that they give traceroutes low priority which is always displayed as packetloss on those hops.