Re: No route to host Goodness - a 'revival' to a 9 year old problem ! Also, the D-Link is connected to the Cisco via an Ethernet cable to the Cisco's lan port. There is no docker0 bridge on Windows. You are able to telnet server on port 80 locally but when you try to telnet your server on port 80 remotely you get no route to host. I have reviewed and followed the MediaBrowser Connectivity article. Port forwarding confirmed. Share Troubleshooting: In-Home access is visible. 2. No remote access. 3. The above reply comes from IP address 151.101.194.1.241, which seems to relate to the remote gateway handling our request. The command: C:\>tracert 22.110.0.1 WinSCP is a free SFTP, SCP, Amazon S3, WebDAV, and FTP client for Windows. No firewall running on the server. Probably, either the router has a configuration problem, or the 22.110.0.0 network does not exist, reflecting a bad IP address. By editing the Hosts file, Windows can be customized to block or redirect specific websites and even protocols that are used by programs and applications. Here are the things that I would like to know: 1. (myserver)$ ip route default via 159.89.128.1 dev eth0 10.46.0.0/16 dev eth0 proto kernel scope link src 10.46.0.5 159.89.128.0/20 dev eth0 proto kernel scope link src 159.89.x.x Since I am unable to copy / paste from the DO console, here is an image of sudo iptables -nvL INPUT WSL2 Bash: Usually, this means that that the host with that IP address is not online or responding. The Windows Hosts file is a file that Windows uses to control and map IP addresses. So it needs to match the IP given to the vEthernet (WSL) interface of the windows host. Because of the way networking is implemented in Docker Desktop for Windows, you cannot see a docker0 interface on the host. The networking all seems fine, I can ping the registry DNS etc, but every docker login command failed with 'no route to host' until I switched to Windows containers - it then worked. This interface is actually within the virtual machine. The ICMP message, "no route to host," means that ARP cannot find the layer-2 address for the destination host. It keeps telling me that there is no route to host and i dont know what that means, so if you could tell me how to do fix I would greatly appraciate it, thanks. You can use TRACERT to find out where a packet stopped on the network. I cannot ping my containers. VPN is used when testing Remote access. Note that in my config, the WSL2 adapter (eth0) is on a different subnet from the default gateway, but it will still use the default when the interface has no override. Firewall is not blocking anything related to Media Server nor the serverapp.exe Is there any firewall running between remote machines and I've looked on canyouseeme.org to check if my ports are open and not even port 80 is open. The gateway IP is a virtual tap interface that's provided by the windows host. My issue started 3 days ago. This means I am currently unable to push any of my containers as they are all Linux based. Static route is still in place. To check this, run a traceroute using the following command: When I check the ports to see if it works, the result is always "no route to host" which means it is getting a signal but I think something is blocking it. But the message is clear - it is a network related, most likely a name resolution problem. In the following example, the default gateway has found that there is no valid path for the host on 22.110.0.1. Reply from 151.101.194.1.241: Destination host unreachable. In this article, well walk you through the steps to correctly edit the HOSTS file. Docker Desktop for Windows cant route