In reply to a post by ukhardy07:

Monitor that time connected like a hawk

along with Loss of Signal & Error Secs.

I have noticed it is usually when one of two different computers are online. Sometimes it's fine but when they are on there seems to be a higher chance of all this occurring. We do also have a high amount of devices connecting to the network on a regular basis. What can be done about that?

UP DOWN

Loss of Signal Defect 0 0
Error Seconds 13859 493

Time Connected: 06:02:06

Current time is 3:28 pm

so it would have reset last at about 9 am, which makes sense because most of my housemates either went to uni or work around that time. At the minute just my imac and phone connected

How many devices are we talking about at once being on the wifi, including phones, wifi printers, tvs, sky boxes, xboxes, play stations, wii's etc? That would be a good indicator.

Is the connection uptime dropping or is that staying up?

Up to about 12 at peak times, the majority being phones, but there are some computers/laptops and an ipod in there, if that makes any difference.

It drops more when there are more people on, but can happen without that, like just now. I have my mac, an android phone and there is an ipod connected and the router restarted 10 minutes ago, so far it has stayed up though

Currently:

Data Rate Information
Stream Type Actual Data Rate
Upstream 708 (Kbps.)
Downstream 13331 (Kbps.)

Defect/Failure Indication
Operation Data Upstream Downstream
Noise Margin 6.2 dB 6.8 dB
Line Attenuation 12.3 dB 22.0 dB

Indicator Name Near End Indicator Far End Indicator
Output Power 12.2 dBm 21.0 dBm
Fast Path FEC Correction NA NA
Interleaved Path FEC Correction 37007183 958736
Fast Path CRC Error NA NA
Interleaved Path CRC Error 723428 3795
Loss of Signal Defect 0 0
Fast Path HEC Error STR NA NA
Interleaved Path HEC Error 40863307 10884
Error Seconds 14803 913
Statistics
Received Cells 11167490
Transmitted Cells 1177928

Sorry for posting all the info, not sure what might be needed here

The downstream speed is well below the 17800-19000 kbit/s predicted by MrSaffron's calculator. That alone implies there might be an internal wiring issue.

A good starting point would be to expose the test socket, check every extension socket has gone dead using a phone (sometimes there's extension wiring that isn't connected via the NTE5 faceplate), connect the router to the test socket and post the statistics. To ensure all the counters reset, it might be a good idea to switch the router off before connecting it to the test socket, then switch it back on after connecting it to the test socket.


Whilst it's hard to judge the number of error seconds without an uptime, there are many more upstream error seconds than downstream.

Dropped again after 18 minutes up, still no new devices connected

The landlord tested all the wiring to see which was actually live, and the one we are using was supposedly the only one in the house. He idd this shortly after I moved in (the house was newly bought and listed when I moved in)

Should I get him round to do another check?

I have a feeling that the net seems to be even more unpredictable when one of two computers connect, both belonging to other housemates. Could something on their end be making the problem worse?

In reply to a post by Connarhea:

The landlord tested all the wiring to see which was actually live, and the one we are using was supposedly the only one in the house. He idd this shortly after I moved in (the house was newly bought and listed when I moved in)

Should I get him round to do another check?

Any live extension wiring has the potential to affect DSL performance, especially if the wiring uses non-twisted pair cable, the pairings on twisted pair cable are wrong or the bell wire is connected. If you move the router to the master socket and disconnect the faceplate to expose the test socket, you will likely isolate all the internal wiring, though you should verify that every extension socket is dead rather than assuming it is.


By testing in the test socket, you can tell whether the issue is in internal wiring (the landlord's responsibility) or external wiring (which is a fault that needs reporting to the voice provider if it affects voice calls, and to EE if it does not).

Having the statistics from the test socket compared to the usual location is the only way to figure out where the issue lies and whose responsibility it is. Without the test socket statistics as a comparison, we're just guessing. I'm not suggesting you start rewiring the place, just exposing the test socket, testing, then carefully replacing the faceplate afterwards. If an internal wiring issue becomes apparent, it's then up to the landlord to get it fixed.

In reply to a post by Connarhea:

I have a feeling that the net seems to be even more unpredictable when one of two computers connect, both belonging to other housemates. Could something on their end be making the problem worse?

More than likely, the additional load they add to the connection causes errors to happen more often.

Sorry to keep posting but checking the error seconds by refreshing the ADSL status page, it seems to be (for the time being) going up at 1 error second per second, or at least very close to that.