Kitz Forum

Broadband Related => ADSL Issues => Topic started by: renluop on April 17, 2017, 01:22:14 PM

Title: Weekend was not good for me
Post by: renluop on April 17, 2017, 01:22:14 PM
weekend not good! Read attachment, please.
Title: Re: Weekend was not good for me
Post by: kitz on April 17, 2017, 07:25:13 PM
Have you tried a Quiet Line test?

Your QLN shows a few noise spikes at tone 190+
Your upstream SNRm is suffering the most...  usual culprits are internal wiring, faulty filters or a High Open.

The graphs shows signs not dissimilar to a HR fault.  Especially if the landline had rung or was in use at around 10:50.  The slow decline and then back up could be side effect of the whetting current.   Noise ingress on internal wiring could also display something similar though.

Title: Re: Weekend was not good for me
Post by: renluop on April 17, 2017, 10:51:29 PM
quickie
whetting current? not a term I've heard of. :-[
Title: Re: Weekend was not good for me
Post by: renluop on April 18, 2017, 08:21:51 AM
I looked it up this morning and now know what it is: whether I really understand is doubtful.
Quiet line tests are a bit of a problem: I hearing aids! I'll rake out my corded, but I'll still have that problem. There is no obvious noise, when using the cordless on full volume.

We did have a call, commencing 10:36 on 15th. As it was from my wife's brother, It would have been somewhat lengthy!

The previous owner had a hard wired extension through the cavity, vertically direct from the master socket to the room above, so no splitters et al.

Title: Re: Weekend was not good for me
Post by: renluop on April 19, 2017, 10:47:34 AM
I viewed the tone graph, FWIW, and found the spikes are at 192 , 211 and 244 (828, 909.9375 and 1056.5625 kHz). Is there anything significant about those? They seem to be pretty permanent.
Title: Re: Weekend was not good for me
Post by: roseway on April 19, 2017, 10:56:27 AM
Have a look at http://www.mediumwaveradio.com/uk.php . Those frequencies look like MW radio stations.
Title: Re: Weekend was not good for me
Post by: waltergmw on April 19, 2017, 12:05:31 PM
My test phone includes a high resistance connection button so often hear radio programs loud and clear when connected directly to the test socket.
It illustrates just how far we've managed to squeeze higher frequencies from the good old PSTN !

Kind regards,
Walter

Title: Re: Weekend was not good for me
Post by: tickmike on April 19, 2017, 02:06:00 PM
My test phone includes a high resistance connection button so often hear radio programs loud and clear when connected directly to the test socket.
It illustrates just how far we've managed to squeeze higher frequencies from the good old PSTN !

Kind regards,
Walter
Re..'high resistance' what sort of resistance value ?. :hmm:
Title: Re: Weekend was not good for me
Post by: renluop on April 19, 2017, 03:23:07 PM
Have a look at http://www.mediumwaveradio.com/uk.php . Those frequencies look like MW radio stations.
Thanks Eric!
I found a transmitter, that I had never hear of about 16 km SSW of me. thode are frequencies .where the spikes are

828   Classic Gold 828   Fern Barrow, Bournemouth           270W   

909   Radio 5 Live           Fern Barrow, Bournemouth         250W

1053   Talk Sport                   Fern Barrow, Bournemouth          1000W

1197   Virgin AM                   Fern Barrow, Bournemouth           250W

1359   R Solent for Dorset   Fern Barrow, Bournemouth           850W

Are they of any significance at all in the case of this thread?
Title: Re: Weekend was not good for me
Post by: roseway on April 19, 2017, 03:45:27 PM
They won't be responsible for the ups and downs of SNRM at the weekend. As Kitz said, the most likely culprit is an intermittent HR fault.

