Troubleshooting Common Acronis Files Connect Issues (Step-by-Step)

Troubleshooting Common Acronis Files Connect Issues (Step-by-Step)

1. Confirm environment and versions

• Check versions: On the Acronis Files Connect server and macOS clients, confirm you’re running supported, up-to-date versions.
• Compatibility: Ensure macOS and AD/SMB server versions are supported by your Files Connect release.

2. Issue: Macs can’t see file shares

1. Verify network connectivity: Ping the SMB server from a Mac and the Files Connect server.
2. Confirm service status: On the Files Connect server, ensure the Acronis Files Connect (afc) service is running. Restart if needed.
3. SMB discovery: From a Mac, try Finder > Go > Connect to Server and use smb://hostname or smb://IP to connect directly. If that works, NetBIOS/Bonjour discovery may be blocked.
4. Firewall and ports: Confirm ports 137–139 (NetBIOS) and 445 (SMB) are open between Macs, Files Connect, and SMB servers.
5. DNS & NetBIOS name resolution: Validate DNS entries for the SMB server and check WINS/NetBIOS settings if used. Add static host entries if necessary.
6. SMB protocol: Ensure the SMB server supports the SMB protocol versions required by macOS and Files Connect (SMB2/SMB3 preferred).

3. Issue: Authentication failures (invalid credentials)

1. Test credentials directly: From a Mac or Windows client, attempt to connect to the SMB share using the same account to rule out Files Connect.
2. Kerberos vs NTLM: If Kerberos is enforced, ensure time synchronization (NTP) between domain controllers, Files Connect server, and clients.
3. AD account restrictions: Check for expired passwords, account lockouts, or logon restrictions (e.g., workstation logon allowed).
4. Service account permissions: Verify the Files Connect service/account has read access to the shares and permission to query AD.
5. Logs: Inspect Files Connect and SMB server logs for authentication error codes to pinpoint causes.

4. Issue: Slow file browsing or transfers

1. Network checks: Measure latency and bandwidth between the Mac, Files Connect server, and SMB server. Resolve high latency or packet loss.
2. SMB signing and encryption: These can slow transfers—confirm if enforced and whether performance tuning is possible within security policy limits.
3. Antivirus and indexing: Temporarily disable AV or indexing on the SMB server to test impact. Exclusions for file-share traffic may be needed.
4. Resource usage: Check CPU, memory, and disk I/O on the Files Connect and SMB servers. Upgrade resources if saturated.
5. TCP tuning: Adjust TCP window sizes and SMB-specific tuning on servers if large transfers are common.

5. Issue: File/folder permission mismatches

1. Permission model check: Confirm whether permissions are NTFS ACLs, POSIX, or mapped—Acronis passes through NTFS ACLs by default.
2. Effective permissions: Use the SMB server’s tools to view effective permissions for the user on specific files/folders.
3. Inheritance and ownership: Inspect for broken inheritance or unexpected ownership causing access differences.
4. Syncing identity formats: Ensure UID/GID or SID mappings are consistent if integrating non-Windows systems.

6. Issue: Spotlight/metadata/search not working

1. Indexing configuration: Ensure Files Connect indexing (if used) is enabled and configured to crawl target shares.
2. Permissions for indexing: Indexing service needs read access to all indexed content.
3. Rebuild index: Trigger a full reindex and monitor logs for errors.

7. Issue: Symbolic links or resource forks behave incorrectly

1. SMB server support: Confirm SMB server preserves symlinks and resource forks; some NAS devices do not.
2. Acronis settings: Enable options to preserve HFS metadata/resource forks if present.
3. Test with small files: Create test symlinks and resource-forked files and verify behavior.

8. Useful diagnostic steps and commands

• From macOS:
  • ping
  • smbutil statshares -a
  • mount_smbfs //user@server/share /Volumes/share
• On Files Connect server:
  • Check afc service status and restart it.
  • Review Files Connect logs (location depends on install; check /var/log/ or product docs).
• On SMB server:
  • Check SMB/CIFS service logs and audit successful/failed auths.

9. When to escalate to Acronis or vendor support

• Reproducible crashes or service failures after updates.
• Authentication errors with clear AD/Kerberos issues beyond configuration scope.
• Bugs causing metadata loss or corruption.
  Provide logs (Files Connect logs, SMB server logs, macOS client logs), exact versions, and reproduction steps.

10. Quick checklist (do these first)

• Verify services are running and versions supported.
• Test direct SMB connection from a Mac.
• Confirm credentials work directly on SMB server.
• Check firewall/ports and DNS name resolution.
• Review logs for specific error codes.

If you want, I can produce a tailored checklist with exact commands and log paths for your OS and Files Connect version—tell me the server OS and product version.