Threaded Mode | Linear Mode

TTM13 · 04-03-2013, 03:56 PM

Hi,
As of this month I've been on DR for a year. Ever since the first day I've had constant disconnects - the longest I have ever gone has been 4 1/2 days without being disconnected. It is incredibly frustrating when it boots me off in an evening

Has anyone else had this problem before? It looks as though Origin don't know what is causing it. I email them every few days to notify them of disconnects and they just run their 24hr line tests again.

Could it be hardware? Would using a Huewei modem to replace the Cellpipe do anything?

Getting fed up of it to be honest.

bgnx · 04-03-2013, 04:12 PM

You're gonna have to provide more info than that..

First things first, is it the DSL that is disconnecting? i.e. does the DSL light on the cellpipe go off/start flashing when you have problems?

If no, then likely router problem - Do your router logs suggest anything in particular? Test with another router or test by connecting a computer direct to cellpipe and set up a PPPoE connection to your ISP. Also possibly test with a different patch cable between cellpipe and your equipment.

If DSL is dropping, the likely a line issue, internal cabling or possible faulty cellpipe - Plug cellpipe direct to test socket behind faceplate of the BT master socket (this rules out any of your internal cabling.), possibly test with new cable between test socket and router. If the problem stops, then its internal cabling/setup. If the problem persists, then ISP should be able to have line tested to look for anything out of the ordinary.

Is there a pattern to the disconnects? Certain times of the day? Do the drops happen when the phone rings or anything like that?

tekmobile · 04-03-2013, 04:14 PM

(04-03-2013 03:56 PM)TTM13 Wrote: Hi,
As of this month I've been on DR for a year. Ever since the first day I've had constant disconnects - the longest I have ever gone has been 4 1/2 days without being disconnected. It is incredibly frustrating when it boots me off in an evening

Has anyone else had this problem before? It looks as though Origin don't know what is causing it. I email them every few days to notify them of disconnects and they just run their 24hr line tests again.

Could it be hardware? Would using a Huewei modem to replace the Cellpipe do anything?

Getting fed up of it to be honest.

How is your line constant disconnects are normally due to line faults.

My line has been incredibly stable I don't recall any disconnections although I'm with LBO

TTM13 · 04-03-2013, 04:39 PM

Hi, I've tested with two routers - the Tenda it came with and the Linksys I'm currently using - made no difference. I've connected my PC directly through the Cellpipe in the past and it still did it, so it's something from the Cellpipe onwards.

The Cellpipe is right next to the master socket and has been plugged into the test socket for months also. I have checked the lights on the Cellpipe in the past but have forgotten what lights are on/off, will have to check next time. I've also used two different cables between the Cellpipe and socket which has made no difference.

Line seems fine for voice, not crackly or anything. Any others tests I could do for line quality?

Unfortunately there's no pattern to the disconnects. It could go four days and be stable, then get four disconnects within a few hours of each other. It does it at any time, in any weather. Never had it d/c when someone phones though.

**mirdragon** · 04-03-2013, 05:33 PM

Have you tried different cable from modem to master socket?

What have Origin or Thales said?

This seems very similar to what was happening to me, which in turn forced me to leave the network

bgnx · 04-03-2013, 05:58 PM

In that case -

(04-03-2013 05:33 PM)mirdragon Wrote: What have Origin or Thales said?

**mirdragon** · (This post was last modified: 04-03-2013 07:50 PM by mirdragon.)

I was with ripwire at the time and both tried blaming my hardware and line. As soon as moved back to bt not had any the issues using same line and hardware. Only difference is no cellpipe.

What have Origin/Thales done to help diagnose the problem

Have they put another box on the line to help diagnose or put monitoring equipment on it

Hopefully your issue is totally different to the issues I had and may get resolved, but after more than a year with the issues and getting nowhere fast I decided to take the plunge and leave DR and move back to BT.

alexatkin · (This post was last modified: 04-03-2013 08:45 PM by alexatkin.)

I wouldn't count on it not being the same issue. I am still monitoring my connection as it has periods of the PPP session dropping a lot, and just when I start to worry about it the problem will go away for a week or two.