Whetting current refers to the fact that electric current passing through a poor joint can temporarily repair it. This can happen when someone rings you - the ringing signal causes extra current to flow, and the quality of the joint improves, but it doesn't last.
Title: Re: Weekend was not good for me
Post by: renluop on April 21, 2017, 08:54:18 PM
Got wife to listen for noise (her hearing is superior to mine) and she heard no noise. I've yet to use a corded though. Today the up margin has been jumping around like a kangaroo on heat, that sat on a hornets nest. There is quite a problem with DSL connection

Code: [Select]
21 Apr 2017 20:25:50 Recording started

21 Apr 2017 20:25:55 IP address is now 147.147.192.217
21 Apr 2017 20:33:51 DSL connection dropped
21 Apr 2017 20:33:51 No DSL connection
21 Apr 2017 20:34:08 Recording paused
21 Apr 2017 20:34:14 Recording resumed
21 Apr 2017 20:34:15 No DSL connection

21 Apr 2017 20:35:11 Recording paused
21 Apr 2017 20:35:15 Recording resumed
21 Apr 2017 20:35:17 Unable to login to modem/router

21 Apr 2017 20:36:33 Recording paused
21 Apr 2017 20:36:36 Recording resumed
21 Apr 2017 20:36:38 DSL connection restored

21 Apr 2017 20:36:41 IP address is now 147.147.*.*

So I'm a bit stuck, as no noise no PSTN call reason.

I doubt it is at all relevant, but I have a MasterPlug tower. It has an input from the phone socket, and output to the router, so I ask if there is a downside to that configuration, that could be in part a culprit.

BTW just noticed the IPcanged @20:25, 20:36 and 20:44. Bit often isn't it?
Title: Re: Weekend was not good for me
Post by: burakkucat on April 21, 2017, 09:14:53 PM
BTW just noticed the IPcanged @20:25, 20:36 and 20:44. Bit often isn't it?

Yes, it is. It is either indicating a problem with the equipment or a circuit with a defective connection.
Title: Re: Weekend was not good for me
Post by: burakkucat on April 21, 2017, 09:19:34 PM
Re..'high resistance' what sort of resistance value ?. :hmm:

Walter really meant to use the phrase "high impedance". The test telephone will present an impedance of many Mega Ohms to the circuit. The high impedance will not allow sufficient current to pass, thus not looping the pair and signalling a calling condition to the exchange equipment.
Title: Re: Weekend was not good for me
Post by: renluop on April 21, 2017, 10:44:36 PM
Yes, it is. It is either indicating a problem with the equipment or a circuit with a defective connection.
You mean the Billion router or what? The computer is a Dell refurb, probably about 9 months old according earliest files found.

Any suggestion as to what next? How do I approach ISP without some positive evidence?


All a b****y nuisance, as I've just "forced JLP to send someone out to troubleshoot my HDR,prior to requesting Humax to repair/ replace.
Title: Re: Weekend was not good for me
Post by: burakkucat on April 22, 2017, 12:59:44 AM
Please be aware that it is always difficult performing remote fault-finding.

As to the equipment, I was being somewhat vague, for it could be your modem/router or the ISP's DSLAM/MSAN or bRAS. As for the possibility of a defective connection, it could be anywhere in the cable between your home and the serving telephone exchange.

I think it will have to be a case of being rather patient and making careful observations, along with date and time, when those disconnects occur.
Title: Re: Weekend was not good for me
Post by: renluop on April 22, 2017, 06:43:04 AM
Of course! :) But I have the additional trouble of DSLStats failing to keep working (another thread).
Should I swap over to my old router yet?
Title: Re: Weekend was not good for me
Post by: kitz on April 22, 2017, 10:04:45 AM
Quote
BTW just noticed the IPcanged @20:25, 20:36 and 20:44. Bit often isn't it?

It indicates that the line lost sync to the exchange. See  - "DSL connection dropped"
The line will have had to retrain and once sync was negotiated a new PPP session will have had to be obtained from your ISP at which point you were allocated a new IP address.



Quote
Got wife to listen for noise (her hearing is superior to mine) and she heard no noise. I've yet to use a corded though.

