I have problems using SCP...any suggestions?
Everytime I try to SCP a file from my office, I get the following message... ssh_exchange_identification: Connection closed by remote host lost connection I've tried various things, but no luck. Anyone have an idea? Thanks, Tom --- Tom Nielsen Neuro Logic Systems, Inc. 805.389.5435 x18 www.neuro-logic.com
On 09 Apr 2003 15:09:41 -0700
Tom Nielsen
Everytime I try to SCP a file from my office, I get the following message...
ssh_exchange_identification: Connection closed by remote host lost connection
I've tried various things, but no luck. Anyone have an idea? Just a guess. Check the versions of scp and ssh on both sides of the connection.
--
Jerry Feldman
On Wed, 9 Apr 2003, Jerry Feldman wrote:
On 09 Apr 2003 15:09:41 -0700 Tom Nielsen
wrote: Everytime I try to SCP a file from my office, I get the following message...
ssh_exchange_identification: Connection closed by remote host lost connection
I've tried various things, but no luck. Anyone have an idea? Just a guess. Check the versions of scp and ssh on both sides of the connection.
NOP. TCPWrappers is the enemy, can we take a look (you might want to forge the addresses though) at the contents of you /etc/hosts.[allow|deny] files... That message is typically a denial from TCPWrappers.
-- Jerry Feldman
Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
On Thursday 10 April 2003 00:09, Tom Nielsen wrote:
Everytime I try to SCP a file from my office, I get the following message...
ssh_exchange_identification: Connection closed by remote host lost connection
I've tried various things, but no luck. Anyone have an idea?
Thanks, Tom
hi Tom, Are you running sshd through inetd? if so check /etc/hosts.allow. One line should say something like: sshd: ALL (or instead of ALL just the networks / ip-addresses you want to connect from) If you are running sshd as a stand-alone daemon check /etc/ssh/sshd_config: check the AllowHosts and DenyHosts entries and see if 127.0.0.1 is allowed or denied. Also, if you Require ReverseMapping you'll be disconnected if your client doesn't have proper forward and reverse DNS mappings (e.g. localhost is 127.0.0.1 and 127.0.0.1 is localhost) - use nslookup to check that. HTH, Marcel
On Fri, 11 Apr 2003 23:05, Marcel Broekman wrote:
On Thursday 10 April 2003 00:09, Tom Nielsen wrote:
Everytime I try to SCP a file from my office, I get the following message...
ssh_exchange_identification: Connection closed by remote host lost connection
I've tried various things, but no luck. Anyone have an idea?
Thanks, Tom
Hi Tom, Please check the SuSE SDB, I think this may be related SuSE Linux 8.1 No Longer Allows SSH Login http://sdb.suse.de/sdb/en/html/ssh_heimdal.html -- Regards, Graham Smith ---------------------------------------------------------
I had a mysterious failure of ssh because when I created ~/.ssh/authorized_keys on the server side my editor wrapped it so that it was 4 lines instead of the (necessary) 1 line. Henry Harpending On Sat, Apr 12, 2003 at 01:18:23AM +1000, Graham Smith wrote:
On Fri, 11 Apr 2003 23:05, Marcel Broekman wrote:
On Thursday 10 April 2003 00:09, Tom Nielsen wrote:
Everytime I try to SCP a file from my office, I get the following message...
ssh_exchange_identification: Connection closed by remote host lost connection
I've tried various things, but no luck. Anyone have an idea?
Thanks, Tom
Hi Tom,
Please check the SuSE SDB, I think this may be related
SuSE Linux 8.1 No Longer Allows SSH Login http://sdb.suse.de/sdb/en/html/ssh_heimdal.html
-- Regards,
Graham Smith ---------------------------------------------------------
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
I don't have an authorized_keys file in .ssh, just known hosts. Last night I looked up hosts.deny and found all:all. I blocked it and I got farther. I managed to scp to a point where it asked me for my password. I entered it but it didn't work. Now I need to figure that out. Thanks, Tom On Fri, 2003-04-11 at 15:02, Henry Harpending wrote:
I had a mysterious failure of ssh because when I created ~/.ssh/authorized_keys on the server side my editor wrapped it so that it was 4 lines instead of the (necessary) 1 line.
Henry Harpending
On Sat, Apr 12, 2003 at 01:18:23AM +1000, Graham Smith wrote:
On Fri, 11 Apr 2003 23:05, Marcel Broekman wrote:
On Thursday 10 April 2003 00:09, Tom Nielsen wrote:
Everytime I try to SCP a file from my office, I get the following message...
ssh_exchange_identification: Connection closed by remote host lost connection
I've tried various things, but no luck. Anyone have an idea?
Thanks, Tom
Hi Tom,
Please check the SuSE SDB, I think this may be related
SuSE Linux 8.1 No Longer Allows SSH Login http://sdb.suse.de/sdb/en/html/ssh_heimdal.html
-- Regards,
Graham Smith ---------------------------------------------------------
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Tom Nielsen Neuro Logic Systems 805.389.5435 x18 www.neuro-logic.com
On 11 Apr 2003 15:19:20 -0700
Tom Nielsen
I don't have an authorized_keys file in .ssh, just known hosts.
Last night I looked up hosts.deny and found all:all. I blocked it and I got farther. I managed to scp to a point where it asked me for my password. I entered it but it didn't work. Now I need to figure that out.
Maybe this will help:
---------------------------------------------------------------------------------
ssh2 does not necessarily need a password, you could use
challenge-response authentication.
Generate your ssh-keys with
On Saturday 12 April 2003 00:19, Tom Nielsen wrote:
I don't have an authorized_keys file in .ssh, just known hosts.
Last night I looked up hosts.deny and found all:all. I blocked it and I got farther.
This is not a good idea (security-wise) if you run other services through inetd too, like ftp or telnet. Better leave "all:all" in hosts.deny and put "sshd:all" (or the networks/ip-adresses you want to connect from) in hosts.allow. Sorry, cant help you with your passwd problem. Try creating a new user and see if this new user can connect. Maybe you were trying to connect as root and sshd_config denies access for user root? cheers, Marcel
participants (8)
-
Graham Smith
-
Henry Harpending
-
Jerry Feldman
-
Marcel Broekman
-
Raúl Gutiérrez Segalés
-
Tom Nielsen
-
Tom Nielsen
-
zentara