Alvaro Zuniga <[EMAIL PROTECTED]> writes:
>> Are you sure the sshd process is running? The first thing I would try if I
>> didn't have access to the box is to portscan the IP using nmap to see if
>> the ssh port (port 22) is open. If I did have access, a quick "ps aux |
>> grep sshd" would do the trick.
>>
>> Are you sure you're hitting the right IP address? If this is a Cox
>> connection, it might have been assigned a new IP address via DHCP.
>
> Everything is ok. I connect directly, times out. I connect to another
> computer
> and from that computer stablish the connection, not problem.
You can ping the machine directly? Or there any other open ports that
you can connect to ('telnet hostname port#')? Does 'telnet hostname 22'
give you a connect string? What does 'ssh -v' report? Is the remote machine
running a firewall? how about portsentry? Can you check the logs on the remote
machine?
--
Scott Harney<[EMAIL PROTECTED]>
"...and one script to rule them all."
gpg key fingerprint=7125 0BD3 8EC4 08D7 321D CEE9 F024 7DA6 0BC7 94E5