TBH if you cant hear any noise using a cordless phone, then its unlikely you'd hear anything with a corded. 
Cordless phones can sometimes pick up a bit of noise unrelated to physical line conditions which is why we say test with a corded phone. eg you may sometimes hear a bit of noise when testing with a cordless which isn't really there on the physical line


Out of interest those drops weren't at around the time you were doing the Quiet Line Test were they? (or was the phone in use at that particular time?)
I always watch DSLstats when performing a QLT, if the upstream SNRm starts wavering or if you lose sync then its further proof of a developing HR fault.
Title: Re: Weekend was not good for me
Post by: renluop on April 22, 2017, 10:34:38 AM
QLT difficult to recall, but wifey's was well away from comp, and DSLstats bad behaviour not helpful. Next time I play, I'll make sure to be watching Eric's marvel!
Title: Re: Weekend was not good for me
Post by: renluop on April 24, 2017, 07:08:10 PM
Yesterday, having set up DSLStats 5.9.3.2, I had no problems at all, save that DS SNRM was running above US. I turned the router off overnight.
At boot this morning I was delighted that sync had risen from ~5500kbps to ~7300 kbps, which  @6 db SNRM was not far from the ~7900 kbps @ 3dB. Premature delight! DSLStats had stopped working. On its restart down sync had plummeted to 150kbps @ SNRM rocketed to over 30 dB. Tones used diminished.
We went out and came back mid-afternoon, by when it had recovered. QLN was different from its norm, while the anomalies existed.
A PDF of some graphs is attached.
Title: Re: Weekend was not good for me
Post by: kitz on April 24, 2017, 09:18:13 PM
Do you have any SNRm graphs for this morning?

Quote
QLT difficult to recall, but wifey's was well away from comp, and DSLstats bad behaviour not helpful.

Not sure if I misunderstand our answer or if you misunderstood me. 
What would be useful is if you could get a SNRm graph mapping whilst performing a Quiet Line Test.  If you could get a before and after period in the same graph too that would be useful.     

In fact it needn't be a QLT, even better may be to try a Ringback test.
Dial 17070... and I think its option 1

Whilst doing this if possible, get DSLstats to record every 10 seconds rather than the default 60 secs.
Configuration > Graphs > Sample every:

What I'm trying to check is if there is any variation in SNR margin whilst the phone is in use or when it rings. 
Title: Re: Weekend was not good for me
Post by: burakkucat on April 24, 2017, 09:32:54 PM
Looking at the abnormal QLN plot, I am suspicious of the circuit's integrity.  :-\

That plot looks somewhat like what I would expect with a "one leg dis" . . . but with the two disconnected ends held in very close proximity, such that there is significant capacitive coupling "across the gap".
Title: Re: Weekend was not good for me
Post by: renluop on April 24, 2017, 11:30:53 PM
Do you have any SNRm graphs for this morning?

Not sure if I misunderstand our answer or if you misunderstood me. 
What would be useful is if you could get a SNRm graph mapping whilst performing a Quiet Line Test.  If you could get a before and after period in the same graph too that would be useful.     

In fact it needn't be a QLT, even better may be to try a Ringback test.
Dial 17070... and I think its option 1

Whilst doing this if possible, get DSLstats to record every 10 seconds rather than the default 60 secs.
Configuration > Graphs > Sample every:

What I'm trying to check is if there is any variation in SNR margin whilst the phone is in use or when it rings.

SNRm graphs for the morning, such as are, in PDFs below.

Sorry for PDFs instead of gifs! Windows 10 and MSPaint don't work the same as earlier editions. I haven't cracked it yet.
Wii do other things tomorrow.
Title: Re: Weekend was not good for me
Post by: renluop on April 24, 2017, 11:37:44 PM
Looking at the abnormal QLN plot, I am suspicious of the circuit's integrity.  :-\

