-
Title
"Failed to establish connection to the host" Error adding new DB2 agents for instances on a Windows host -
Description
User is unable to add DB2 monitoring to a Windows host.
Error when setting up DB2 instances in Foglight.
When trying to add the DB2 Windows servers to Foglight getting one or both of the following errors.Failed to establish connection to the hostA command shell connection could not be established
-
Cause
CAUSE 1 * this is the most common issue *
Insufficient WMI permissions
CAUSE 2
Incorrect DB2 hostname used in the installer
CAUSE 3
DB2 host is unavailable
CAUSE 4
DB2 credentials are incorrect
CAUSE 5
Remote Registry service is not running
CAUSE 6
Ports for WMI are blocked
-
Resolution
RESOLUTION 1
* this is the most common issue *
DB2 agents that connect to Windows machines using the Agent Manager’s WindowsShellService need to make the following specific registry changes to allow the connection.
Please refer to KB 65870 to enable WindowsShellService access on registry keys.
RESOLUTION 2
Verify that the DB2 hostname is correct, that it can be resolved from the agent manager server, and that ports are open between the FglAM and monitored host.
RESOLUTION 3
Confirm that the DB2 host is available and online
RESOLUTION 4
Check that the specified OS credentials are trusted and are granted with required permissions to establish a connection with the host. Also confirm that the correct credentials are entered into the installer and that the accounts can access DB2 and/or the OS from outside of Foglight.
RESOLUTION 5
The Remote Registry service must be running in Windows to allow agents remote access to the registry.
RESOLUTION 6
Please ensure that the following ports are open bidirectionally between the FglAM and DB2 host with WMI connections
- DB2 specific port (e.g. default 50000)
- 135 (DCE/RPC Locator service, WindowsShellService, WMIConnection Service)
- 139 (NetBIOS Session Service),
- 445 (Windows shares)