On Mon, 09 Feb 2004 03:46:17 -0500, Andrey Asadchev
<(E-Mail Removed)> wrote:
> Bob Parnes wrote:
>> Hello,
>>
>> I am running debian testing on several computers. Before today I used
>> rsync successfully to back up files to a dedicated backup computer.
>> Today I revived a third computer and tried running rsync but got the
>> follower error lines:
>>
>> protocol version mismatch - is your shell clean?
>> (see the rsync man page for an explanation)
>> rsync error: protocol incompatibility (code 2) at compat.c(70)
>>
[...]
>
> man sshd_config
>
> Protocol
> Specifies the protocol versions sshd should support. The
> possible values are ``1'' and ``2''. Multiple versions must be
> comma-separated. The default is ``2,1''.
>
> Check which version the client and server are running:
> cat /etc/ssh/sshd_config | grep Protocol
>
> Unless you have a specific need, use SSH2 instead of 1.
>
> If that does not help, try to debug your ssh connections by manually
> connecting and copying files.
> If manuall ssh works ok, increase the verbosity of rsync with "-v" option.
> If that does not give any clues, try using strace to see where it fails.
/etc/ssh/sshd_config shows Protocol 2 only, on both computers.
The trouble seems to be that I cannot ssh manually from one computer
to the other, in either direction. I get an error message,
"Temporary failure in name resolution."
I googled with this message. The appropriate posts stated that this
is a name resolution problem, and that I am missing entries in
/etc/resolv.conf. So I entered lines in that file,
nameserver 192.168.1.249
nameserver 192.168.1.250
and restarted ssh in both computers. However, the result was the same.
I can mount directories using NFS in either direction, so I don't see a
problem with the network.
What I don't understand is that I try to connect using the IP address,
so I don't see the reason for a name resolution failure. But this is
new to me, because I have had no trouble with rsync or ssh with other
network connections, with entries only in /etc/hosts.
Thanks for the troubleshooting map. If you can help with this, it may
get me over the hump.
Bob Parnes
--
Bob Parnes
(E-Mail Removed)