[SOLVED] Ping Issue Over LAN - "Destination Host Unreachable"
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ping Issue Over LAN - "Destination Host Unreachable"
Hello! I am running into an issue when pinging my desktop PC from my laptop (Lenovo X1 Carbon).
- Both machines are running Ubuntu 22.04
- Both machines are connected using wifi
- The issue starts to happen after I close my laptop lid (or click "suspend"), and then open the lid back up
Things work fine at first and I get a response:
Code:
PING 192.168.1.12 (192.168.1.12) 56(84) bytes of data.
64 bytes from 192.168.1.12: icmp_seq=1 ttl=64 time=7.53 ms
64 bytes from 192.168.1.12: icmp_seq=2 ttl=64 time=8.14 ms
Then, when I close the lid on my laptop, reopen it, and try to ping again, I get a "Destination Host Unreachable" and "No route to host" error:
Code:
PING 192.168.1.12 (192.168.1.12) 56(84) bytes of data.
From 192.168.1.14 icmp_seq=1 Destination Host Unreachable
ping: sendmsg: No route to host
However, I can ping other machines on my network without an issue after opening the lid (i.e. Windows PC, TV, etc.). And I can ping my laptop from my desktop at this point too (the other direction). When I try the ping in the other direction like this, it actually fixes the issue and my laptop can ping my desktop again afterwards!
Any help would be greatly appreciated. My ultimate goal here is to remote into my desktop PC from my laptop. Thanks in advance, Jon.
Then, when I close the lid on my laptop, reopen it, and try to ping again, I get a "Destination Host Unreachable" and "No route to host" error:
Most laptops will disconnect from the WiFi when you close the lid, in order to save power. If you want to prevent this from happening you could try connecting an external screen.
Quote:
Originally Posted by jonshaw199
My ultimate goal here is to remote into my desktop PC from my laptop. Thanks in advance, Jon.
Are you using KDE? If so, then you can try KRFB/KRDC. It works well.
Most laptops will disconnect from the WiFi when you close the lid, in order to save power. If you want to prevent this from happening you could try connecting an external screen.
Are you using KDE? If so, then you can try KRFB/KRDC. It works well.
That makes sense, but I need my laptop for on-the-go and after I close and reopen the lid once, then I can no longer ping or remote into my desktop PC (I can still access the internet and reach other local devices though). But until then, I don't have issues and I can remote into it. Also, I'm currently using gnome and Remmina but I will check those out! Very new to linux in general.
Maybe try: ip r ; arp -a # while not working vs. working
Quote:
However, I can ping other machines on my network without an issue after opening the lid (i.e. Windows PC, TV, etc.). And I can ping my laptop from my desktop at this point too (the other direction). When I try the ping in the other direction like this, it actually fixes the issue and my laptop can ping my desktop again afterwards!
Maybe wait a minute for network to start back up. Check logs/dmesg/journalctl ...
Ok I'm back in town and continuing this investigation. I will look into each of these suggestions and get back to you.
I will say that I'm starting to wonder if the problem lies with the desktop computer (the one I'm trying to connect to; never had issues with the laptop and I just built the desktop). I'm experiencing a number of seemingly intermittent network issues, maybe unrelated though. For example, I disabled ssid broadcasting on the router (I guess that means "hidden"), and I have to repeatedly try connecting until it finally succeeds. This PC has a TUF GAMING B550-PLUS WIFI II motherboard w/ a MT7921 wifi card; also my kernel version is 6.5.0-25-generic if that matters. I wouldn't be surprised if a wired connection would help, but I'm hoping I don't have to do that.
Also, I realize this might be the wrong forum for this question. But it's really hard for me to say; don't even know where to start on this. Thanks everyone for the input.
I thought I had updated everything on the desktop, but the software updates dialog JUST popped up and I noticed some firmware changes specifically for this wifi card. So I proceeded with the updates, repeated the suspend/awake process about 10 times, and I'm no longer able to reproduce the issue. I can ping and remote into the desktop from my laptop every time. Maybe this isn't related and it's just a coincidence, but it seems like a good sign...
What I don't understand is why suspending/awaking the laptop would make a difference if the issue did lie with the desktop firmware. Maybe this is just a coincidence of some sort. Will do a bit more testing...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.