Troubleshooting: Connection Issues with Target Machine/Host | Knowledge Base Article

Unable to Establish Connection with Target Machine/Host

KB ID: 116005
Encountering the error message "Connection could not be established to the host" typically indicates difficulties in connecting to the designated target machine or host. Several factors may contribute to this problem.
Possible Causes:
1. Incorrect IP address entry for the target machine.
2. Unreachable state of the target host.
3. Absence of the Vembu Integration Service on the target host.
4. Inactivity of the Vembu Integration Service on the added target host.
To address this connectivity issue, follow the steps outlined below:
1. Check Host Reachability:
   Ensure that the target host is reachable from the source. Verify the accuracy of the IP address entry.
2. Verify BDRSuiteIntegrationService (BIS) Availability:
   a. Access the Control Panel on the Windows host machine.
   b. Navigate to the 'Programs' section and select 'Programs and Features.'
   c. Look for the presence of the VembuIntegrationService (BIS) agent.
3. Confirm BDRSuiteIntegrationService (BIS) Status:
   a. Open the 'Run' dialog and type 'services.msc.'
   b. Locate and inspect the status of 'VembuIntegrationService' [up to v52] or 'BDRSuite Delegation Service' [from v53].
   c. If the service is inactive, manually initiate it. If disabled, adjust the Startup type to 'Automatic' via service properties.
4. Check Port 42005 (BIS) or BDRSuite Delegation Service Port (BDS):
   a. Access the Control Panel on the host machine and select 'System and Security.'
   b. Choose 'Windows Firewall' and click 'Advanced settings.'
   c. Navigate to 'Inbound Rules' and locate the 'VembuIntegrationServicePort' [up to v52] or 'BDRSuite Delegation ServicePort' [from v53].
   d. If the port is disabled or blocked, enable it by:
      i. Right-clicking and selecting 'Properties,' then choosing "Allow the connection."
   e. If the port is absent, manually add it to the firewall:
      i. Click 'New Rule,' choose 'Port,' and proceed.
      ii. Select TCP port and specify "42005," then continue.
      iii. Allow the connection and apply the rule for Domain, Private, and Public profiles.
      iv. Name the rule as “VembuIntegrationService.exe” and finalize the addition.
5. Validation:
  Confirm the presence of the newly added rule in the 'Inbound Rules' section of the Windows Firewall.
By following these steps, you can address the issue of establishing a connection with the target machine/host for BDRSuite and BDRSuite Backup-for-Microsoft-Hyper-V. If the problem persists, please contact Vembu support for further assistance.
    • Related Articles

    • Troubleshooting: Unable to Establish Connection to the Target Host

      KB ID: 117433 Challenge: Encountering difficulties in connecting to the target host? Ensure that the specified SSH Port is valid and that the target host is powered on. Cause 1: The target host is offline. Cause 2: Firewall is enabled on the target ...
    • Unable to Establish Connection to KVM Host

      KB ID: 221012 Issue: Encountering the specified error in BDRSuite indicates a failure to establish a connection with the designated host, identified by either its Hostname or IP Address. The error message advises users to verify the installation and ...
    • Troubleshooting Network Path Connection Issues to Target Host

      KB ID: 117037 Issue: Encountering difficulties when trying to establish a network path connection to the target host with BDRSuite Cause: This problem occurs when the BDRSuite Backup Server or BDRSuite Backup Client cannot access the admin$ share ...
    • Unable to Connect to the Target Host

      KB ID: 117068 Cause: This error can occur due to the following reasons: 1. The target host's IP address is not reachable. 2. The Vembu Integration Service (VIS) is not available or not running on the target host. Solution: Cause 1: Ensure the ...
    • Unable to Connect to Target Host: Network Connection Issue Troubleshooting

      KB ID: 117043 Cause: Encountering connectivity issues when attempting to connect to the target host may result from the following scenarios: Cause 1: Unreachable Target Host (UNC Validation) The target host is not reachable, leading to issues with ...