Failure to Establish FTP Control Connection with Vault

Overview:

Root Cause:

Possible causes for not being able to establish TCP connection to port 21 on Host:

Solution:

Incorrect Host setting
- Ensure the Domain name of Vault is correct.
- If NLB(Network Load Balancing) is bypassed (Host setting set to vlt-<PODID>-ftp.veevavault.com) make sure the Vault is on the POD specified.
Incorrect Port
- Ensure port is set to 21. This is the default port for Explicit FTPS (FTPES).
- Implicit FTPS is not supported and defaults to port 990. Vault's service is strictly PASSIVE mode Explicit FTPS.
Customer-side firewall restrictions
- Ensure the firewall has open outbound connections to port 21 on the FTP server.
  - Windows(see link below for further instruction on setting up telnet):
```
telnet yourdomain.com 21
```
  - macOS:
```
nc -vz yourdomain.com 21
```

- If your destination IP range is restricted, contact Veeva Support to know IP Ranges that should be used.
- As the IP address of the NLB changes with every major release, if you have a specific IP in your rule and not the range, that would correlate to the service failing after a major release. It is recommended that customers always use IP address ranges to avoid this issue.

Product Support Portal