Bastionhost automatically checks connectivity to managed assets on a schedule. You can also run a manual test to confirm reachability or troubleshoot connection failures. This topic describes how to configure periodic checks and perform manual connectivity tests.
Set up periodic connectivity checks
Log on to the Bastionhost console. In the top navigation bar, select the region where your Bastionhost instance resides.
In the instance list, find the target instance and click Manage.
In the left-side navigation pane, go to System Settings > Network Diagnostics.
In the Connectivity Check Settings section, select Periodic Check of Asset Connectivity and set a check interval.
Valid values: 1 hour to 24 hours.
Check results appear in the Network Status column of the asset list. Possible values are Normal, Port Exception, Network Timeout, and Proxy Server Exception. For details on each status, see Manage a host.
Run a manual connectivity test
Log on to the Bastionhost console. In the top navigation bar, select the region where your Bastionhost instance resides.
In the instance list, find the target instance and click Manage.
In the left-side navigation pane, go to System Settings > Network Diagnostics.
In the Connectivity Test section, enter the Target IP Address and Port, then click Test Connection.
The test result appears in a message on the page. For more information about how to troubleshoot connectivity exceptions, see Handle connectivity exceptions.
To check connectivity from the asset list, go to Assets > Hosts or Assets > Database and click Check Network Status of Asset. Network status on the O&M page syncs from the Assets page on each refresh. A manual test run from the O&M page does not write results back to the Assets page.
Handle connectivity exceptions
If a connectivity test fails, perform the following checks to identify the cause:
Check whether the security group rules allow access from the Bastionhost instance to the port of the specific host.
Check whether Cloud Firewall is deployed for the specific host and whether policies that allow access from Bastionhost to the port of the specific host are configured. For more information, see Configure access control policies in scenarios in which Cloud Firewall is deployed together with Bastionhost.
Check whether an on-premises firewall is deployed for the specific host and whether policies that allow access from Bastionhost to the port of the specific host are configured.
The Windows client crashes without an error message
If the Windows client crashes without an error message, perform the following checks:
Check whether other users can reproduce the issue.
Use the network diagnostics described in this topic to test connectivity.
Bypass Bastionhost and connect directly to the server by using MSTSC to rule out an issue with the server itself.
Check whether the security group allows the Bastionhost domain name and IP address.
Login fails with SocketTimeoutException
SocketTimeoutException is typically caused by network connectivity issues or a blocked port. Perform the following checks:
Use the network diagnostics to test connectivity.
If the network is unreachable, check whether the security group allows the Bastionhost outbound IP address, and check the server firewall or iptables rules and VPC connectivity.
If the connection recovers automatically, the issue might have been caused by a temporary network fluctuation or backend jitter. Continue to monitor the connection.