SSH can't connect
Jim
binarynut at comcast.net
Sat Oct 2 23:35:21 UTC 2010
On 10/02/2010 07:05 PM, JD wrote:
>
> On 10/02/2010 12:14 PM, Jim wrote:
>> On 10/02/2010 02:52 PM, JD wrote:
>>> On 10/02/2010 11:43 AM, Jim wrote:
>>>> ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22
>>> OK, So port 22 is open.
>>> Is this on the server where sshd is running or is this
>>> on the client where you are invoking /usr/bin/ssh ??
>>>
>>> If on the server, then take a look at the contents of
>>> the server's
>>> /var/log/secure
>>> /var/log/iptables (if you have configured iptables to log there)
>>> /var/log/messages
>>>
>>> and search for any messages pertaining to ssh or port 22 ...etc
>>>
>> /var/log/secure
>>
>> This is the only entries, and they repeated a number of different times.
>>
>> Sep 29 09:34:19 Acer sshd[1564]: Server listening on 0.0.0.0 port 22.
>> Sep 29 09:34:19 Acer sshd[1564]: Server listening on :: port 22.
>>
>>
>> /var/log/iptables
>>
>> There is no /var/log/iptables on server.
>>
>>
>>
>> /var/log/messages
>>
>> There is no entries in /var/log/messages for port 22.
> If you have admin privs on the server, can you edit
> /etc/init.d/sshd and modify the line
>
> $SSHD $OPTIONS&& success || failure
> to
> $SSHD $OPTIONS -d&& success || failure
>
> The -d will turn on debug.
>
> You will look for messages in the debug output where
> an incoming connection request is getting dropped.
>
>
>
I guess the debug output will show up in /var/log/messages ?
More information about the users
mailing list