In Windows Security , navigate to Virus & threat protection > Protection history to see if a FileCatalyst process (like TransferAgent.exe ) was recently blocked. You can select Allow on device to whitelist it.
: The FileCatalyst Server typically uses Port 21 or 22 for control and a range of UDP ports for data. If another application (like a standard FTP server) is using these, the service will be blocked from binding to the port. The Review: Troubleshooting & Resolution Issue Likely Cause Recommended Fix Connection Timed Out Firewall or Router blocking UDP traffic. filecatalyst blocked
: FileCatalyst relies on UDP (User Datagram Protocol) for its high-speed transfers. Most standard firewalls are configured to allow TCP but block unexpected UDP traffic. In Windows Security , navigate to Virus &
| Layer | Typical Blocking Mechanism | Specific Examples | |-------|----------------------------|--------------------| | | Stateful packet inspection, port blocking | UDP ports 33000–33009 (default) closed; SPI drops non-ICMP responses | | NAT Device | Port exhaustion or mapping failures | Symmetric NAT fails to maintain UDP hole-punching | | Proxy Server | Unsupported CONNECT methods or UDP proxying | HTTP/S proxies intercepting raw UDP traffic | | Endpoint Security | Application whitelisting, DLP rules | Antivirus heuristic blocks FileCatalyst’s kernel driver; DLP blocks file types | | QoS / Traffic Shaping | Rate limiting or drop of UDP bulk traffic | Router polices UDP flows >5 Mbps as “non-essential” | | IDS/IPS | Signature-based drop | False positive match on proprietary UDP pattern | If another application (like a standard FTP server)