[
https://issues.apache.org/jira/browse/NET-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292869#comment-13292869
]
Sebb commented on NET-469:
--------------------------
The response to PASV is
bq. 227 Entering Passive Mode (85,88,142,160,117,69)
This means that the server is listening on the IP address 85.88.142.160 at the
port 117*256+69 = 30021.
That is the address that NET is trying to reach, and the one for which no route
is found.
The response does not seem right, because the server is at 91.231.x.x
Try pinging 85.88.142.160 from your client host.
By the way, the TCP dump appears to be truncated, the PASV reply in particular
is incomplete.
Can you provide dumps for both NET and command-line FTP for comparison?
> Erroneous "No route to host" on upload failure
> ----------------------------------------------
>
> Key: NET-469
> URL: https://issues.apache.org/jira/browse/NET-469
> Project: Commons Net
> Issue Type: Bug
> Components: FTP
> Affects Versions: 3.1
> Environment: Java(TM) SE Runtime Environment (build 1.6.0_31-b04)
> Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode)
> Linux 2.6.39-gentoo-r3 #6 SMP PREEMPT Thu Dec 8 19:34:57 WET 2011 x86_64
> Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz GenuineIntel GNU/Linux
> Reporter: Vasco Figueira
> Attachments: dump.txt
>
>
> The example code at
> http://commons.apache.org/net/examples/ftp/FTPClientExample.java
> ...fails to store a file in a remote server with:
> java TestConnection -s 91.231.###.## ###### ******** file.csv file.csv
> {{
> 220 Unauthorized access prohibited!
> Connected to 91.231.###.## on 21
> USER *******
> 331 Password required for ######.
> PASS *******
> 230 User logged in.
> SYST
> 215 Windows_NT
> Remote system is Windows_NT
> PASV
> 227 Entering Passive Mode (85,88,142,160,117,69).
> java.net.NoRouteToHostException: No route to host
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> at java.net.Socket.connect(Socket.java:529)
> at
> org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:762)
> at org.apache.commons.net.ftp.FTPClient._storeFile(FTPClient.java:565)
> at org.apache.commons.net.ftp.FTPClient.__storeFile(FTPClient.java:557)
> at org.apache.commons.net.ftp.FTPClient.storeFile(FTPClient.java:1795)
> at
> pt.knowledgeworks.emsa.mssim.scenario.TestConnection.main(TestConnection.java:285)
> }}
> Tcpdump in attachment. I'm no tcp expert to tell what's wrong with the dump.
> Ping, traceroute and other ftp clients work without problems. Standard
> command-line ftp managed to upload a file with no problems.
> Originally discovered via wagon-ftp (mvn deploy).
> Thanks in advance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
