4
1
I have a machine running 4 VMs on it. There is one Fedora VM which is causing me some trouble. The IPs of the VMs are something like 10.100.100.* I have a Windows PC which is in the same network. It has an IP 10.100.25.77. When I reboot the Fedora VM, I am able to ping it from my Windows PC as well as use putty to ssh to it. The next day, I cant ping it or ssh from my Windows PC. However I can ping and ssh to the other VMs on the machine. If I ssh to one of the other VMs, I can ping and ssh to the Fedora VM. Next if I restart it, things get back to normal and I can access it without any issues. The IP of the VM doesn't change after rebooting and it is statically assigned
I would like to know what is causing this and how to get it fixed.
As a last resort, I am thinking of running a cron job to restart the VM every night, it is not a critical server, but will be generally used occasionally in the day time.
Nmap scan report for 10.100.100.81
Host is up (0.00018s latency).
Not shown: 995 closed ports
PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
111/tcp open rpcbind
139/tcp open netbios-ssn
445/tcp open microsoft-ds
MAC Address:XX:XX:XX:XX:XX:XX (VMware)
ssh and ping both timeout. I will run an nmap scan and post the results here in a few hours. One observation I made, is that I can ssh to it from any IP with the IP 10.100.100.* Dont know if this points to anything – iamme – 2012-10-08T05:10:24.027
1
I have asked another question following up on this http://superuser.com/questions/484816/what-is-the-point-of-system-autodeath
– iamme – 2012-10-08T07:04:14.867