VMware Converter Unable to Query Live Source Machine During Migration

Products

• Converter

Issue/Introduction

Users may encounter an error message stating "Unable to query the live source machine" when attempting to migrate a virtual machine using VMware Converter. This issue prevents the migration process from starting, impacting the ability to move VMs between environments.

Environment

- VMware Converter
- Destination environment: vCenter Server

Cause

This issue is typically caused by network connectivity problems between the VMware Converter server and the source machine. Potential causes include:

1. Blocked network services or ports
2. Firewall restrictions
3. SSL/certificate issues
4. Domain controller connectivity problems

Resolution

Follow these steps to resolve the "Unable to query the live source machine" error:

Verify basic network connectivity:

1. For Linux:
   1. Open a terminal on the Converter server.
   2. Use the `ping` command to test basic connectivity:
      • ping <source_machine_ip>
   3. If ping is blocked, use traceroute to identify where the connection fails:
      • traceroute <source_machine_ip>
2. For Windows:
   1. Open a Command Prompt as an administrator on the Converter server.
   2. Use the `ping` command to test basic connectivity:
      • ping <source_machine_ip>
   3. If ping is blocked, use tracert to identify where the connection fails:
      • tracert <source_machine_ip>

Test specific port connectivity:

1. For both Linux and Windows:
   1. Test connectivity to port 9089 (Converter communication):
      • telnet <source_machine_ip> 9089
   2. Test connectivity to port 443 (SSL communication):
      • telnet <source_machine_ip> 443
        
        Note: For Windows, you may need to enable Telnet Client in Windows features.

Check and configure firewall settings:

1. If the above tests fail, consult with your network team to:
   1. Ensure ports 9089 and 443 are open for Converter communication.
   2. Verify any other ports required by Converter are accessible
   3. Request a review of overall firewall rules and security policies that might be blocking Converter traffic.

Verify SSL certificates:

1. Open a web browser on the Converter server.
2. Navigate to https://<source_machine_ip>:9089
3. If you receive a certificate error, examine the certificate details.
4. Verify that the certificate is valid and trusted by your system.
5. If necessary, renew or replace certificates on both the source and Converter server.

Ensure domain controller connectivity:

1. Verify that the Converter server can communicate with the domain controller.
2. Check for any blocked services related to LDAP, Kerberos, or SMB protocols.
3. Consult with your network team to resolve any identified issues.

Review Converter logs:

1. For Linux:
   1. Navigate to the Converter log directory (typically /var/log/vmware-converter/).
   2. Open the most recent log file using a text editor:
      • sudo nano <log_file_name>
2. For Windows:
   1. Open File Explorer and navigate to C:\ProgramData\VMware\VMware vCenter Converter Standalone\logs.
   2. Open the most recent log file using a text editor like Notepad.
3. For both:
   1. Look for error messages related to connection failures or authentication issues.
   2. Address any specific issues identified in the logs.

Test with a non-production VM:

1. Identify a non-critical VM in your environment.
2. Attempt to migrate this VM using Converter.
3. If successful, compare network and security settings with the problematic VM.
4. Document and address any differences found.

Consult with network team:

1. If issues persist, provide your network team with the results of the above tests.
2. Request a comprehensive review of network path, routing, and security settings between the Converter server and the source machine.

If all else fails:

1. Consider setting up a test environment that mimics your production setup but with reduced security restrictions.
2. Attempt the migration in this environment to isolate whether the issue is related to network/security configurations or a problem with Converter itself.

Additional Information

- VMware Converter Network Port Requirements: VMware Ports and Protocols