Troubleshooting "Can't Contact Server" Error When Connecting FileCloud to Active Directory
Original Question or Issue:
Customer reported that FileCloud could no longer connect to Active Directory. The integration was previously working but suddenly stopped. They were able to ping the AD server, but FileCloud returned the error "Can't Contact Server" when attempting to connect.
Environment:
- Product - FileCloud Server
- Version - 23.253
- Platform - Windows
Steps to Reproduce:
- Open the Active Directory/LDAP configuration in FileCloud.
- Attempt to connect to the configured AD server.
- Observe the error "Can't Contact Server."
Error or Log Message:
"Can't Contact Server"
Defect or Enhancement Number:
Cause:
The issue is not indicative of a FileCloud defect. While ICMP (ping) connectivity to the AD server is successful, LDAP/LDAPS connectivity is likely unavailable. This typically points to an environmental issue, such as firewall restrictions, DNS resolution problems, network policy changes, or LDAP/LDAPS service/port availability on the Domain Controller.
Resolution or Workaround:
- Advised the customer to verify with their network/Active Directory administrators whether any recent infrastructure or security changes were made.
- Confirm that the FileCloud server can establish connectivity to the Domain Controller over the required LDAP/LDAPS ports (e.g., 389 or 636, as applicable).
- Verify DNS resolution, firewall rules, network policies, and that the AD LDAP/LDAPS service is running and accessible.
- Once LDAP/LDAPS connectivity is restored, retry the AD connection from FileCloud.
Notes:
- Successful ping only verifies basic network connectivity and does not confirm that LDAP/LDAPS services are reachable.
- Since the integration previously worked, the issue is most likely due to an environmental or network change rather than a FileCloud application issue.