VMware vSphere

 View Only
  • 1.  Cannot convert a remote machine

    Posted May 30, 2009 09:30 AM

    Hi,

    I need to convert a remote windows 2003 server. However, VMWare converter says:

    Unable to contact the specified host 'x.x.x.x'. This might be because the host is not available on the network, there is a network configuration problem, or the management services on this host are not responding.

    The server is running fine and I have remote desktop access to it and use it constantly.

    1. Which management services is needed for Converter to operate?

    2. What else could it be?

    3. Alternatively I could run Converter locally on the remote machine, but there is not enough disk space. Is it possible to have it create the destination on an FTP server?

    It is Windows Server 2003, Web Edition, Service Pack 1.

    Thanks in advance.

    Martin



  • 2.  RE: Cannot convert a remote machine

    Posted May 30, 2009 10:22 AM

    Alternatively I could run Converter locally on the remote machine, but there is not enough disk space. Is it possible to have it create the destination on an FTP server?

    The destination could be a local usb drive, a mapped network path, or also a ESX Server or a vCenter Server.

    Andre

    **if you found this or any other answer useful please consider allocating points for helpful or correct answers



  • 3.  RE: Cannot convert a remote machine

    Posted May 30, 2009 03:22 PM

    Sounds like a name resolution problem. Check DNS and/or your hosts file entries. You can install converter directly in the server you want to convert, and from there, point the destination directly to ESX instead.

    -KjB

    VMware vExpert



  • 4.  RE: Cannot convert a remote machine

    Posted May 30, 2009 04:45 PM

    If it is a remote machine could it be a firewall issue? They say that they can connect via RDP but that would be a different port than converter would use correct?

    Here is a link to the required ports.

    http://communities.vmware.com/thread/61478

    Message was edited by: Chamon



  • 5.  RE: Cannot convert a remote machine

    Posted Aug 15, 2009 09:36 AM

    I had the same problem and installed the converter directly to the server and from there, point the destination directly to ESX.

    And my problem solved.

    Thanks a lot.

    ibrahim



  • 6.  RE: Cannot convert a remote machine

    Posted Oct 09, 2009 07:53 PM

    Hi People,

    We had the same problem. The solution was to recreate the default shares C$ and admin$ that didn't configured in a Windows 2000 SP4 server.

    After this was possible to start the virtualization

    Elvecio



  • 7.  RE: Cannot convert a remote machine

    Posted Jun 12, 2009 11:46 AM

    Hi,

    I need to convert a remote windows 2003 server. However, VMWare converter says:

    Unable to contact the specified host 'x.x.x.x'. This might be because the host is not available on the network, there is a network configuration problem, or the management services on this host are not responding.

    The server is running fine and I have remote desktop access to it and use it constantly.

    1. Which management services is needed for Converter to operate?

    2. What else could it be?

    3. Alternatively I could run Converter locally on the remote machine, but there is not enough disk space. Is it possible to have it create the destination on an FTP server?

    It is Windows Server 2003, Web Edition, Service Pack 1.

    Thanks in advance.

    Martin

    I have the exact same problem. I have installed VMWare Converter 4.0.1 standalone on my Windows 2003 Server. I start the conversion wizard, select "Powered-on machine" followed by "remote machine" and enter the IP address and credentials. I get the same error message:

    Unable to contact the specified host 'x.x.x.x'. This might be because the host is not available on the network, there is a network configuration problem, or the management services on this host are not responding.

    The Windows Firewall is off on the remote Windows XP host. I can RDP to it without problems and even see it in Network Neighbourhoods. I have followed the few pre-requisites in the manual, e.g. turned off windows firewall, simple filesharing off, same workgroup and not files are shared on the remote host except for the administrative shares, i.e. ADMIN$, C$ and IPC$.

    What's wrong?

    Thanks

    UPDATE: I tried to perform a hot clone of another remote windows xp pro computer on my network and I received the same error message. It doesn't make sense if no firewalls are enabled and I can RDP to the machines.



  • 8.  RE: Cannot convert a remote machine

    Posted Mar 02, 2014 09:01 PM

    The issue is FIREWALL and the management ports that are needed for a REMOTE machine to be converted are being blocked by a firewall rule. You must disable or open ports on your firewall. In case of my client, they needed a Vista machine to be converted and were getting exact same message. Once the Windows Firewall was DISABLED it worked great! Note that I said disabled. Do not stop the firewall service that will bring the entire firewall down just open the ports temporarily.

    For example in Windows Vista: Control Panel --> Windows Firewall --> Turn Windows Firewall ON or Off --> OFF

    I assume in case of 2003, if behind firewall, see if you can temporarily move it to a network port of the same network as your converter machine. Good luck!



  • 9.  RE: Cannot convert a remote machine

    Posted Jun 03, 2016 01:12 AM

    Hello,

    I was with the same issue. Check the version of your VMware Converter software.

    I was trying by using the VMware Converter 5.0 and just reinstalled the VMware Converter 5.5. It worked to me !

    alex-brweb@hotmail.com