That plot looks somewhat like what I would expect with a "one leg dis" . . . but with the two disconnected ends held in very close proximity, such that there is significant capacitive coupling "across the gap".

Que! can you put that in words one syllable? ;D Is your suspicion based on the relative smoothness of the abnormal QLN graph?
Title: Re: Weekend was not good for me
Post by: burakkucat on April 25, 2017, 12:00:46 AM
Que! can you put that in words one syllable? ;D

I know nothing, I come from Barcelona.  ::)

Quote
Is your suspicion based on the relative smoothness of the abnormal QLN graph?

It certainly should not have that shape!

My suspicion is that there is either a defective joint or a fracture in one of the wires making up the circuit's pair. The two ends are being held very close together but without being in intimate contact and are emulating a capacitor. Hmm . . . I'm now having second thoughts. Rather than a series capacitive effect, I wonder if we are seeing a parallel (shunt) capacitive effect. All higher frequencies have disappeared leaving a plot that rapidly flattens with increasing frequency.

I know you have had many problems with the D-side circuit over the years. When I first arrived here, N years ago, you were waiting for the hole digging man to excavate the cable. Am I right in saying that you have been told that cabling with aluminium conductors form part of your circuit?
Title: Re: Weekend was not good for me
Post by: konrado5 on April 25, 2017, 08:08:49 AM
renluop: could you also attach current Hlog?
Title: Re: Weekend was not good for me
Post by: renluop on April 25, 2017, 11:02:00 AM
@B'cat
I can't recall having mentioned ali, but my part of the estate was built 1971 and cables are d.i.g. Prior to ADSL2/2+ the attenuation was 43-44 db and since 46-47. For that I am getting  sync ~7350 kbps ADSL2+. BT estimate for number is 3.5 -5.5 Mbps.

The crow fly distance from exchange to house is 2044 metres, and by road, using local knowledge of area and how cable on the D side runs I put @ ~2550 metres.

I've assumed from the speed obtained vs BT estimator, that ali was unlikely.

Right tree?
Title: Re: Weekend was not good for me
Post by: renluop on April 25, 2017, 11:13:49 AM
@ konrado5

What do you expect HLog to reveal? See attachment.

@ kitz I haven't forgotten. :)
Title: Re: Weekend was not good for me
Post by: renluop on April 25, 2017, 03:09:32 PM
@ Kitz now attached is my ring back graph!
Title: Re: Weekend was not good for me
Post by: burakkucat on April 25, 2017, 04:42:35 PM
I can't recall having mentioned ali, but my part of the estate was built 1971 and cables are d.i.g. Prior to ADSL2/2+ the attenuation was 43-44 db and since 46-47. For that I am getting  sync ~7350 kbps ADSL2+. BT estimate for number is 3.5 -5.5 Mbps.

Thank you for that information. My memory has obviously got you muddled with someone else.  :-[

Quote
I've assumed from the speed obtained vs BT estimator, that ali was unlikely.

Right tree?

Agreed.
Title: Re: Weekend was not good for me
Post by: konrado5 on April 26, 2017, 12:58:54 AM
@ konrado5

What do you expect HLog to reveal? See attachment.
I hope someone will have Hlog similar to mine.
Title: Re: Weekend was not good for me
Post by: renluop on April 26, 2017, 06:58:18 AM
On start of DSLStats this morning DS SNRM had risen to 9dB.
Title: Re: Weekend was not good for me
Post by: roseway on April 26, 2017, 07:56:08 AM
It appears that DLM has got you.
Title: Re: Weekend was not good for me
Post by: renluop on April 27, 2017, 07:38:39 PM
A FWIW update.

Was out most of day, in which time DSLStats had stopped working. Restored all was much as in the morning.
For a few minutes either side of 17:36 DS SNRm to 0, or may be less. Around 18:10 Sync dropped from
 5000 to 3100 kbps and tones in use maxed at # 125. QLN is once more not as it should be (b'cats comment).*

I wonder if Kitz got anything from the SNRm graph she requested.

S..'s Law; all this is going on, when after nearly a month of hoop jumping, I've just got a loan satellite box for one that has a fault less than 6 months from new. ::) :-X
* All back to where it was in~ 40 mins.
Title: Re: Weekend was not good for me
Post by: renluop on April 30, 2017, 07:08:14 PM
I hope it isn't too forbidden! :fingers:
Possibly a waste of time, I am running the rival (Routerstats Lite) along with DSLStats in case it shows anything up at failures and beyond. If wanted, I'll paste an abridged log.

