Search

Preface
Informatica Managed File Transfer Welcome Overview
- 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

User Guide

User Guide

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

Back Next

Passive

Passive

The Passive connection has the following settings:

Local Address: This is the IP address of the server hosting the port to which
Managed File Transfer
is listening. If available, you can also select it from the drop-down list.
Enabled: If set to Yes, the Data Connection for the Listener will attempt a traditional FTP connection to establish the data port.
Validate IP: This option specifies if the server should check if the IP address for the data connection is the same as for the control port. If the IP is not valid, the connection will fail. If left blank, the default is No.
Local Port: The local port on which the server will make the Active Data Connection. If none specified, any available port is used.

FTPS Server Configuration

Watch

Comments

0 COMMENTS

We’d like to hear from you! Log in to comment.