| Test | Command / Action | Expected Result | |------|------------------|------------------| | Connectivity | fcclient --test <server> -p 33001 | SUCCESS: UDP reachable | | Throughput | fcclient --send testfile.dat --rate 100M | Sustained >90% of line rate | | Log check | grep "blocked" /var/log/filecatalyst/* | No entries |

Are you seeing a specific (like "UDP transmission blocked") or is the application failing to launch entirely? Frequently Asked Questions and Troubleshooting

If a rule was accidentally changed, you can restore Windows Defender Firewall to its default settings to clear conflicting rules. 2. Network and Port Configuration

FileCatalyst blocking is almost always due to , aggressive UDP rate limiting , or NAT incompatibility . Resolution requires systematic testing at each network layer and, where necessary, architectural fallback to TCP/HTTPS. For mission-critical environments, proactive monitoring of UDP port reachability and firewall rule expiry is strongly recommended.

: 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.