yeah.... I thought of that as I was driving to social security in prescott
today.
:-)~MIKE~(-:


On Mon, Sep 10, 2012 at 1:17 PM, kitepilot@kitepilot.com <
kitepilot@kitepilot.com> wrote:

> Delete line 1 of /home/bmike1/.ssh/known_hosts or delete the file
> altogether.
> ET
>
>
> Michael Havensto writes:
>
>> After brian said opessh-server I remembered that is what I had to do
>> before. So I installed it and now it says:
>> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@**@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>> @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
>> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@**@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>> IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
>> Someone could be eavesdropping on you right now (man-in-the-middle
>> attack)!
>> It is also possible that a host key has just been changed.
>> The fingerprint for the ECDSA key sent by the remote host is
>> 5a:e4:46:fb:6e:52:a4:74:15:fd:**d5:83:1c:63:01:74.
>> Please contact your system administrator.
>> Add correct host key in /home/bmike1/.ssh/known_hosts to get rid of this
>> message.
>> Offending ECDSA key in /home/bmike1/.ssh/known_hosts:**1
>>   remove with: ssh-keygen -f "/home/bmike1/.ssh/known_**hosts" -R
>> 192.168.0.3
>> ECDSA host key for 192.168.0.3 has changed and you have requested strict
>> checking.
>> Host key verification failed.
>> So to add it would I:
>> cat
>> /home/bmike1/.ssh/known_hosts:**1>>5a:e4:46:fb:6e:52:a4:74:15:**fd:d5:83:1c:63:01:74
>>
>> ???
>> :-)~MIKE~(-:
>>
>> On Mon, Sep 10, 2012 at 6:08 AM, kitepilot@kitepilot.com <
>> kitepilot@kitepilot.com> wrote:
>>
>>> I'd try first:
>>> telnet 192.168.0.3 22
>>> That will validate that the remote SSH server is listening.
>>> If it is not, nothing else will work.
>>> YMMV...
>>> ET
>>>
>>> Amit Nepal writes:
>>>
>>>> "ssh: connect to host 192.168.0.3 port 22: Connection refused"  .. can
>>>> you check if the ssh server is listening on port 22 ? to me it looks
>>>> like
>>>> either the ssh port is changed to something else or the firewall is
>>>> blocking port 22 .. if the port is non default, you might want to use
>>>> rsync
>>>> -P<options>e "ssh -p <portNumber> ...................
>>>> Thanks
>>>> *Amit K Nepal
>>>> Infrastructure Engineer (RHCE)
>>>> omNovia Technologies Inc. <http://www.omnovia.com>
>>>> Amit K Nepal <http://www.amitnepal.com>
>>>> <http://www.amitnepal.com>*
>>>> On 9/10/2012 12:09 AM, Michael Havens wrote:
>>>>
>>>>> ssh: connect to host 192.168.0.3 port 22: Connection refused
>>>>>
>>>>
>>>>  ------------------------------****---------------------
>>>>
>>> PLUG-discuss mailing list - PLUG-discuss@lists.plug.**phoe**nix.az.us<http://phoenix.az.us>
>>> <PLUG-discuss@lists.**plug.phoenix.az.us<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<
>>> http://lists.PLUG.**phoenix.az.us/mailman/**listinfo/plug-discuss<http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss>>
>>>
>>>
>> ------------------------------**---------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.**phoenix.az.us<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<http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss>
>