From: blowme@googlesucks.com   
      
   Don't know how relevant this is, but I have a lenovo laptop and its a   
   piece of junk. Very unreliable, weird acting and unstable. I will never   
   buy Lenovo product.   
      
   Jeff Liebermann  wrote in   
   news:o4prietrvmn2hb59ioijo4qc4l4dlbfgst@4ax.com:   
      
   > On Sun, 23 Jun 2019 10:37:27 -0700, Jeff Liebermann    
   > wrote:   
   >   
   >>On Sun, 23 Jun 2019 10:53:33 +0000 (UTC), hohum    
   >>wrote:   
   >>   
   >>>I am either being hacked by the ISP or someone on the network.   
   >>   
   >>Right.  The first step to solving a problem is to blame someone.   
   >>   
   >>>Lately I have had to change the mac address AND the user account to   
   get   
   >>>back ability to ping the router reliably.   
   >>>   
   >>>Very funny that changing the user account reestablishes my   
   connectivity   
   >>>even after I have changed the mac address.   
   >>   
   >>I'm dealing with a similar problem that I can't seem to fix.  It's an   
   >>Arris SB-6141 cable modem and an Asus RT-AC66Uv1 router.  There are   
   >>about 6 assorted Thinkpad/Lenovo laptops all connected via Wi-Fi. Some   
   >>new, some old.  Only the Thinkpad/Lenovo laptops running Windoze 10   
   >>all have the same problem.  If the Comcast or the modem loses internet   
   >>connectivity, the Wi-Fi will disconnect, and remain disconnected even   
   >>if connectivity is restored to the modem.  Wi-Fi connectivity can be   
   >>temporarily restored by changing the MAC address or rebooting the   
   >>laptop or router.  ipconfig release/renew doesn't restore wi-fi   
   >>connectivity.  Running "network reset" and playing with various power   
   >>saving settings do not help.  Temporarily switching to a different   
   >>router doesn't fix the problem.  No problems with other machines   
   >>running Windoze 7, XP, Android, ChromeOS, etc.  My initial guess(tm)   
   >>is either a Windoze 10 problem, or a bad Wi-Fi driver.  I'll post   
   >>something when I visit the site in about 2 weeks.   
   >   
   > Problem solved and the problem had nothing to do with Windoze 10   
   > or a bad Wi-Fi driver.  So much for my initial guess(tm).   
   >   
   > I did a Comcast internet service call Saturday that was rather   
   > unusual.  I've been working on this customers computers for   
   > probably 15 years, ever since he moved to Bonny Doon.  His Comcast   
   > internet had always been unreliable and subject to erratic short   
   > term outages.  Comcast has looked at his problem many times.   
   > There were visits by installers, but since the cabling was installed   
   > quite nicely, nothing was changed.  Last time I was there (about   
   > 6 months ago), I found an intermittent F connector, which I replaced.   
   > In the last few weeks, the erratic outages became more frequent to   
   > the point where the customer was sufficiently desperate to have me   
   > work on it on a weekend and in rather hot weather.   
   >   
   > I spent 4 hrs systematically replacing everything possible to see   
   > what happens.  The SB6141 was upgraded to an SB6183, which   
   > improved the download speed to about 75 Mbits/sec, but didn't do   
   > anything for the erratic drop outs.  I was down to my laptop   
   > plugged directly into the SB6183 and it still screwed up.  The   
   > Rigol DSA815 spectrum analyzer showed nothing unusual and the   
   > SNR and signal levels in the modem diagnostics were well with   
   > acceptable limits.  Nothing interesting in the modem logs.  Yet,   
   > every 5 to 20 minutes, the error rate dramatically increased,   
   > stayed there for about 5 minutes, and then returned to normal.   
   > Several times, I thought I had fix it, only to have it crap out   
   > by simply waiting a few minutes.  Maximum frustration for me.   
   >   
   > A quick check of the neighbors showed that none were having any   
   > manner of similar problems with their Comcast internet.  So, the   
   > problem was somewhere on the customers property or in his   
   > equipment or computahs.   
   >   
   > I was about to give up when I looked more carefully at what was   
   > inside the cable box.  The cable entered the box via some F barrel   
   > connectors, and then went to a -6dB tap.  It continued through   
   > the tap via RG-6/u which eventually went to the TV and the rest   
   > of the house.  I had that branch of the cable disconnected and   
   > replaced with a 75 ohm termination, so I knew it wasn't in that   
   > part of the house cabling.  Connected to the -6dB tap was a   
   > -8dB attenuator which continued to about 20ft of RG6/u coax to   
   > the cable modem.   
   >   
   > It was at this point that I was getting desperate.  Despite the   
   > good readings on both the modem and spectrum analyzer, something   
   > didn't seem right with this arrangement.  I had never seen that   
   > much attenuation in front of a cable modem.  -6dB was about right   
   > for the tap, but the -8dB attenuator was far too much attenuation.   
   > I removed the attenuator from the system, and immediately things   
   > started to look much better.   
   >   
   > The first thing I noticed was that all the download speed tests   
   > had stabilized to a solid 90 Mbit/sec, which indicated that it   
   > could go much faster, but was being rate limited either at the   
   > CMTS or my 100baseT ethernet cable.  We tested it every way I   
   > could think of and the dropouts seemed to be gone.  The mysterious   
   > wi-fi disconnects also disappeared.  So, the extra attenuator   
   > that had been in the system for at least 10 years was the   
   > apparent culprit.   
   >   
   > Of course, not everything went perfectly.  I forgot to take photos.   
   > I forgot to close the lid on my fishing box full of coax connectors   
   > and dumped half the contents on the ground.  Dinner at a local   
   > restaurant was awful.  It was much too hot and I was dead tired.   
   >   
   > Unfortunately, two questions remain un-answered for the now.  Why   
   > was the modem signal levels and SNR normal, when it was obviously   
   > having a difficult time dealing with the low signal levels?  That's   
   > 4 different modems that I tested (3ea SB6141 and 1ea SB6183).  There   
   > were some errors appearing in the statistics pages, but nothing   
   > unusual.  After removing the attenuator from the system, the SB6183   
   > still showed some errors, but not as many as with the attenuator.   
   > I need to take a closer look at the numbers and the effects of   
   > excessive attenuation in front of the cable modem.  Also, why did   
   > excessive packet loss and errors cause only the Lenovo Win 10 wi-fi   
   > driver to disconnect and not automatically reconnect?  Yet another   
   > project.   
   >   
   >   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)