Example:

                      Code:

                      Jan 23 03:13:37 Router daemon.info pppd[26700]: Connect time 11.9 minutes.

                      Jan 23 03:34:04 Router daemon.info pppd[2970]: Connect time 7.0 minutes.

                      Jan 23 20:45:37 Router daemon.info pppd[2970]: Connect time 1030.9 minutes.

                      Jan 23 20:45:40 Router daemon.info pppd[2970]: CHAP authentication succeeded: Welcome.

                      Jan 24 21:34:37 Router daemon.info pppd[2970]: Connect time 1489.0 minutes.

                      Jan 24 21:35:34 Router daemon.info pppd[2970]: CHAP authentication succeeded: Welcome.

                      Jan 26 23:34:51 Router daemon.info pppd[2962]: CHAP authentication succeeded: Welcome. (Router Reboot)

                      Jan 29 17:59:22 Router daemon.info pppd[2962]: Connect time 4044.5 minutes.

                      Jan 29 17:59:46 VDSL Sync, Downstream 69993, Upstream 28846, Synced for 7 seconds.

                      Jan 29 17:59:46 Router daemon.info pppd[2962]: CHAP authentication succeeded: Welcome.

                      Jan 31 15:17:07 Router daemon.info pppd[2962]: Connect time 2717.4 minutes.

                      Jan 31 15:17:13 VDSL Sync, Downstream 69993, Upstream 28846, Synced for 163055 seconds.

                      Jan 31 15:17:13 Router daemon.info pppd[2962]: CHAP authentication succeeded: Welcome.

                      Feb  3 16:56:14 Router daemon.info pppd[2962]: Connect time 4419.1 minutes.

                      Feb  3 16:56:20 VDSL Sync, Downstream 69993, Upstream 28846, Synced for 428204 seconds.

                      Feb  3 16:56:20 Router daemon.info pppd[2962]: CHAP authentication succeeded: Welcome.

                      Feb  4 21:42:39 Router daemon.info pppd[2962]: Connect time 1726.4 minutes.

                      Feb  4 21:42:50 VDSL Sync, Downstream 69993, Upstream 28846, Synced for 531795 seconds.

                      Feb  4 21:42:50 Router daemon.info pppd[2962]: CHAP authentication succeeded: Welcome.

                      Feb  4 22:05:12 Router daemon.info pppd[2962]: Connect time 22.4 minutes.

                      Feb  4 22:06:03 VDSL Sync, Downstream 69993, Upstream 28846, Synced for 533188 seconds.

                      Feb  4 22:06:03 Router daemon.info pppd[2962]: CHAP authentication succeeded: Welcome.

                      Feb  5 18:20:24 Router daemon.info pppd[2962]: Connect time 1214.4 minutes.

                      Feb  5 18:21:15 VDSL Sync, Downstream 69993, Upstream 28846, Synced for 606101 seconds.

                      Feb  5 18:21:15 Router daemon.info pppd[2962]: CHAP authentication succeeded: Welcome.

                      Feb 25 00:55:31 Router daemon.info pppd[2962]: Connect time 27754.3 minutes.

                      Mon 25 01:02:18 VDSL SYNC STATUS: Downstream 69993, Upstream 29872, Synced since Mon Feb 25 01:02:19 2013.

                      Feb 25 01:02:19 >

                      Feb 25 01:02:27 Router daemon.info pppd[10370]: CHAP authentication succeeded: Welcome.

                      Feb 27 18:09:13 Router daemon.info pppd[10370]: Connect time 3906.8 minutes.

                      Feb 27 18:09:14 VDSL SYNC STATUS: Downstream 69993, Upstream 29365, Synced since Wed Feb 27 18:09:39 2013.

                      Feb 27 18:09:39 >

                      Feb 27 18:09:40 Router daemon.info pppd[10370]: CHAP authentication succeeded: Welcome.

                      Feb 27 20:05:48 Router daemon.info pppd[10370]: Connect time 116.2 minutes.

                      Feb 27 20:05 VDSL SYNC STATUS: Downstream 69993, Upstream 29365, Synced since Wed Feb 27 18:09:39 2013.

                      Feb 27 20:05:54 Router daemon.info pppd[10370]: CHAP authentication succeeded: Welcome.

                      Mar  3 21:26:47 Router daemon.info pppd[10370]: Connect time 5840.9 minutes.

                      Mar  3 21:26 VDSL SYNC STATUS: Downstream 69993, Upstream 29365, Synced since Wed Feb 27 18:09:36 2013.

                      Mar  3 21:26:53 Router daemon.info pppd[10370]: CHAP authentication succeeded: Welcome.

I have noticed though that usually if mine goes really wonky, forcing the line to resync will fix it.
eg:

                      Code:

                      Dec 23 00:04:43 Router daemon.info pppd[20652]: Connect time 207.6 minutes.

                      Dec 23 00:22:15 Router daemon.info pppd[20652]: Connect time 17.5 minutes.

                      Dec 23 00:35:34 Router daemon.info pppd[20652]: Connect time 13.3 minutes. (Forced VDSL Resync)

                      Jan  4 23:29:28 Router daemon.info pppd[20652]: Connect time 18653.6 minutes.

So I think its at least partly related to them pushing my upstream a little bit too hard. Its annoying as I daren't ask them to scale it down as they will probably just stick interleaving back on or knock 10Mbit off my line, when all it needs is the SNR setting a tiny bit higher.

@TTM13 Were you with Origin before they switched to PPPoE? Because I didn't noticed any problems myself until they made the switch, but then its hard to know before then as any problems would have just shown as temporary glitches in web access.

**mirdragon** · 04-03-2013, 08:56 PM

it is bad, if it's still going on like this - i've been left the network for over a year now and tbh I don't think i would switch back - i made some changes to my router a month ago and bt done some work on our cabinet and it's still connected - now up 28 days - it will probably go down tomorrow or wednesday as i'm changing my package with BT and switching to the unlimited (unthrottled) connection and I'll also get 50GB of free cloud storage.

I use snmpsoft syslogger which my router forwards all events too, which helps if anything goes wrong, but i tend not to monitor it as much as i did when on the DR network as there is no longer the need to do so.

alexatkin · 04-03-2013, 10:36 PM

Like I said, I think the problem lies with the static profiles Digital Region have.

They are working on a "one size fits all" premise and that is utterly useless. It means you either push your line too hard and get some instability, or don't push it hard enough and lose out on speed and/or latency.

I wouldn't say its enough to leave, but its certainly far from ideal.