# Unable to connect to the Vembu Integration Service in the target host. Check network connection status between the Vembu BDR Backup server and the target host

KB ID : 117008
Products :
Published : April 13, 2020
Created : April 13, 2020

Cause:

1) When the target host is not reachable [ UNC validation path validation [ admin$] ] 2) When there is an issue in accessing Windows Management Instrumentation [ WMI ] of your target host Solution: For Cause 1: When added target host is not reachable - UNC Validation Target host Remote share [ Admin$ ] is required for copying the VIS installer to the target machine.

You can confirm UNC validation by verifying the admin$share access manually from your Machine where VembuBDR or VembuVMBackup is installed. • Go to 'run' and type the following \IP\admin$
• In place of IP, provide the 'Hostname\IP' of the target machine

Make sure the target host is reachable and it must be added into your Network Address Translation(NAT) gateway.

Note: Make sure the target “HostName\IP” you are trying to use is added into your network address translation(NAT) gateway.

If it is reachable and you still face the above error, then proceed with the following verification:

Case 1: Make sure your firewall does not block remote connections. Add the below rule into your Inbound firewall rules in your target machine to ensure the same

   Step 1: Open control panel
Step 2: Navigate to System and Security >Windows Firewall >Advanced Setting
Step 3: In Windows firewall with advanced security, click Inbound Rules.
Step 4: Inbound rules > click new rule and proceed to opt for Predefined option
Step 5: In predefined drop-down > select “Remote Service Management “ rule and proceed with the default option to enable it and click finish.


Case 2: Make sure the following services are running in your target machine

   Server Service
Windows Remote Management (WS -management)
Cluster Service


For Cause 2: When there is an issue in accessing Windows Management Instrumentation [ WMI ] of your target host

Case 1: Make sure your firewall does not block any Windows Management Instrumentation function. Add the below rule into your Inbound firewall rules in your target machine to ensure the same

  Step 1: Open control panel
Step 2: Navigate to System and Security >Windows Firewall >Advanced Setting
Step 3: In Windows firewall with advanced security, click Inbound Rules.
Step 4: Inbound rules > click new rule and proceed to opt for Predefined option
Step 5: In predefined drop-down > select “Windows Management Instrumentation“ rule and proceed with the default option to enable it and click finish.


Case 2: Make sure the following services are running in your target machine

   Window Management Instrumentation
Cluster Service


Confirmation test:

When the above-mentioned solutions are verified, perform a pre-test using WBEM utility.

Step 1: Open “wbemtest” in your server/client machine

Step 2: In the namespace text box provide Target hostname\IP : \IP\root\cimv2

Example: \192.168.100.100\root\cimv2