There are two main issues that can arise regarding a connector:

1. An application is unreachable.
2. Connector is offline.

Application is Unreachable

Check if the application can be reached:

HTTP: curl -kfsSLv -m 5 http://internalIP_or_FQDN:port
HTTPS: curl -kfsSLv -m 5 https://internalIP_or_FQDN:port
SSH: curl -v telnet://<internalIP_or_FQDN>:22
RDP: curl -v <internalIP_or_FQDN>:3389

In case an application cannot be reached, ensure there are no routing or firewalls blocking access from the Connector to the internal apps.

DNS resolution

In some cases the Connectors are on a network where a different DNS server is utilized than expected. Running the following commands checks whether the Connector is able to resolve internal applications via DNS:

• nslookup hostnameORfqdn
• dig hostnameORfqdn

Connector is Offline

You can tell whether the connector is offline by checking the connectors page in the Management Console. Go to Settings -> Connectors.

In case a connector is offline, try the following steps:

• Try to reboot your machine.
• To make sure a firewall isn't blocking outbound connectivity from Connector to the Axis backend. When it works it will end with displaying some certificate information:

The following script checks connectivity to Axis Security:

curl -kfsSLv -m 5 backend-tcp.axissecurity.com:443

My Connector is Partially Connected and the Axis Client is Not Online

If the connector shows that it is partially connected and the Axis Client is not online in the management console, verify the following:

Common Connector Misconfigurations

If your connector is not working, use the following table to check for the following: