Serv-U MFT Server provides RFC-compliant implementations of FTP, FTPS (via SSL/TLS), SFTP (via SSH2) for FTP client,
SSH client and automated file transfers, plus HTTP/S for web transfers, mobile transfers, and web administration.
File Transfer Protocol Guide
The five file transfer protocols Serv-U supports each have their own advantages and disadvantages. Use the following chart to help determine which protocols you should support in your deployment.
Automated or Scripted Transfer*
Legacy or Mainframe Access
Strong Authentication (2 Factor)
"Anywhere Access" (Mobile or Web)
Single Firewall Port
Native Windows Client
Native Linux/Unix Client
* Serv-U offers file transfer scheduling using FTP Voyager.
1 = Some legacy systems have FTPS or SFTP clients; check with your local administrators.
2 = HTTP/S web browsers are usually available on Linux/Unix platforms when they are shipped with a GUI interface.
FTP and FTPS (via SSL/TLS)
Guaranteed compatibility with every major FTP client
RFC-compliant FTPS supported by X.509 certificates
Strong two-factor authentication with client certificates
On-the-fly data compression
Integrity checks via XCRC, XMD5, XSHA1, etc.
Date/time preservation via MDTM
Change password option
IPv6 and IPv4 support
FIPS 140-2 validated cryptography (requires Serv-U MFT Server)
SFTP (via SSH2)
Guaranteed compatibility with every major SSH client