Mengatasi Destination Host Unreachable
So, just to cover some basics.The second router upstairs is NOT using DHCP to pass out IP addresses, correct? If it is, you should turn off that service on the second router. I'm not saying to turn it off on both.
The second router should essentially be set up in bridge mode. Where it simply allows other computers to connect to the network it is part of. For example, with a Belkin router, you would simply enable 'Bridge Mode' and multiple features (like DHCP) would be turned off and made inaccessible.Now. Have you turned off the Windows Firewalls for each of these computers for testing purposes yet? That should be done, to ensure that the Firewall included with Windows isn't causing the ping request to be blocked. You didn't say which version of Windows you are using, and with Windows 7 ICMP are indeed blocked by default with the built-in firewall. So, if you wanted to continue to use the firewall, you would have to create an exception on each computer to allow ICMP (ping) requests through.
This doesn't mean the computers can't communicate with each other. You could have multiple network sharing services actively working with Windows 7, and still be blocked from pinging the machines. But.at the very least, disabling the firewall temporarily for testing. would be the way to go to see if indeed it is the firewall at issue here.As a side note. Can you view shared directories from each computer in question? Swap files, etc?At any rate.I've been trying to play Terraria on my home network, but I'm having troubles.
Pokemon fire red ruby gemini. After checking that the Terraria game and server were being allowed through Windows firewall on both machines, I decided to see if the two machines could ping each other, and they can't.You left out something. You set up the server, gave it an exception in the firewall, you set up a client, gave it an exception in the firewall, and then decided to ping each computer. You didn't say what happened in between.
Was it that you started the game on the client machine, and it couldn't see the server? Or did you think 'Hmm. I wonder if these computer can even see each other, I'd better ping them.'
Before you tried to connect the client to the server? Did you stick with the default port of 7777? I've tried selecting 'Host and Play' from within the game application on one machine, and then having the second connect to it, and it just sits on 'Connecting to '. I then tried running the console TerrariaServer.exe, and I can connect to that server from the same machine, but not the other one. All on port 7777. After the above didn't work and googling didn't help, my reaction was what you said: 'I wonder if.'
My reasoning being that if ping doesn't even work, then there's something really wrong. It didn't occur to me that ping could fail while other stuff works perfectly fine.–Jul 26 '12 at 16:04. Finally, I should mention that I had the above setup ('Host and Play') working fine yesterday, but it's stopped working today. I can't think of anything that's really changed though. Certainly nothing in Terraria settings has changed, so I concluded it had to be a Windows or router issue. After everything else so far, my strongest suspicion is that it has something to do with the fact that the second computer's IP address doesn't show at all (from either machine) when I do arp -a. I don't really know what that means, but I can see other devices (laptops), so I feel like it should be there.–Jul 26 '12 at 16:09.
@CamJackson Your reasoning was fine. With Windows XP. You didn't know that since Vista, the Windows Firewall would block Ping requests unless specifically told not to. But there is still something wrong here. Did you keep the firewall off while trying to play the game today?
Did the Vista machine (the one not running the server) have any updates at all overnight? It is likely not a router issue if it did work properly at one point. And indeed is something limited to just the single Vista machine (again, assuming that it is the one without the server).–Jul 26 '12 at 16:13.
Destination Host Unreachable Ping Solution
I can't believe this. I just reset the wireless adapter on the Vista machine, and now Ping and Terraria are both working. I hadn't thought to do that yet because the internet (and pinging the 2 routers) was working flawlessly on that machine.
Bagaimana Cara Mengatasi Destination Host Unreachable
No idea how the USB wifi dongle was causing local network traffic to fail. Also, I can only see 192.168.1.9 (the Vista machine) when doing arp -a from 192.168.1.2 (the Win7 machine). But I can see 192.168.1.2 from both. This all reinforces how little I know about networking. Thanks for your help!–Jul 26 '12 at 16:27. Solution that works for me is to unplug the router, and restart it.This has happened to me a number of times, out of the blue. I lose connectivity to the Internet, then I try to ping the router at 192.168.0.1, and it tells me that the destination host 192.168.0.9 is unreachable.
That's my laptop which I'm issuing the ping from.Tonight it seemed like the Roku, my laptop and my son's laptop all lost internet connectivity. Pinging, gave me the results I just mentioned.
Pulling power on the router and restarting it resolved the problem.It's a DIR-655 with pretty up-to-date firmware. The Roku is actually connected via wire.Would love to know why this happens, but it's a spurious problem, and I don't believe it has anything to do with settings in the router being incorrect. I found this (simple) fix for this kind of problem (I have a very similar network setup, including two routers, one for internet access, the other for WiFi): in my case my notebook was suddenly no longer able to access another computer in the same local network.After disabling the ethernet network port, my notebook was suddenly happy with my WiFi network again. Obviously my activated LAN card (without a LAN cable connected to it!) somehow interfered with the routing procedure of my Windows 7/64bit system.