UPDATE: For the source of the problem, see this post.
Yesterday, while happily typing away on my new laptop, all of a sudden pages weren't loading, and ping gave me this, in between actual results:
Note that two Android devices literally right next to it were pinging away like crazy. No other device on the network was having problems, just the brand-new laptop--which has worked fine for, what?, two weeks? I have not installed/uninstalled/tweaked anything to do with networking in over a week.
I plugged an Ethernet cable in and got blazing speed. Since I'm in bed anyway, it really doesn't matter whether it's hardwired or wireless, but I certainly don't expect a brand-new laptop to already have hardware problems.
Any ideas on what's causing this? Again, it was working fine until it abruptly became sporadic yesterday afternoon, AND it's the only device having problems.
UPDATE: Scratch the wired idea... Last night it was fine, this morning, not so much. I noticed the plug was kind of loose, so I managed to scrounge up one other [much shorter] cable and tried it...same result. I've unplugged and rebooted my modem and router, just on the remote chance there was some glitch [that mysteriously only affected ONE device out of 15], but, no.
To summarize, a continuously running while/do/ping/sleep 5/done on the laptop WITH both wired and wireless connections, yields the result I posted above, mixed in with actual results:
SECOND UPDATE: I booted up from my 20.04 install drive and guess what? I let my continuous ping test run for 10 minutes, with NOT ONE hiccup. So I've now deduced that something got screwed up somewhere, although I don't know when or how, since as stated earlier I'd been using the laptop all day when, out of the blue, it started losing its connectivity. I hadn't updated or installed or modified ANYTHING around the time it started.
My question now is...well, shoot, I knew this would come back to bite me. Because of the issues surrounding the laptop's arrival and Kubuntu installation, for the first time in 35 years, I did not partition the drive like I normally do. I just checked the 'guided -- use entire disk' option and let it rip. So now, if I need to reinstall the OS, I can't do a clean install without losing data. Before I take that plunge, can anyone suggest somehow fixing this? Now that I know it's not a hardware problem, it has to be a setting/configuration/something.
Yesterday, while happily typing away on my new laptop, all of a sudden pages weren't loading, and ping gave me this, in between actual results:
Code:
ping: google.com: Temporary failure in name resolution
I plugged an Ethernet cable in and got blazing speed. Since I'm in bed anyway, it really doesn't matter whether it's hardwired or wireless, but I certainly don't expect a brand-new laptop to already have hardware problems.
Any ideas on what's causing this? Again, it was working fine until it abruptly became sporadic yesterday afternoon, AND it's the only device having problems.
UPDATE: Scratch the wired idea... Last night it was fine, this morning, not so much. I noticed the plug was kind of loose, so I managed to scrounge up one other [much shorter] cable and tried it...same result. I've unplugged and rebooted my modem and router, just on the remote chance there was some glitch [that mysteriously only affected ONE device out of 15], but, no.
To summarize, a continuously running while/do/ping/sleep 5/done on the laptop WITH both wired and wireless connections, yields the result I posted above, mixed in with actual results:
Code:
PING google.com (142.250.68.46) 56(84) bytes of data. 64 bytes from lax17s46-in-f14.1e100.net (142.250.68.46): icmp_seq=1 ttl=115 time=13.7 ms 64 bytes from lax17s46-in-f14.1e100.net (142.250.68.46): icmp_seq=2 ttl=115 time=12.2 ms 64 bytes from lax17s46-in-f14.1e100.net (142.250.68.46): icmp_seq=3 ttl=115 time=12.4 ms 64 bytes from lax17s46-in-f14.1e100.net (142.250.68.46): icmp_seq=4 ttl=115 time=11.6 ms 64 bytes from lax17s46-in-f14.1e100.net (142.250.68.46): icmp_seq=5 ttl=115 time=12.1 ms --- google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4007ms rtt min/avg/max/mdev = 11.586/12.389/13.671/0.692 ms PING google.com (142.250.68.46) 56(84) bytes of data. --- google.com ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 4096ms ping: google.com: Temporary failure in name resolution PING google.com (142.250.68.46) 56(84) bytes of data. 64 bytes from lax17s46-in-f14.1e100.net (142.250.68.46): icmp_seq=1 ttl=115 time=12.1 ms 64 bytes from lax17s46-in-f14.1e100.net (142.250.68.46): icmp_seq=2 ttl=115 time=13.2 ms 64 bytes from lax17s46-in-f14.1e100.net (142.250.68.46): icmp_seq=3 ttl=115 time=14.2 ms 64 bytes from lax17s46-in-f14.1e100.net (142.250.68.46): icmp_seq=4 ttl=115 time=13.0 ms 64 bytes from lax17s46-in-f14.1e100.net (142.250.68.46): icmp_seq=5 ttl=115 time=11.8 ms --- google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 11.832/12.859/14.195/0.844 ms PING google.com (142.250.68.46) 56(84) bytes of data. 64 bytes from lax17s46-in-f14.1e100.net (142.250.68.46): icmp_seq=1 ttl=115 time=12.1 ms 64 bytes from lax17s46-in-f14.1e100.net (142.250.68.46): icmp_seq=2 ttl=115 time=11.8 ms 64 bytes from lax17s46-in-f14.1e100.net (142.250.68.46): icmp_seq=3 ttl=115 time=13.6 ms 64 bytes from lax17s46-in-f14.1e100.net (142.250.68.46): icmp_seq=4 ttl=115 time=11.7 ms 64 bytes from lax17s46-in-f14.1e100.net (142.250.68.46): icmp_seq=5 ttl=115 time=11.7 ms --- google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4007ms rtt min/avg/max/mdev = 11.690/12.152/13.563/0.717 ms PING google.com (142.250.68.46) 56(84) bytes of data. --- google.com ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 4081ms ping: google.com: Temporary failure in name resolution
My question now is...well, shoot, I knew this would come back to bite me. Because of the issues surrounding the laptop's arrival and Kubuntu installation, for the first time in 35 years, I did not partition the drive like I normally do. I just checked the 'guided -- use entire disk' option and let it rip. So now, if I need to reinstall the OS, I can't do a clean install without losing data. Before I take that plunge, can anyone suggest somehow fixing this? Now that I know it's not a hardware problem, it has to be a setting/configuration/something.
Comment