Benches macOS

6

No route to host (unreachable from Mac bu…

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Hi all,

Short description:

I'm getting a "no route to host" when pinging a server at work (and I'm doing this from home). If I do the same thing with my PC, it returns a response and it can find the server. Both computers are on DHCP, wireless via the Airport Extreme. I'm not using a firewall on any computer and I'm not forwarding any ports on the Airport Extreme. It's all wide open. This USED to work on the Mac and one day it suddenly just would not work! At least that's what I would like to think... 🙂

Long description:

This started a while ago, can't exactly tell when and what I could have done to cause this (or if this was caused by me at all).

One day I was unable to SSH into work like I do quite often from home. Also, VNC did not work (same server). Now the weird thing; I was able to FTP into the server on port 21. The server is also running FTP on another port, however this port was unreachable. I tried doing a ping to the server in the shell but all I got was "no route to host".

Since I am not running a firewall and I'm not using port forwarding (and all of this worked fine using that setup) I was clueless. I booted up my PC and connected it just the same way I do with my Mac; wirelessly and using DHCP through my Airport Extreme.

From the PC I was able to do everything, just like I used to.

I've found out that flushing the DNS cache might do the trick (lookupd -flushcache). This didn't work. I've also tried to do flush the firewall rules (ipfw flush) -- and this did nothing... probably because I'm not even running a firewall.

What should I do?

I hate having to reinstall the whole computer when Leopard is closing in...

Macbook Pro 2.16GHz, 2GB RAM, build 8R2218 Mac OS X (10.4.10)

6 replies

Sign in or join Beachball Help to reply.

  1. 0

    BDAqua

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Are you pinging by IP# or Name?

  2. 0

    Fredrik Averpil

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I've tried both nut it doesn't matter. Always the same "no route to host".

  3. 0

    Gnarlodious

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I wonder if your modem has a DNS server set? Seems like OSX is unable to get DNS for various protocols. I use the OpenDNS servers.

    This may have started with 10.4.10. Seems like Apple is getting ready to roll out a new SSH GUI interface.

  4. 0

    BDAqua

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Good pint gnarly... after re-reading, I think you've probably figured it out with flaky DNS for Macs.

  5. 0

    Etidorhpa

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Try opening the file /etc/ssh_config from the terminal (you will need to use sudo) with the editor of your choice... eg:

    sudo emacs /etc/ssh_config

    Add the following lines to the end:

    AddressFamily inet

    BindAddress
    x.x.x.x

    where
    x.x.x.x is the IP address of your computer behind your router (I use static IPs for consistent results).

    Save and see if you don't have better luck with ssh.

  6. 0

    Fredrik Averpil

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Weird thing is ... I had my computer powered off for like a day and brought it to work. At work I tried pinging the server again ... and now it worked!!

    When I got back home VNC, SSH and everything worked fine!

    Maybe those flushing commands did the trick but needed the computer to be restarted?

    I have not tried any of the suggestions in the thread ...it just started working.