The connection was reset

kwikbreaks

OK on the alarm sensors being wireless. I used to have a wireless alarm at my previous house and it caused no problems but it wasn't wired into the phone system.

If there is something in your house creating local noise let's hope the faceplate filters it out.

One thing you can easily do now that you realise there is no need to power cycle the router to check the stats is to check it next time you get the connection reset error and see if it has just resynced although we can't be 100% sure the connection time does reset if it does as you've been power cycling it.

J_B

I just opened about 6 tabs on another forum and one gave the error message.

Stats here


or would you prefer the copy paste stuff?

J_B

Today I was reading a webpage when suddenly - "The connection was reset"
I immediately checked the sats - results here


The faceplate has arrived, will try and fit it tomorrow ....

kwikbreaks

Well the post from the first had gone negative noise margin so getting errors then doesn't surprise me.

The second set of stats show a changed sync but it looks like the uptime wasn't reset and it's just the router uptime not the connection uptime. I'm surprised that the noise margin exceeds the target as that suggests it hasn't just resynced unless there was a longish burst of interference that cleared after sync was established.

As the uptime isn't since the last sync it's all guesswork. Lets hope the faceplate sorts it. Still worth trying the alternate router even if it does become stable though as it may perform better - downside is you'll heed to set it up with your login and also setup the WiFi the same as you have now if you don't want to have to reconnect everything to the new WiFi setup.

J_B

kwikbreaks wrote: »

Lets hope the faceplate sorts it.

Just fitted it - didn't reboot router, should I have done/??

kwikbreaks wrote: »

Still worth trying the alternate router

I hope it will arrive tonight, but probably won't get time to try it till next week

kwikbreaks

Well you should have shut down the router before messing with the phone wiring. It looks like not doing so has possibly earned you a 12dB target margin as that is what it is currently sitting on. The good news is that even with that 12dB margin (assuming it is) you are syncing as fast as the better of the earlier ones.

Bit too soon to say for sure but it suggests that the previous filtering wasn't any too hot and this may have fixed that. If it has you should have a stable connection now and the target margin will very slowly head back to the default 6dB and you top speed will go up to nearer what you'd expect the attenuation to support.

J_B

kwikbreaks wrote: »

Well you should have shut down the router before messing with the phone wiring.

Whoops
Sorry!

kwikbreaks wrote: »

. If it has you should have a stable connection now and the target margin will very slowly head back to the default 6dB and you top speed will go up to nearer what you'd expect the attenuation to support.

Stats just now

Speedtest results


I will have time tomorrow to try the spare router - it's a plusnet branded "technicolour TG582n"

Will investigate and post results

Many thanks :T

kwikbreaks

Unfortunately the sync rate has changed so it must have resynced since the earlier post.

Lets hope the alternate router fares better.

J_B

OK
New router fitted and working
I set it all up and then went out for about an hour to let it settle and came back with these stats

I think the first line says 'uptime' of 26 minutes, but I'd been out of the house for about an hour. Nobody else is here and the power hadn't been off.

Just tinkered with the wires now so had to unplug and stats now showing thus ... (wow, I can copy and paste from this router!!)
[EDIT - well, it looked ok in the preview! ]



Uptime:0 days, 0:09:55 DSL Type:ITU-T G.992.1 Bandwidth (Up/Down) [kbps/kbps]:448 / 4.512 Data Transferred (Sent/Received) [MB/MB]:1,29 / 7,26 Output Power (Up/Down) [dBm]:12,3 / 19,8 Line Attenuation (Up/Down) [dB]:25,5 / 42,5 SN Margin (Up/Down) [dB]:21,0 / 12,3 System Vendor ID (Local/Remote):TMMB / ---- Chipset Vendor ID (Local/Remote):BDCM / TSTC Loss of Framing (Local/Remote):0 / - Loss of Signal (Local/Remote):0 / - Loss of Power (Local/Remote):0 / - Loss of Link (Remote):- Error Seconds (Local/Remote):0 / - FEC Errors (Up/Down):0 / 21 CRC Errors (Up/Down):0 / 0 HEC Errors (Up/Down):- / 0 / 0


and speedtest says

Don't think we've ever had over 3 before!

kwikbreaks

I noticed these things...

Bandwidth (Up/Down) [kbps/kbps]:448 / 4.51
That's about the fastest sync we've seen.

Line Attenuation (Up/Down) [dB]:25,5 / 42,5
The reported attenuation anomaly pointed out by Gunjack has gone suggesting it was just an artefact of the old router's reporting.

SN Margin (Up/Down) [dB]:21,0 / 12,3
It looks like you do have a 12dB target now. That will eventually heal itself but will take weeks. You may want to ask your ISP if they can reset it now that you have fitted a filtered faceplate. I think you said it was Plusnet - if so their forum is best bet for that - just explain about the new faceplate and ask if they can reset your profile to defaults. You may need to register - http://community.plus.net/forum/index.php

These error stats are worth keeping an eye on....

Loss of Signal (Local/Remote):0 / -
Loss of Power (Local/Remote):0 / -
Loss of Link (Remote):-
Error Seconds (Local/Remote):0 / -
FEC Errors (Up/Down):0 / 21
CRC Errors (Up/Down):0 / 0
HEC Errors (Up/Down):- / 0 / 0

Speedtouch/Thomson routers have a reputation for reporting a ridiculously high number of FEC errors. That one may not. In any event they are all corrected errors so have a lot less impact than CRC errors.

I'm hopeful. Take a look at the stats late evening (without rebooting).