[ https://issues.apache.org/jira/browse/NET-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16316515#comment-16316515 ]
Filipe Bojikian Rissi commented on NET-649: ------------------------------------------- Okay, I solved it on a fork, because it is an urgent solution for me, and I opened a Pull Request with the improvement, I opened a ticket following the guidelines in CONTRIBUTING.md. It was a simple change I made: {code:java} - __passiveHost = m.group(1).replace(',', '.'); // Fix up to look like IP address + __passiveHost = "0,0,0,0".equals(m.group(1)) ? _socket_.getInetAddress().getHostAddress() : + m.group(1).replace(',', '.'); // Fix up to look like IP address {code} The Pull Request link is [https://github.com/apache/commons-net/pull/28] Thanks for listening > 227 Entering Passive Mode > ------------------------- > > Key: NET-649 > URL: https://issues.apache.org/jira/browse/NET-649 > Project: Commons Net > Issue Type: New Feature > Components: FTP > Affects Versions: 3.6 > Environment: Fedora, Java 8 > Reporter: Filipe Bojikian Rissi > Fix For: 3.7 > > > In a situation where I passed, the FTP server is restoring 227 Entering > Passive Mode (0,0,0,0,156,126), so it was obvious to me that the problem is > on the server side and not on the API, but using the File Zila client and > analyze the log precebi that the same problem was also happening, so he > changed the route to use the IP of the server that returned this information > and thus manages to make the route correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)