Skip to main content
Question

File Analytics Setup Fails: Domain Connection Issue

  • November 12, 2025
  • 3 replies
  • 50 views
T

I’m trying to enable File Analytics for my Files instance, but I keep getting the error: “Can’t connect to provided domain” when attempting domain join.

Here’s my setup and what I’ve verified so far:

  • Environment: AD server, Files server, and File Analytics server are all deployed within the same cluster.
  • Files Configuration:
    • SMB authentication is enabled under Authentication.
    • Administrator account is configured under Manage Roles.
  • Connectivity Checks:
    • From the File Analytics console, I can successfully ping the AD server and perform nslookup for name resolution.
  • Despite these checks, enabling File Analytics for Files still fails with the domain connection error. I’m running out of ideas at this point.

Has anyone encountered a similar issue? Are there specific settings or configurations I should double-check? Any guidance or troubleshooting tips would be greatly appreciated.

3 replies

T
  • Tominaga
  • Author
  • Adventurer
  • November 12, 2025

Prism Central: 2024.3.1.2
AOS: 7.0.1.5
Files 5.2
Analytics 3.4.2

aluciani
Forum|alt.badge.img+34
  • aluciani
  • Chevalier
  • November 14, 2025

Hey ​@Tominaga 

Look this over to see if it helps. Always test in dev or staging before trying this in production.

Confirm DNS and Name Resolution

  • Ensure the File Analytics VM can resolve the AD domain name.
  • Run nslookup <domain-name> from the File Analytics VM and verify it returns the correct AD server IP.
  • If DNS is external, confirm the correct DNS servers are configured in Prism Central and on the File Analytics VM.

Validate Network Connectivity

  • Check that the File Analytics VM can reach the AD server on required ports:
  • TCP 389 (LDAP)
  • TCP 445 (SMB)
  • TCP 88 (Kerberos)
  • You can use telnet <AD-IP> <port> or nc -zv <AD-IP> <port> for testing.

Verify Authentication Settings

  • Under Authentication, confirm:
  • SMB authentication is enabled.
  • The administrator account has the correct permissions to join computers to the domain.
  • Ensure the account is not locked and the password is correct.

Check Cluster and File Analytics Configuration

  • All components (AD server, Files server, File Analytics VM) should be on the same cluster or have proper routing if external.
  • Confirm the File Analytics VM has the correct NTP settings and time sync with AD (Kerberos requires time sync within 5 minutes).

Review Logs for Detailed Errors

  • On the File Analytics VM, check:
  • /var/log/fa/fa.log
  • /var/log/fa/domain_join.log
  •  
  • Look for Kerberos or LDAP-related errors.

Common Fix
If all checks pass, try:

  • Restarting the File Analytics VM.
  • Re-entering the domain join credentials in the File Analytics configuration.
  • If using a custom OU, verify the path is correct.

Helpful Documentation

T
T
  • Tominaga
  • Author
  • Adventurer
  • November 18, 2025

Thanks.
had already checked connectivity with the AD server, but I hadn’t verified NTP synchronization.
I’ll check that now.

Terms & ConditionsAccessibility statement