Can't SSH into 10.5 macs - Port 22 Connection Refused

[#1]

I posted this problem a few months back and found a temporary solution which
works but really hamstrings my package pushing capabilities. Hoping now to
find a solution.

The problem is that I cannot SSH into most (but not all) of my 10.5.6 macs
on the floor. That includes localhost on my mac. All 10.5.6 macs have had
NAV 11 installed. I've uninstalled NAV on some macs during troubleshooting
but I am still not able to connect via SSH. The temporary workaround has
been to repair disk permissions in Disk Utility and reboot. Afterward, I am
able to SSH into the machine. However, I am denied the next day when I try
to SSH into the mac.

Here is a log of me trying to SSH into localhost on my mac:

SEA-LOPEZG:~ lopezgreg$ ssh -vvv localhost
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 localhost [::1] port 22.
debug1: connect to address ::1 port 22: Connection refused
debug1: Connecting to localhost [fe80::1%lo0] port 22.
debug1: connect to address fe80::1%lo0 port 22: Connection refused
debug1: Connecting to localhost [127.0.0.1] port 22.
debug1: connect to address 127.0.0.1 port 22: Connection refused
ssh: connect to host localhost port 22: Connection refused

Interestingly, there is one 10.5.6 mac running NAV 11 that I am able to SSH
into.

Any ideas as to why the connection is refusing on port 22?

G Lo
--
Gregory Lopez
Sr. Mac/Network Analyst

[tlarkin]

Sounds like remote log in is disabled, which allows ssh connections and
is different from remote desktop connections.

---

Thomas Larkin
TIS Department
KCKPS USD500
tlarki at kckps.org
blackberry: 913-449-7589
office: 913-627-0351

[#3]

Gregory, did you ever get an answer to this?
I had the same thing happen to me and remote login was on and the port responded to ping but it would not let a login happen. My solution was to just re-image the box and it works fine now.
I was not running Nav 11 and the box misbehaving was using the same image as 45 other lab machines.
I hope I do not run into this outside of a lab because that gets more complicated when dealing with a computer with a users data on it. Our lab machines do not store user data for students, but faculty and staff machines do.

Let me know if you found a fix.

Bruce