KB Article #178140
FTP Server: Connections fail. Server listening on wrong Network Interface and IP Address
Problem
-- System with multiple IP Addresses and Network Interfaces
-- Multiple hostnames bound to different IP addresses
-- The ftpd.cfg field ADDRESS has another IP / hostname configured than the one the "hostname" resolves to. This might be required in clustered instances.
-- Check via netstat on what IP address the configured FTP port is currently listening. The exact netstat command varies per OS. E.g. "netstat -ona | grep [FTP port]" for Linux). The output shows not the expected IP Address, but the IP Address the hostname resolves to.
-- With Secure Relay, the initial connection works, but then the Master Agent shows below error, and the connection is ended.
ERROR 2016-08-29 16:20:45,280 incall [Thread-152] - [Incall:32238] Incall connection to /10.0.0.1:9234 refusedcom.axway.niocore.NIOCoreException: com.axway.niocore.NIOCoreException: Error while connecting: java.net.ConnectException: A remote host refused an attempted connect operation.
Resolution
- Edit the parameter file internet/server/classses/ftpd.cfg in free text.
- Remove the ADDRESS field/line completely (do not just leave the field with a blank value)
- Save, activate and restart
- Check again via netstat. Now the ftp server should listen to all network interfaces. For example:
netstat -ona | grep 9234
tcp 0 0 0.0.0.0:9234 0.0.0.0:* LISTEN off (0.00/0/0)