upgrade CentOS - yum update
after reboot if it fails check:
netstat -an | grep LISTEN
/etc/init.d/sshd status
i.e if sshd is running fine.
Main Topics
Browse All TopicsHi
I have a centos VM that I'm using as a dev server to which I can connect using both dreamweaver and winscp over sftp. When the vm is freshly launched I can ssh into the bash shell using putty but oftne I find that after a while of working the putty client no longer connect, displaying the error:
network error: connection timed out.
I used to think that this only happened after my laptop (which runs vista as the host os) was woken up after going to sleep. So I disabled sleep altogether and this evening it's just happened again. I know I can get it back by just closing down and relaunching the centos VM, but this is too time consuming and it's been going on too long. Can anyone suggest what steps I should take to remedy it?
thanks in advance
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I tried all of your suggestions but none of them worked. So after further investigation I realised that the reason for the latest loss of ssh was nothing to do with the ssh service - it has been running fine all along. It was because of a recent change in my network config whereby I had switched to using the MS loopback virtual adapter and evidently Putty doesn't like this. I think I need to configure an ssh tunnel for putty to work but I'm unsure how exactly to do this. Theses are the details:
IP address of loopback connector: 192.168.0.1
IP address of centos VM 192.168.0.193
the reason I know that ssh is working is because I can still connect to the VM with putty when I go through the normal IP address assigned by my wifi network, however I need this to work when I'm out of range of that wifi net so I need putty to use the loopback connector if possible.
I did the traceroute and found that it was fine and then tried again by using the IP address of the VM (192.168.0.193) as the target for my putty session and it worked using the loopback. I've no idea why it didn't work before but I did reset the laptop at some point so looks like it's something intermittent. Hopefully not. anyway thanks for your help.
Business Accounts
Answer for Membership
by: ddiazpPosted on 2009-08-13 at 19:20:39ID: 25094836
Instead of rebooting the VM, you could run 'service sshd restart'.
Check your /var/log/messages log files for sshd and see if there's anything conflicting with it, maybe you installed another ssh daemon that takes over the port?
Once the ssh connetion times out, go onto the VM and do `service ssh status` and also double check the config files on /etc/xinetd.d/sshd/