It will reset the routing table cache on the WiFi router. 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. What I strongly suspect is happening here is that the client is accessing the API via a load balancer or some other type of network device and that device is configured to time out after 120 secs, at which point the device returns the 502. Reply from 192.168.11.3: Destination host unreachable. You are getting a response before you are timing out client-side. Pinging 192.168.11.1 with 32 bytes of data: Reply from 192.168.11.3: Destination host unreachable.
REQUEST TIME OUT WINDOWS
Sometimes a simple reboot on the second computer can fix the problem. and when I ping my main Windows from VM machines I get: C:\Users\amin>ping 192.168.11.1. Disable the firewall on the destination computer and try to ping it again from the first device.Įven 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. So, as Andriy Zavoloka mentioned, I too doubt the Firewall settings on the destination computer. It means the firewall settings on your computer are fine. You can ping the localhost IP (Loopback address) successfully. Since you can ping other addresses from your computer successfully, your local computer network configuration is fine. 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.Ĭommon causes for this error are either network configuration errors or firewall blocking.
0 kommentar(er)
