Benches macOS

13

Can't ssh into my own mac

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I'm really banging my head against the wall with this one.

I can't seem to ssh into my own mac. I've made sure Remote Login is on and that the Firewall is allowing connections. I was starting to think it had something to do with Norton Antivirus 11 but I installed NAV 11 on a freshly built 10.5 mac and was able to ssh into it (from my mac and from that one). I also tried with 10.5.2, 10.5.4 and 10.5.5 with success.

It's as if port 22 keeps toggling off despite the GUI saying otherwise. Here's the message I get when I try to ssh into my own mac:

XXX-XXXXX:~ xxxxxxxx$ ssh -vvv 127.0.0.1

OpenSSH_5.1p1, OpenSSL 0.9.7l 28 Sep 2006

debug1: Reading configuration data /etc/ssh_config

debug2: ssh_connect: needpriv 0

debug1: Connecting to 127.0.0.1 [127.0.0.1] port 22.

debug1: connect to address 127.0.0.1 port 22: Connection refused

ssh: connect to host 127.0.0.1 port 22: Connection refused

I've got a Macbook Pro w/ CS3, NAV 11, Office 08, etc. Any ideas?

13 replies

Sign in or join Beachball Help to reply.

  1. 0

    nerowolfe

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Welcome to Apple Discussions:

    My first and gut reaction would be to lose Norton, which, IMO
    is itself a virus.

    ClamAV is fine for Macs and there are no virii anyway. Only malware that one has to invite onto the platform.

    I have had similar problems, albeit in the PC world with similar products in which they would not always act the same way. Removing Norton completely is not an easy task and I suspect that it is the problem.

    It may simply be that an uninstall/reinstall of Norton will fix things. I have no faith in Norton anymore.

    You might create a new user and see if the ssh issue exists with the new user as well.

  2. 0

    BobHarris

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I can *ssh 127.0.0.1* without any problems. I also have the same ssh version: "OpenSSH_5.1p1, OpenSSL 0.9.7l 28 Sep 2006". I'm using Mac OS X 10.5.5 on a MacBook.

    Do you have a permissions problem?

    If you $HOME directory is writable by Group or Other, ssh will start to get cranky.

    If $HOME/.ssh is anything except drwx------, ssh will get cranky.

    If some of the key files in $HOME/.ssh do not have the correct permissions, ssh will get cranky.

    See *man ssh* for all the permissions ssh requires on key files.

    Did you add anything to /etc/ssh_config that might change ssh behavior?

    Did you add anything to /etc/sshd_config?

    Have you tried disabling the firewall as an experiment?

    Have you tried disabling NAV as an experiment?

  3. 0

    nerowolfe

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Welcome to Apple Discussions:

    My first and gut reaction would be to lose Norton, which, IMO
    is itself a virus.

    ClamAV is fine for Macs and there are no virii anyway. Only malware that one has to invite onto the platform.

    I have had similar problems, albeit in the PC world with similar products in which they would not always act the same way. Removing Norton completely is not an easy task and I suspect that it is the problem.

    It may simply be that an uninstall/reinstall of Norton will fix things. I have no faith in Norton anymore.

    You might create a new user and see if the ssh issue exists with the new user as well.

  4. 0

    Tim Haigh

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    If the mac you want to be the ssh server is behind a router then you don't really need to use its built in application firewall.

    The way to test ssh is to make sure your client and server are both on the same LAN turn off the built in firewalls.

    Then engage the connection using the local ip of the server e.g 192.168.0.10 but make the login very verbose so you can see a full description of the login process.

    eg

    ssh -vvv [email protected]

    If you dont specify a username make sure the account name your sshing from is has an account on the server with exactly the same name.

  5. 0

    Marc Wilson

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    G Lo wrote:

    XXX-XXXXX:~ xxxxxxxx$ ssh -vvv 127.0.0.1

    Who says sshd is listening on localhost?

  6. 0

    BobHarris

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I can *ssh 127.0.0.1* without any problems. I also have the same ssh version: "OpenSSH_5.1p1, OpenSSL 0.9.7l 28 Sep 2006". I'm using Mac OS X 10.5.5 on a MacBook.

    Do you have a permissions problem?

    If you $HOME directory is writable by Group or Other, ssh will start to get cranky.

    If $HOME/.ssh is anything except drwx------, ssh will get cranky.

    If some of the key files in $HOME/.ssh do not have the correct permissions, ssh will get cranky.

    See *man ssh* for all the permissions ssh requires on key files.

    Did you add anything to /etc/ssh_config that might change ssh behavior?

    Did you add anything to /etc/sshd_config?

    Have you tried disabling the firewall as an experiment?

    Have you tried disabling NAV as an experiment?

  7. 0

    Greg Lopez

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I did an ls -la to check permissions and $HOME/.ssh permissions look like this:

    drwx------ 3 xxxxxxx staff 102 Dec 4 19:14 .ssh

    I haven't added anything to /etc/sshd_config. I have tried to disable the firewall (through GUI) and have disabled NAV to no avail.

    I'm thinking of reinstalling NAV 11 to see if it will work. I can't use a different AV due to office policy.

    I'm still learning unix so any other commands you could suggest would be appreciated. 🙂

  8. 0

    BobHarris

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Can you ssh into your Mac from another system?

    Have you tried:


    ssh localhost

    Do you have anything strange in /etc/hosts ? I would expect to see somthing like:


    127.0.0.1 localhost
    255.255.255.255 broadcasthost
    ::1 localhost
    fe80::1%lo0 localhost

    it is the 127.0.0.1 line I'm thinking about.

    But also notice there are other
    localhost entries for IPv6, so using
    localhost works, but
    127.0.0.1 does not, then maybe it is an IPv4 problem, and IPv6 is working for
    localhost.

    Do you have IPv6 enabled? As an experiment ONLY try disabling IPv6. You can turn it back on after the experiment. This may be a bit of old folklore, but in a previous Mac OS X version (Panther I think), IPv6 and ssh did not play well together. It think it has been resolved since then, so I'm just throwing this out as ideas at this point.

    System Preferences -> Network -> Advanced -> IPv6 -> Off

    Like I said, you can turn it back on if this experiment doesn't change anything.

  9. 0

    Greg Lopez

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Got it!

    The problem was NAV 11. I ended up uninstalling and shutting down. I was able to ssh in after I booted up. Then I reinstalled NAV 11 but couldn't connect through ssh after the install. In NAV 11 prefs, I turned on Auto-Protect and Vulnerabilty Protection and then rebooted. I was able to ssh in after the reboot.

    Thanks to those who helped!

  10. 0

    Greg Lopez

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    nerowolfe probably most deserves credit.

    The problem was NAV 11. I ended up uninstalling and shutting down. I was able to ssh in after I booted up. Then I reinstalled NAV 11 but couldn't connect through ssh after the install. In NAV 11 prefs, I turned on Auto-Protect and Vulnerabilty Protection and then rebooted. I was able to ssh in after the reboot.

    Thanks to those who helped!

  11. 0

    Greg Lopez

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Just a follow-up:

    It appears NAV 11 changes some preferences around which contribute to not being able to ssh into my mac. If after NAV 11 reinstall you still have issues, try running Disk Utility>Repair permissions in order to

    fix. Here is my log:

    Repairing permissions for ³Macintosh HD²

    Reading permissions database.

    Reading the permissions database can take several minutes.

    User differs on "private/etc/hostconfig", should be 0, user is 99.

    Group differs on "private/etc/hostconfig", should be 0, group is 99.

    User differs on "System/Library/LaunchDaemons/ssh.plist", should be 0, user

    is 99.

    Group differs on "System/Library/LaunchDaemons/ssh.plist", should be 0,

    group is 99.

    Group differs on "private/etc/cups", should be 0, group is 26.

    Permissions differ on "private/var/spool/cups/cache/rss", should be

    drwxr-xr-x , they are drwxrwxr-x .

    Permissions repair complete

  12. 0

    sfelix

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi nerowolfe,

    i'm also having the same issue but perhaps for slightly different reasons. I can't use ssh to connect to any server and i am not using NAV, my firewall is disabled. I first noticed this after I installed the 10.5.6 update. Any ideas would be appreciated, this is quite aggravating. Thanks.

  13. 0

    Andre John Mas

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    An easy test to see if it is a connectivity issue:

    - on the machine you are trying to connect to: ssh localhost

    - on the machine you are trying to connect from (replace hostname with the name/address): telnet hostname 22

    If the former works, but not the latter then there are chances it is a connectivity issue. If the former does not work then ssh is not running on the remote server. You could also try pinging the machine to see if it responds.