For the past few decades, many organizations have used the SSH File Transfer Protocol (SFTP) as their main file transfer solution. It’s more secure and less prone to connectivity issues than the archaic File Transfer Protocol (FTP). However, it’s becoming increasingly clear that SFTP is also starting to age. Companies struggle to meet today’s business needs and use cases with purely SFTP-based solutions.
Read MoreTopics: JSCAPE MFT, SFTP, sftp server, mft solutions
Some people are unsure of the difference between MFT Gateway and SFTP server. These are two distinct applications with different core functionalities. Combine them, and you’ll get a more secure, compliant, and highly available file transfer environment.
Read MoreTopics: JSCAPE MFT, sftp server, mft gateway
By default, SFTP (SSHfile transfer protocol) uses port number 22, but can be configured to listen on ports other than port 22.
SFTP only requires one port for moving data over an internet connection, making SFTP more secure and easier to use than other file-sharing protocols, such as FTP/S, which require trading partners to open a range of ports behind their firewalls.
Read MoreTopics: SFTP, ssh, sftp server, sftp port number
Windows, including Windows 10, lacks a built-in SFTP client, making it challenging for users to securely transfer files to an SFTP server. This post guides Windows users on setting up an alternative solution for secure file transfers.
Read MoreTopics: File Transfer Clients, Secure File Transfer, SFTP, ssh, Windows SFTP Client, sftp server