Preface
Introduction
- Managed File Transfer General Features
  - Workflow Automation
  - Ad-Hoc File Transfers and Collaboration
- Getting Started
  - Screen Tips
  - Login
Dashboard
Resources
Workflows
Task Reference
Services Overview
Users
Logs and Reports
Encryption
System
Appendix
Glossary Terms
- AES
- Asymmetric
- Asymmetric Cryptology
- Authentication
- Certificate
- Certificate Authority
- CIDR
- Cipher
- Cryptology
- CSV
- Decryption
- Diffie-Hellman/DSS
- Digital Signature
- DSA
- Element
- Encryption
- Fingerprint
- FTP
- FTPS
- Hash Function
- HTTP
- HTTPS
- ICAP
- Icon
- ISO format
- JCE Service Provider
- JDBC drivers
- JKS
- Key
- Key Alias/Key ID
- Key Pair
- Key Store
- MDN
- MMS
- Non-Repudiation
- Passphrase
- PKCS12
- Private Key
- Project
- Public Key
- Public Key Cryptology
- Public Keyring
- RSA
- Run Priority
- SAML
- Secret Key
- Secret Keyring
- Self-Signed Certificate
- SFTP
- Signing
- SMS
- SMTP
- SSH
- SSL
- SSO
- Symmetric
- Symmetric Cryptology
- URL
- Variable
- Verification
- XML

Managed File Transfer User Guide

10.5.3
- 10.5.0
- 10.4.0
- 10.2.3
- 10.2.2 HotFix 1
- 10.2.2
- 10.2.1
- 10.2

Back Next

FTP - Connection fails

There are two modes in FTP communications: Active and Passive.   In Active mode, the FTP server will attempt to connect back to a port on the

Managed File Transfer

FTP client in order perform the data transfer. The challenge with Active mode is that your firewall may block the FTP server from trying to open a port back into your network.   In Passive mode, the FTP server does not need to connect back to a port on the

Managed File Transfer

FTP client, which is a more firewall-friendly mode. Therefore, if you have problems with connecting to the FTP server, you may want to change the mode on the FTP server resource to Passive.

Rename Saved Search

Table of Contents

Managed File Transfer User Guide

Managed File Transfer User Guide

FTP - Connection fails

FTP - Connection fails