I am now getting "unable to read data from file special routers.dat" and "unable to read data from file routers.dat" on starting the program. The program runs once the warnings have been cancelled. Are the warnings particularly significant?
Title: Re: Weekend was not good for me
Post by: roseway on April 30, 2017, 07:20:27 PM
Where is DSLstats installed? Those messages occur if DSLstats is installed in an unsuitable directory so it has difficulty reading the files in question.
Title: Re: Weekend was not good for me
Post by: ejs on April 30, 2017, 08:01:46 PM
I doubt it is at all relevant, but I have a MasterPlug tower. It has an input from the phone socket, and output to the router, so I ask if there is a downside to that configuration, that could be in part a culprit.

Wouldn't the obvious thing to do be take that MasterPlug thing out of the phone wiring entirely? I assume the MasterPlug thing is supposed to be providing surge protection for the phone line.
Title: Re: Weekend was not good for me
Post by: renluop on April 30, 2017, 08:21:14 PM
Wouldn't the obvious thing to do be take that MasterPlug thing out of the phone wiring entirely? I assume the MasterPlug thing is supposed to be providing surge protection for the phone line.
I have done the obvious, and it doesn't seem to have had any obvious effect on the problem. As the router's line is the extension (hard wired), I'm not sure of the protection any way.
Title: Re: Weekend was not good for me
Post by: renluop on April 30, 2017, 08:23:43 PM
Where is DSLstats installed? Those messages occur if DSLstats is installed in an unsuitable directory so it has difficulty reading the files in question.
C\ProgramFiles (x86).
Title: Re: Weekend was not good for me
Post by: roseway on April 30, 2017, 10:44:41 PM
As I recently discovered in a different thread, Program Files and Program Files(x86) are not suitable locations for DSLstats. The reason is that these folders are not fully accessible to ordinary users. Install DSLstats under C:\Users\<Your name>.
Title: Re: Weekend was not good for me
Post by: renluop on May 01, 2017, 08:46:23 AM
And clearly not useless users like me! :-[ Thanks, Eric!
Title: Re: Weekend was not good for me
Post by: roseway on May 01, 2017, 11:34:42 AM
It wouldn't be fair for me to agree with you :)
Title: Re: Weekend was not good for me
Post by: renluop on May 01, 2017, 04:36:16 PM
I hope it isn't too forbidden! :fingers:
Possibly a waste of time, I am running the rival (Routerstats Lite) along with DSLStats in case it shows anything up at failures and beyond. If wanted, I'll paste an abridged log.

That abridged log is attached just in case it may show something. One small thing is how attenuation can vary by ~3dB within minutes. That variation i worked as, say, 200 yards.
Title: Re: Weekend was not good for me
Post by: ejs on May 01, 2017, 05:55:26 PM
Could it be varying between ADSL1/2 and ADSL2+?
Title: Re: Weekend was not good for me
Post by: renluop on May 01, 2017, 07:47:25 PM
Telnet reports adsl 2+ and that's what router is set up for. How could a connection fluctuate between modes? :-\
Title: Re: Weekend was not good for me
Post by: ejs on May 01, 2017, 08:15:37 PM
Does it report ADSL2+ when it shows an attenuation of 43.5dB?

In general the mode would be negotiated at the time the connection is established, and some exchange equipment will switch the mode automatically based on the usability of the extended ADSL2+ downstream tones. And 3dB is approximately the expected increase in reported attenuation from ADSL1/2 to ADSL2+. Of course, if the modem is set for ADSL2+ exclusively, and/or it always reports it's using ADSL2+, then it's not that.
Title: Re: Weekend was not good for me
Post by: renluop on May 02, 2017, 09:13:35 AM
TBH I don't know, or even where I can find that historical data. Ido know that PN did put me on ADSL 2+. As to my Billion router, I am finding it very difficult to work out, if the mode in telnet is static or variable. If any one can help, I'd be grateful.

Last night I turned off the computer. When I rebooted today, I found DS SNRm 22.8 dB; speed 2151 kbps; attenuation 42.5 dB. Maximum speed is is 5132 kbps, and now mode is ADSL 2.

It's all confusing!
Title: Re: Weekend was not good for me
Post by: renluop on May 02, 2017, 11:07:46 AM
After a struggle I found how to lock in to a single gdmt mode. I also took the risk of tweaking noise margin down to 6 dB.(http://www.sherv.net/cm/emoticons/nervous/nail-biting.gif). Speed is now 5998 kbps.

I'll see if it settles, but has anyone more suggestions in the meantime?
Title: Re: Weekend was not good for me
Post by: renluop on May 05, 2017, 03:13:25 PM
As things have settled down somewhat, albeit with speed and SNRm fluctuations, twice to -2dB, I'll live with it until something decisive happens. Sufficient unto the day is the hassle thereof!

One entry in the event log today has me head scratching
Quote
05 May 2017 06:32:27   Incorrect login name or password
It cannot be true. I had left router and computer on overnight, and did not get up until a little after seven, so there was no interference with name or password.
What could've caused the event to be?
Title: Re: Weekend was not good for me
Post by: roseway on May 05, 2017, 04:13:12 PM
Normally that message means what it says, but in this case I suppose it could have been a spike of electrical interference which happened just as it was logging on, or something like that.
Title: Re: Weekend was not good for me
Post by: d2d4j on May 05, 2017, 04:32:34 PM
Hi roseway

I'm pretty sure from memory I have seen similar messages (win7 over wifi) and to be honest, I did not mention it previously because I thought it was already logged in and this message was another attempted login using same credentials

I do not think any data is missing from mine

I am sorry in advance if I am wrong though, old age and memory fade

Many thanks

John
Title: Re: Weekend was not good for me
Post by: tickmike on May 06, 2017, 12:09:27 AM
Normally that message means what it says, but in this case I suppose it could have been a spike of electrical interference which happened just as it was logging on, or something like that.
Look what I find in my logs
05 May 2017 02:39:38   Incorrect login name or password

I used to see it a lot and just ignored it as DSLstats still worked.
Title: Re: Weekend was not good for me
Post by: roseway on May 06, 2017, 07:07:54 AM
OK, I'll look at this again.
Title: Re: Weekend was not good for me
Post by: roseway on May 06, 2017, 07:45:22 AM
I've had a look at this now, and the message in question is shown when the modem fails to respond to the password, or fails to return the expected prompt, within the timeout time. This is normally the result of an incorrect username or password, as the message says, but it could just be a timeout resulting from the modem responding slowly.

Timeouts have been a slightly irritating issue with some modems, and that's what I'm working on now. In the meantime, if it only happens occasionally it's harmless (apart from missing one sample).
Title: Re: Weekend was not good for me
Post by: renluop on May 06, 2017, 11:05:55 AM
Why in the early hours, when I was in my pit, and nothing was going on?
Something crossed my mind. We hsve a small electrical unit nearby. Normally it gives no trouble, but did when we came in 2002. Perhaps it's going doolally again. Hmmm.
Title: Re: Weekend was not good for me
Post by: tickmike on May 06, 2017, 11:16:38 AM

 We hsve a small electrical unit nearby. Normally it gives no trouble, but did when we came in 2002. Perhaps it's going doolally again. Hmmm.


What do you mean outside near your house ?.
Have you got a Medium wave radio tuned to 612kHz you could take near it and check for interference.

[Moderator edited to fix the [quote][/quote] tags.]
Title: Re: Weekend was not good for me
Post by: renluop on May 06, 2017, 07:09:20 PM
The two attachments will help explain. The leccy unit may be smaller than illustration. Access is not easy, as it is along a fairly steep and uneven forest path on the flank of neighbour's house.

I have a radio and will try to see if there is out of ordinary noise, when convenient.
Title: Re: Weekend was not good for me
Post by: tickmike on May 06, 2017, 10:10:01 PM
It's a local substation, Possible high voltage in and steps it down for your area supply 230/415 Volt supply.
The cabinet would have fuses in.
There could be something called a 'tap Changer' to keep the output voltage constant.
The contacts on the tap changer do need regular maintenance and could be arching and making interference..
Even if you find nothing contact your area electrical supplier and ask them to come and check there gear.
 We live in a 'Special Conservation' area we have substation in the next lane to us and it had to be housed in a old barn to hide it, I have got our local electric supplier to clean the tap changer on a number of times.
Title: Re: Weekend was not good for me
Post by: renluop on May 06, 2017, 11:19:18 PM
OT very!
Special conservation area- sounds interesting, may I ask why it has the accolade?

Behind my house is the boundary of the New Forest National Park.
Title: Re: Weekend was not good for me
Post by: tickmike on May 07, 2017, 09:34:24 PM
OT very!
Special conservation area- sounds interesting, may I ask why it has the accolade?

Behind my house is the boundary of the New Forest National Park.
It's what our local council has put on the area 'Area of outstanding natural beauty' And that makes it very difficult to get planning permission.
We are in South-Derbyshire and we have a 800 Acre deer park with it's large Grade 1 mansion owned by the National Trust .
Title: Re: Weekend was not good for me
Post by: renluop on May 08, 2017, 09:32:13 PM
Having set up as lastly advised by Eric, the problems seemed to have vanished.  As that time I was running my connection from the hard wired extension: telephone socket > filter> router, ignoring the surge protector. Now I have once more included the protector in the run, as in attachment, method #2 inclusive of filter, but no phone is linked to the filter, as the phone is a slave.
It may be entirely coincidental, yet invalid floating point errors, and DSLStats has stopped warnings have bloomed. Also the Systray then contains more than one icon!
Not direcly to do with this. I rebooted computer this evening, and reset the router, which had been suffering “No DSLConnection” problems. Here is the Event Log afterwards
Quote
08 May 2017 20:17:42   Recording started
08 May 2017 20:17:46   Impossible upstream ES value reported. Value set to zero.
08 May 2017 20:17:46   Impossible downstream ES value reported. Value set to zero.
08 May 2017 20:18:00   Unable to determine IP address
08 May 2017 20:18:14   DSL connection dropped
08 May 2017 20:18:14   No DSL connection
08 May 2017 20:18:45   DSL connection restored
08 May 2017 20:20:44   DSL connection dropped
08 May 2017 20:20:44   No DSL connection
08 May 2017 20:21:14   No DSL connection
08 May 2017 20:21:45   DSL connection restored
08 May 2017 20:21:49   IP address is now 91.125.*.*
Is it, then, mere coincidence, that the problems have resurfaced with the new configuration. I cannot see how it cannot be, or what more could be the problems.
Title: Re: Weekend was not good for me
Post by: renluop on May 09, 2017, 11:49:20 AM
Have done a wander around house with radio, amd found that near to my answerphone base unit there's a substantial pulsating "puuurrrup". The base unit, being in the hall, is distant from the router. The slave is quite near the router, 6", but seems OK.

The DECT units, Panasonic, are about 8 y.o. At that age are they likely to have deteriorated appreciably?