SSH with no password problem

This question has been asked many times but non of the solutions seems to fix my problem.

On pc-a I (windows xp running Cygwin) I generated ssh keys and copied to pc-b (RHEL). I wal able to ssh to pc-b from pc-a with no problem.
Later I had to fix an NSF problem by changing user and goup ID of the user on pc-b. I also changed the rights to user dir.
all this broke the ssh set up. So I did all original steps to create no passwd ssh connection. However it would not work this time. I made sure there is no group write privilege for group on /home/user/.ssh path. I chmod .ssh to 700 and known_hosts to 600, user and group both set to user's for testing and none works.
This problem is duplicated for two redhat machines exactly the same way with none of the fixes working for any of them.

what else should I be looking at?

thanks in advance.
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.

Are you able to log in to the machine with this same username and using password?
Dushan De SilvaTechnology ArchitectCommented:
Please check firewall, ports are correctly opened.

BR Dushan
Artysystem administratorCommented:
Run 'sshd -ddd' on RHEL, it will run in foreground in debug mode, then try to connect from pc-a.

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
Firstly check connectivity:

telnet hostname 22

[spud@bigserver spud]# telnet 22
Connected to (
Escape character is '^]'.

Telnetting confirms that the port (ssh port 22) is correctly accessable and confirms that ssh is runing on it.

Next try and connect in verbose mode so that you get loads of useful info as to where the fault is:

ssh -vv

The -vv gives shed loads of information from the client side, and you'll see exactly at what point the connection fails or is rejected.

Finally, I always recommend this article if you need to go back to basics:


There are several reasons for this to happen, I had the same problem and I fixed it.

first , though, write here the errors reported in /var/log/secure whenever you try to connect.

if you get a permission denied error, try changing your sshd_config file to include the following:
RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile      .ssh/authorized_keys
also, you might want to copy the key file in your /etc/ssh/ssh_known_hosts file
root@host# cat yourkey.file >> /etc/ssh/ssh_known_hosts
root@host# service sshd restart
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
Linux Networking

From novice to tech pro — start learning today.