Client on IDNet with line issues

Started by jameshurrell, May 30, 2014, 10:25:22

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

jameshurrell

I have a client who has at best a piece of wet string for their internet connection - supplied via IDNet. They are located at the boundary of two exchanges and their line is long. I am trying to help them stabilize the connection to where it is usable at best and could do with some advice. I've also posted this in the Kitz ADSL forum as their are some techies lurking in there...

They had a TP-Link router in place for some time, but gradually the connection got so bad with multiple disconnects that I have now removed this and replaced it with a DGN2200v3. Since this router was installed last night, the connection has been better, however, it disconnects every 30 minutes (pretty much exactly) for a few seconds, which is something I have never seen before.

DGN2200 log:

[Internet connected] IP address: , Friday, May 30,2014 08:45:05           
[DSL: Up] Friday, May 30,2014 08:44:59             
[Internet disconnected] Friday, May 30,2014 08:44:52             
[DSL: Down] Friday, May 30,2014 08:44:47
....
[Internet connected] IP address: , Friday, May 30,2014 08:12:56           
[DSL: Up] Friday, May 30,2014 08:12:51             
[Internet disconnected] Friday, May 30,2014 08:12:43             
[DSL: Down] Friday, May 30,2014 08:12:38
...
[Internet connected] IP address: , Friday, May 30,2014 07:42:42           
[DSL: Up] Friday, May 30,2014 07:42:37             
[Internet disconnected] Friday, May 30,2014 07:42:29             
[DSL: Down] Friday, May 30,2014 07:42:24
...
[Internet connected] IP address: , Friday, May 30,2014 07:14:43           
[DSL: Up] Friday, May 30,2014 07:14:38             
[Internet disconnected] Friday, May 30,2014 07:14:30             
[DSL: Down] Friday, May 30,2014 07:14:25             

Slight blip here:

[Internet connected] IP address: , Friday, May 30,2014 07:12:34                       
[DSL: Up] Friday, May 30,2014 07:12:29             
[Internet disconnected] Friday, May 30,2014 07:12:21             
[DSL: Down] Friday, May 30,2014 07:12:16
...
[Internet connected] IP address: , Friday, May 30,2014 06:44:37           
[DSL: Up] Friday, May 30,2014 06:44:31             
[Internet disconnected] Friday, May 30,2014 06:44:24             
[DSL: Down] Friday, May 30,2014 06:44:19

And so on... The router appears to re-sync because the sync speed is different when it comes back up. Any idea what could cause that? I assume that this is some sort of interference on the line, but so regularly is odd to say the least.

I have RouterStats running now and it seems that just before the connection drops, the Downstream noise margin plummets - I assume this is causing the disconnect? here is the downsteam noise graph:



This is a simple ADSL2+ connection. Current router stats:

                 ADSL Link                      Downstream                Upstream                             
                 Link Rate                      2080 Kbps                   448 Kbps                             
                 Line Attenuation            50.5 dB                      30.0 dB                             
                 Noise Margin                 15.3 dB                      17.0 dB       

TP-Link was reporting line attn. of 61, but I know that routers report things differently.

Internal wiring is a bit of a mess, which probably isn't helping:

Master socket upstairs with nothing connected > extension cable to outside to kitchen with small extension socket (router connected here with filter, but no phone) > additional extension cable joined here and that continues to an office where it is split (I don't know how as it is in the wall) into 2 further sockets (one has a fax and phone via a filter, the other has just a phone via a filter).

Looking at the socket in the kitchen where the router is connected, all 4 wires were connected, so I have removed wires 3 and 4 to leave 2 and 5. In the office, one extension socket also had 4 wires connected, so I have again removed wires 3 and 4 - the other socket is currently inaccessible. The master socket is also inaccessible (currently) and have not touched this (yet). Client cannot plug router into Master socket as this is at one end of the house and wifi does not extend far enough.

My next step is to remove wires 3 and 4 from the third extension socket and also from the master socket. Then temporarily connect router to test socket at master socket to rule out extension.

I'm half wondering if there is a line fault in play here as well.
Any pointers gratefully received.

PS: Just had another half hour disconnect.. but this time the router was not able to reconnect by itself. It required a hard reboot. Downstream noise plummeted....


Steve

My impression is until you've disconnected the additional wiring at the master socket or run from the test socket there, it's difficult to say. It would obviously be great if just running 2 and 5 on the master solved the issue.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

nowster

Separate router on master socket and separate access point where it's needed, interconnected using ethernet. Filter (plate type) on master socket, with all extensions behind the filter.

Most likely to be something electrical inside the house that's interfering, and perhaps "flat cable" internal extension wiring.

Attenuation shows that the line is capable of 4Mbps or more, but the noise margin has been cranked up to improve the reliability.

jameshurrell

Thanks both, this is exactly what I suspect.

My plan is to first remove wires 3 and 4 from master socket and see if that resolves it (yes Steve, this would be a good result). If not, then as you suggest nowster, I connect the router to the test socket and see if it stabilizes. If it does, yes, next step is to leave router in room with master socket and feed ethernet down to the other end of the house and attach a WAP.

Gary

I think although I could be wrong that Simon had issues with a DGN2200v3. Anyway they are known to have some connection issues, whether that's been cured now who knows, but google will lead the way.
Damned, if you do damned if you don't

Simon

Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

RandomGeeza

Quote from: Gary on May 31, 2014, 08:43:57
I think although I could be wrong that Simon had issues with a DGN2200v3. Anyway they are known to have some connection issues, whether that's been cured now who knows, but google will lead the way.

Likewise, I did too... Not the most reliable of units.

Simon

Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.