You could try 'nmap localhost' on that machine to ensure that ssh is running on that port. Could it also be a protocol version problem? Like, the client is using protocol 1, but the sshd is only allowing protocol 2 connections? JC On 6/8/07, John R Pierce <pierce at hogranch.com> wrote: > > John Lagrue wrote: > > I tried that, and monitored the ssh.trace file with tail-f in another > > window. There were no obvious signs of error, only what looks like a > > child starting and then exiting. Mind you, it's been a fair few years > > since I last looked at a trace file! > > > lace your /etc/profile and ~/.bash_profile files with some `echo "I'm > here..."` kind of statements... see if its bombing somewhere > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070608/c76826e2/attachment-0005.html>