Filecatalyst Infastructure |work|

On Linux servers, the default kernel network stack is tuned for general web traffic, not high-speed UDP bulk transfer. You must edit /etc/sysctl.conf :

[Remote User] --UDP--> Internet --(Port 33000-33020)--> [Firewall] --> [DMZ Gateway] | v [Internal AD] <--LDAP--> [FileCatalyst Central] <--REST--> [Internal Storage (Isilon)] | v [On-prem Client] --UDP--> [FileCatalyst Server] <--Plugin--> [S3 Cloud Archive] filecatalyst infastructure

This is the most distinct aspect of FileCatalyst. Standard firewall rules often break the transfer because admins treat it like standard FTP. On Linux servers, the default kernel network stack

FileCatalyst infrastructure is designed as a modular suite of server and client applications centered around a patented, UDP-based file transfer protocol. This architecture is engineered to bypass the speed limitations of traditional TCP-based protocols (like FTP or HTTP) by remaining unaffected by network latency and packet loss. Core Architecture Components FileCatalyst infrastructure is designed as a modular suite

While the goal is speed, you must prevent FileCatalyst from choking out other business applications (VoIP, Email).