Gonna toss out an obvious was there a hosts entry?
On Jun 17, 2011 8:49 AM, "Dazed_75" <
lthielster@gmail.com> wrote:
> These machines are all gigabit ethernet and connected to the same gigabit
> switch with little network traffic at the time of these attempts.
>
> On Fri, Jun 17, 2011 at 6:23 AM, Joseph Sinclair
> <plug-discussion@stcaz.net>wrote:
>
>> A connection timed out usually occurs due to:
>> 1) The ip address has no host (ping the same IP address, then use telnet
to
>> connect to port 22)
>>
>
> I realized after sending the message I should have included the successful
> ping of lapdog2 which was done by name. Telnet also fails.
>
> 2) tcp wrappers is dropping the connection (check /et/hosts.allow and
>> /etc/hosts.deny on lapdog3)
>>
>
> Nothing but comments in either file.
>
>
>> 3) the firewall on lapdog3 is dropping the connection (check the firewall
>> configuration on lapdog3 via iptables-save or ufw status)
>>
>
> ufw status was inactive at that time. As far as I can tell this morning,
> iptables says nothing about port 22 or ssh though last night I could have
> sworn it did and said to accept. In any case, I get the same result this
> morning though I am on a different machine trying to ssh to lapdog2.
>
>
>> 4) SSHD is not on port 22 or dropping connections (check sshd
configuration
>> on lapdog3)
>>
>
> It is using port 22. I do not know how to check for dropping connections.
> I did check syslog and dmesg/messages. NOTE: lapdog2 is able to ssh to
this
> machine but then ssh'ing back to lapdog 2 gives the same results as doing
it
> directly on this machine.
>
>
>>
>> On 06/17/2011 02:14 AM, Dazed_75 wrote:
>> > Ignore the original question. I checked lapdog2's IP in a terminal that
>> was
>> > logged into a different machine. The ssh was using the right IP but
>> getting
>> > this result and I cannot figure out why:
>> >
>> > larry@hammerhead:~$ ssh -v lapdog2
>> >> OpenSSH_5.8p1 Debian-1ubuntu3, OpenSSL 0.9.8o 01 Jun 2010
>> >> debug1: Reading configuration data /etc/ssh/ssh_config
>> >> debug1: Applying options for *
>> >> debug1: Connecting to lapdog2 [192.168.2.124] port 22.
>> >> debug1: connect to address 192.168.2.124 port 22: Connection timed out
>> >> ssh: connect to host lapdog2 port 22: Connection timed out
>> >> larry@hammerhead:~$
>> >>
>> >
>> >
>> > On Fri, Jun 17, 2011 at 2:00 AM, Dazed_75 <lthielster@gmail.com> wrote:
>> >
>> >> I tried to ssh from this machine to my laptop (ssh lapdog3) and find
>> that
>> >> ssh is somehow using an old IP instead of doing name resolution on th
e
>> name
>> >> lapdog2 which now has a new lease on a different IP.
>> >>
>> >> 1) How do I fix this?
>> >> 2) Why does ssh use an old, apparently, stored IP?
>> >>
>> >> --
>> >> Dazed_75 a.k.a. Larry
>> >>
>> >> The spirit of resistance to government is so valuable on certain
>> occasions,
>> >> that I wish it always to be kept alive.
>> >> - Thomas Jefferson
>> >>
>> >
>> >
>> >
>> >
>> >
>> > ---------------------------------------------------
>> > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
>> > To subscribe, unsubscribe, or to change your mail settings:
>> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>>
>>
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
>> To subscribe, unsubscribe, or to change your mail settings:
>> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>>
>
>
>
> --
> Dazed_75 a.k.a. Larry
>
> The spirit of resistance to government is so valuable on certain
occasions,
> that I wish it always to be kept alive.
> - Thomas Jefferson
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)