SCP Connectivity Status
This table lists SCP statuses and possible corresponding connectivity statuses or alternate proxy connection statuses.
No. |
Status |
Possible Connectivity Status or Alternate Proxy Connection Status |
Remarks |
---|---|---|---|
1 |
No redirection |
No connectivity |
Could not connect to the configured proxy. |
2 |
Always redirecting |
Connected |
Connected to the configured proxy. Traffic Redirecting setting is set to always redirect. |
3 |
No policy or invalid policy applied (not redirecting) |
|
No Policy OR an invalid policy is applied to SCP. |
4 |
Blocked |
Blocked - CertValidationFailure |
HA proxy certificate validation failed – Secure Channel use case. |
5 |
Blocked |
Blocked - Secure channel Port Blocked |
Could not connect to the configured Secure Channel port. |
6 |
Blocked - Proxy unavbl |
No connectivity |
Could not connect to the configured proxy, and Block if proxy not available is selected in the policy. |
7 |
Blocked - Mutual Auth Failed |
Proxy Mistrust |
Mutual authentication with proxy fails and Block if mutual auth fails is selected in the policy. |
8 |
No redirection |
Connected to corporate network |
Connected to the configured corporate network. SCP can connect to the IP address configured in the policy. |
9 |
No redirection |
VPN |
Connected to the configured VPN. SCP can connect to the VPN IP address configured in the policy. |
10 |
Redirecting |
Out of corporate network |
Out of office. SCP can’t reach the corporate IP address configured in the policy. |
11 |
Bypass active |
No connectivity |
SCP is in bypass mode. |
12 |
No redirection |
ePO connectivity detection error |
Always redirect is not selected, the corporate network is not defined, and the endpoint is not connected to the VPN. So SCP tries to get ePO details from the registry and it can't find the ePOServer list from the following (or WOW6432Node) registry entry: HKEY_LOCAL_MACHINE\\SOFTWARE\\ |