Ping — Request timed out on a local network
I’m trying to ping another computer that is connected to the same Wi-Fi network. Pinging to anything else (localhost, website, etc.) works fine. But when I try to ping to the local ip address of my second computer I get a Request timed out. message
$ ping target_ip Pinging target_ip with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for target_ip: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), 7 Answers 7
- Try to ping another device from your local network (pinging localhost or a website is not the same).
- Try to ping from target_ip to source_ip (opposite direction).
If you have response in any of 2 cases above, check the firewall on your target machine (or as in your case, for Windows, make sure you are connected to Private Network, not Public). And make sure you are trying to ping the proper IP address.
@AlexT Why #2 (pinging source_ip from target_ip) won’t work? If it doesn’t, then it’s either firewall on both source_ip and target_ip, or you don’t have connectivity between hosts (layer 5 or lower).
If you are unable to ping a computer on your network, the reason could be that the firewall on that computer is blocking incoming ICMP (Internet Control Message Protocol) traffic. In this case, you can try enabling the «File and Printer Sharing (Echo Request — ICMPv4-In)» inbound rule in Windows Defender Firewall to allow ping requests.
Note that enabling this rule may make your computer more vulnerable to certain types of attacks, so you should only do so if you trust the computers on your network and are comfortable with the increased risk. Additionally, if you are using a third-party firewall, the steps may be different, so you should consult the documentation for that firewall for guidance.
Here are the step-by-step instructions:
- Open Windows Defender Firewall with Advanced Security on the computer that you are not able to ping. You can do this by searching for «Windows Defender Firewall» in the Start menu and clicking on the corresponding result.
- In the left pane, click on Inbound Rules.
- Scroll down until you find the File and Printer Sharing (Echo Request — ICMPv4-In) rule. This rule is used to allow incoming ICMP traffic, which is what ping uses.
- Right-click on the rule and select Enable Rule.
That’s it! Close the window and try pinging the computer again. It should now work as expected.
I had the same issue, in my case the problem was- I was not able to ping any website like www.google.com or any other external IP address. But I was able to ping my own ipv4 address. If you are not able to ping your own ipv4 address then follow this(https://support.logmeininc.com/central/help/why-do-i-get-request-timed-out-when-trying-to-ping-a-computer). And if you are not able to ping external IP address then there are 2 cases,
- You are connected with the ethernet OR ISP connection. Then Ping will work fine.
- You are using the mobile hotspot, then try changing the bandwidth to 5GHZ from the mobile phone and connect again. It worked for me I hope it will work for you as well.
TLDR: Turn off all defenders
I had the same issue and very similar answers above helped but I do want to add something in that I didn’t see.
My set up was to try to ping an Oracle linux virtual machine running on windows from my MacBook
When I went to turn off Microsoft Defender Firewall, it was already off because I had a third party firewall turned on. Make sure you turn off third party firewalls on your host machine; in my case it was Kaspersky. Once this is turned off, Microsoft Defender Firewall will turn on. Make sure to turn this off.
After this, it had worked for me but some other advice that I found helpful was to make sure all firewalls were off on MacOS and to reset your router.
TLDR: Restart the destination device. If fails restart the router too.
Request Timed Out message tells your computer waited for the acknowledgment of the ping packets sent to the destination IP for a time but received none.
Common causes for this error are either network configuration errors or firewall blocking.
Since you can ping other addresses from your computer successfully, your local computer network configuration is fine.
You can ping the localhost IP (Loopback address) successfully. It means the firewall settings on your computer are fine.
So, as Andriy Zavoloka mentioned, I too doubt the Firewall settings on the destination computer. Disable the firewall on the destination computer and try to ping it again from the first device.
Even though you have mentioned you know the destination IP address is correct, I suggest you use the network discovery feature and verify if the DHCP server of your WiFi network didn’t assign a different IP address to the second computer.
Sometimes a simple reboot on the second computer can fix the problem.
If the issue persists, I suggest you power off the WiFi router (I assume you have the access) and switch it on after one minute. It will reset the routing table cache on the WiFi router.
Then check for the new IP address assigned to the second computer and Ping that address from your first computer.
I hope it will fix the problem.
WiFi having request timeout for icmp_seq
Recently, for some reason or other, my WiFi seems to have ceased to function properly. It was first obvious when pages started taking forever to load.
I decided to do a simple ‘ping’ in terminal to see if there was a problem there: if it could establish a proper connection. Upon doing so, each time I would ping any website, I would get a few successful packet transfers, yet this would be interspersed with: ‘time out for icmp_seq 1’ (or any other number according to which ping it was). Like so:
Thank you for you time if any of you can sort this out. 🙂
MacBook Air, macOS Sierra (10.12.4), The computer dates from 2011
Posted on Jun 2, 2017 3:20 AM
User level: Community Specialist
I understand that your Wi-Fi connection appears to not be functioning properly and you’re seeing latency when web pages are loading. I know it’s important to get the most from your Wi-Fi connection and I’d like to assist you. I’d recommend taking some time to review both Check for Wi-Fi issues using your Mac and Recommended settings for Wi-Fi routers and access points to troubleshoot the behavior you’re experiencing.
Have you tried rebooting your modem and router?
the ping says there is some problem between your mac and google’s webpage. The cause may be poor WiFi connectivity or poor Internet connectivity. I would do the following:
1. Restart the router, hoping anything’s good afterwards.
if problems persist or comes back soon:
2. Pinging the router — if pings to the router are stable (latency
— troubleshoot your WiFi (Reduce distance to router, change WiFi channel)
— troubleshoot your Router: Sometimes the router is just busy because other devices in your network cause heavy load. Or something consumes your routers CPU time in performing a lot of authentication failures. This «something» can be a misconfigured device on your network or even somebody trying to hack your WiFi. In this case, MAC Address filtering maybe a solution.
3. There is a problem with your internet connection. Possible Reasons:
— poor cabling — check all connections
— poor internet connection — maybe the cause is at your provider
— router busy — check whether other devices in your network cause heavy load
Hoping this helps you to solve the issue,
Thank you for your reply. Unfortunately, I can confirm that my router is not at fault, as I have been able to connect several other devices to it, as well as going through all of the steps you have described above, and them not solving my problem. Furthermore, if it is of any significance, I now connect to wifi via a USB WiFi card I happened to have bought for my Raspberry Pi that seems to be doing a decent job for now- however I would ultimately like to get to the bottom of the problem. 🙂
Yes, I have. Unfortunately I can confirm that it definitely is not the router’s fault.
Thank you for replying. I had already used the Apple WiFi diagnostics tool (which I probably should have included in my post), and it only states that seems to be no problems with my internet connection- or whatever the default ‘all clear’ message is. I have also monitored the WiFi connection of several routers that I have connected to over time with the same tool, and they all seem to be showing me that they have a stead connection. Furthermore, it may also be of use to you to know that though some pages may take a rather long time to load, others seem to not load at all (right now I think it is just a matter of luck).
I have also told user ‘Andreas Burgdorf’ that I am currently using a USB WiFi card (Realtek EW-7811Un, if it is of any use), which seems to be working perfectly well.
This seems to make the problem all-the-more interesting as I think it may have something to do with the internal WiFi card itself. However, as I had previously mentioned, it was working perfectly until some time ago.
Request timed out when pinging wireless router [closed]
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Recently I noticed the internet running very slowly on my laptop, which is connected to my wireless network (Netgear DGN2000). When I ping the router, I get long ping times and/or request timed out. here’s an output:
Reply from 192.168.0.1: bytes=32 time=20ms TTL=64 Request timed out. Reply from 192.168.0.1: bytes=32 time=3ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=2ms TTL=64 Request timed out. Reply from 192.168.0.1: bytes=32 time=7ms TTL=64 Request timed out. Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=108ms TTL=64 Reply from 192.168.0.1: bytes=32 time=48ms TTL=64 Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time=21ms TTL=64 Reply from 192.168.0.1: bytes=32 time=3ms TTL=64 Reply from 192.168.0.1: bytes=32 time=6ms TTL=64 Request timed out. Reply from 192.168.0.1: bytes=32 time=28ms TTL=64 Request timed out. Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time=14ms TTL=64 Request timed out. Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=5ms TTL=64 Reply from 192.168.0.1: bytes=32 time=2ms TTL=64 Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time=221ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time=87ms TTL=64 Reply from 192.168.0.1: bytes=32 time=2ms TTL=64 Request timed out. This has only started in the last week. When I connect to the router with a cable, the ping time is