SSh using preshared keys - Connection reset


I am having an issue trying to ftp to a remote server. I have configured the keys in my users profile however it appears when trying to ftp the remote server closes the connection. See below log. I have been able to successfully telnet to the remote host on the given port 6710. One thing to note is the keys in use were setup on another host which were used to connect to the same remote host (ive been assured that using same keys for a new source host to connect with same remote host should work fine). Please let me know what I should review.

Connecting to x.x.x.x...
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /usr/home/ingft/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to x.x.x.x [x.x.x.x] port 6710.
debug1: Connection established.
debug1: identity file /usr/home/ingft/.ssh/ssh_ingft_dsa_key type 2
debug1: loaded 1 keys
ssh_exchange_identification: Connection closed by remote host
Couldn't read packet: Connection reset by peer
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MongolianNoseFluteAuthor Commented:
Pre-shared key is synonymous with static plaintext password.
Your log does not use it, it uses insecure DSA keys that properly patched SSH server is very likely to reject.
Use RSA or EC keys instead.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MongolianNoseFluteAuthor Commented:
Thanks gheist, much appreciated. However, one concern i have - as mentioned these keys were taken from an existing server that was able to exchange with the remote server so I would have thought the keys themselves were not the issue. What do you think?
Which keys you took? Server keys?
You need to generate new keys with ssh-keygen 2048 and append content of generated .pub file to .ssh/authorized_keys file
And .ssh/authorized)keys should not be accessible to other users than one logging in.
Did you set the permissions correctly on the files after you copied the keys?  They don't work if they have the wrong access permissions.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SSH / Telnet Software

From novice to tech pro — start learning today.