SSH hangs accessing CentOS4 in VMware
CentOS 4, VMware and SSH are three things that I cannot get to work together. Let me tell you the whole story and hopefully you'll be able to spot a blindingly obvious mistake that I can't.
I have a VMware install on my Kubuntu Feisty laptop. (The free edition that bugs you to get a free serial when you install, so they get another email to spam). This copy of VMware runs Debian, Windows XP, and if you're feeling extremely patient, Windows Vista without any problems that I can see.
So, I decided to make a CentOS image so I can learn how it differs Debian (not having used Redhat-based distros before). That way I can break a vmware image and not my VPS. So northie and I installed CentOS 4 inside VMware from an ISO. Networking in VMware was set to Bridged, so the guest distro gets an IP from the router's DHCP server. Everything installed without any errors, and the CentOS vm could wget things off the internet. I typed /etc/init.d/sshd start
On the VMware host, I typed ssh root@192.168.1.11
I was shown and accepted the vm's key, and then ssh hung. It didn't cut me off, or say connection closed and show a prompt. It just sat there for 2 minutes and then timed out. As if there was some major packet loss.
I remembered specifically disabling the firewall and SELinux at install time, but i peeked around /etc/selinux and other places to confirm this. I then tried other vmware networking settings, such as NAT. Then I copied /etc/ssh/sshd_config from my laptop to the vm. I added another user onto the vm and SSH into that. Finally I downloaded a pre-made CentOS 4 VMware image and tried that. But every time it would just hang. Occasionally it would ask for a password, then hang and time out. But I couldn't get a prompt through SSH. I can ping the vm fine though
I then decided to see if the VM could SSH itself:ssh localhost worked, yet ssh 192.168.1.11 showed its certificate then hung. However, sshd was set to bind to all interfaces (and was listening, I checked) and ifconfig proved 192.168.1.11 was an IP of the vm
If anyone knows how to fix this, please tell me!
comments