Opened 14 years ago
Closed 8 years ago
#7376 closed Other (outdated)
425 Can't open data connection
Reported by: | Touseef K | Owned by: | |
---|---|---|---|
Priority: | high | Component: | FileZilla Server |
Keywords: | can't open data connection | Cc: | |
Component version: | Operating system type: | Windows | |
Operating system version: | XP SP3 |
Description
I am Touseef from HP trying to replicate customer's issue. Customer uses external ftp site hosted on Filezilla Server 0.9.34 beta. They use our scanner to send to ftp but it fails saying "unable to write file at this location, please use someother location". It works fine from Windows and other scanners sending to same location. I have been able to replicate the problem sending to the customer's ftp site. I captured network trace on both working and non working device. The difference i found was the non working device uses EPRT command to open connection for transfering data and the ftp server responds saying "425 Can't open data connection" where as the working one uses PORT command and it works fine there. I downloaded the same ftp server application and tried replicating, but was able to send fine from the non working device. Now i am wondering what setting on the ftp server can we configure to make ftp server accept connections on EPRT command. Your advice will be really helpful. I have attached screenshots of the network trace for your reference.
Attachments (2)
Change History (5)
by , 14 years ago
Attachment: | nonworkingdevice.JPG added |
---|
comment:2 by , 13 years ago
Component: | FileZilla Client → FileZilla Server |
---|---|
Keywords: | can't open data connection added; 505 LOL removed |
Operating system type: | BSD → Windows |
Operating system version: | 505 LOL → XP SP3 |
Priority: | critical → high |
Resolution: | fixed |
Status: | closed → reopened |
Summary: | 505 LOL → 425 Can't open data connection |
Type: | Bug report → Other |
comment:3 by , 8 years ago
Triage suggestion
It is unlikely that it will be possible to troubleshoot and confirm this bug is fixed so long after it was opened six years ago.
I suggest closing this bug report.
comment:4 by , 8 years ago
Resolution: | None → outdated |
---|---|
Status: | new → closed |
Non Working device