VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
6 Replies Last post: Feb 26, 2009 1:12 PM by vmweathers  

Can't connect to converter helper VM posted: Feb 25, 2009 6:12 AM

Click to view vmaddict's profile Novice 18 posts since
Jun 6, 2006

Hi,

I'm trying to converte (with converter 4) a powered on linux machine to a VM on an ESX 3.5 server.
Converter server create the necessary VM, next boot correctly on converter helper iso, configure the network then try to connect this newly created VM .. but fail.

After some investigation I saw that the network interface is correctly configured (I tested both static and DHCP address) but I can't ping his IP address from everywhere except the ESX that support the VM.

This esx run several other VM correctly that can be reached from everywhere.

Thanks for your help.

Regards.

Re: Can't connect to converter helper VM

1. Feb 25, 2009 6:46 AM in response to: vmaddict
Click to view IamTHEvilONE's profile Virtuoso 1,402 posts since
Apr 1, 2008
Please note that the Helper VM will be on the vm port group that is selected in the wizard. This network needs to be accessible from where you are running converter and the source physical machine.

You can double check the settings in the first attachment on this post, and the second attachment is a port map for what is required.

Regards,

EvilOne

1 - Check the documents
2 - Search the forums
3 - Post Question

And remember to award points to those who assist you.

Re: Can't connect to converter helper VM

3. Feb 25, 2009 11:26 AM in response to: vmaddict
Click to view IamTHEvilONE's profile Virtuoso 1,402 posts since
Apr 1, 2008
So it looks like you have the "Helper VM" on 10.220.11.222 and is on the "Virtual Machine Network". Is this (vm@10.220.11.222) reachable from 10.206.36.161 over 443? I would assume so since the ESX host is on the same Subnet, but that's no guarantee.

Can you screen shot where this port group is on the ALTVM1 Host? (Configuration - Networking)

Lastly, once the conversion has errored out, right click the task and export the logs. that will give you a zip file to attach to this post as well.

Regards,

EvilOne

NOTE: If your problem or questions has been resolved, please mark this thread as answered and award points accordingly.

Message was edited by: IamTHEvilONE - clarity

Re: Can't connect to converter helper VM

4. Feb 25, 2009 10:45 AM in response to: vmaddict
Click to view vmweathers's profile Expert 470 posts since
Oct 14, 2008
Are you certain there are no firewalls between the server and the targetVM? The fact that the server (10.206.36.161) can communicate with the ESX's management IP (10.220.11.200) does not prove that it should be able to communicate with the helperVM's IP (10.220.11.222) Please try to determine where in your network the packets are being dropped. Maybe traceroute will help with that.

(If your question has been resolved please mark the answers as "Helpful" or "Correct".)

Re: Can't connect to converter helper VM

6. Feb 26, 2009 1:16 PM in response to: vmaddict
Click to view vmweathers's profile Expert 470 posts since
Oct 14, 2008
But, I think you asked the right question "Is this (vm@10.220.11.222) reachable from 10.206.36.161 over 443?" .. does it mean that we need to open port 443 on our ESX Firewall ?
Not sure what "our ESX firewall" means here, but you need to determine if there is a firewall on these network paths and open these ports if so:
10.206.36.161 --> 10.220.11.222:443
10.220.11.222 --> 10.206.11.50:22

Is this helper VM only reachable thru this port? This can explain why we can't ping this vm ?The HelperVM will respond to ICMP echo requests (pings) and also to requests on port 443, so it should be pingable if there is not a firewall denying ICMP echo requests, and if your routing and switching are all setup correctly per the connections I mentioned above.

Maybe you missed my earlier response: "Please try to determine where in your network the packets are being dropped. Maybe traceroute will help with that."

This problem is really outside of our control, if you are the network administrator then you should be able to do what I just requested. If you are not then you should forward this request to your network administrator and work with them to debug this.

UPDATE: finally, you really should post your logs so we can be sure about what you are experiencing (or send them via email to us -- private mail me on the forums and I'll send you an email address).

(If your question has been resolved please mark the answers as "Helpful" or "Correct".)

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities