#3600 closed Bug report (fixed)
Failed to parse returned path
Reported by: | rwamz13 | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | FileZilla Client |
Keywords: | Cc: | rwamz13, Tim Kosse | |
Component version: | Operating system type: | ||
Operating system version: |
Description
FTP client fails when connecting to a FANUC robot. Before, I was using Filezilla 3.0.2.1, and everything was working great. I upgraded to 3.0.11.1 today and now it doesn't work. FANUC documentation claims support for 2.2.31.
FANUC uses a default directory: "md:\". So when you log in you are not at "\", but at "md:\". Maybe this is causing the error?
Thanks
Filezilla 3.0.11.1.
Windows XP Professional Version 2002 Service Pack 2.
14:22:25 Trace: ControlSocket.cpp(1056): CRealControlSocket::ContinueConnect(0p22ecf4) m_pEngine=0p11cf170 caller=0p122cae0
14:22:25 Status: Connecting to 172.22.194.222:21...
14:22:25 Status: Connection established, waiting for welcome message...
14:22:25 Trace: CFtpControlSocket::OnReceive()
14:22:25 Response: 220 R-J3 FTP server ready. [SpotTool+ V7.5011]
14:22:25 Trace: CFtpControlSocket::SendNextCommand()
14:22:25 Command: USER anonymous
14:22:25 Trace: CFtpControlSocket::OnReceive()
14:22:25 Response: 230 User logged in [NORM].
14:22:25 Trace: CFtpControlSocket::SendNextCommand()
14:22:25 Command: SYST
14:22:25 Trace: CFtpControlSocket::OnReceive()
14:22:25 Response: 215 UNKNOWN [SpotTool+ V7.5011].
14:22:25 Trace: CFtpControlSocket::SendNextCommand()
14:22:25 Command: FEAT
14:22:25 Trace: CFtpControlSocket::OnReceive()
14:22:25 Response: 500 Command not understood.
14:22:25 Status: Connected
14:22:25 Trace: CFtpControlSocket::ResetOperation(0)
14:22:25 Trace: CControlSocket::ResetOperation(0)
14:22:25 Status: Retrieving directory listing...
14:22:25 Trace: CFtpControlSocket::SendNextCommand()
14:22:25 Trace: CFtpControlSocket::ChangeDirSend()
14:22:25 Command: PWD
14:22:25 Trace: CFtpControlSocket::OnReceive()
14:22:25 Response: 257 "md:\" is current directory.
14:22:25 Trace: ControlSocket.cpp(354): Failed to parse returned path. caller=0p122cae0
14:22:25 Trace: CFtpControlSocket::ResetOperation(2)
14:22:25 Trace: CControlSocket::ResetOperation(2)
14:22:25 Trace: CFtpControlSocket::ParseSubcommandResult(2)
14:22:25 Trace: CFtpControlSocket::ListSubcommandResult()
14:22:25 Trace: CFtpControlSocket::ResetOperation(2)
14:22:25 Trace: CControlSocket::ResetOperation(2)
14:22:25 Error: Failed to retrieve directory listing
Attachments (1)
Change History (5)
by , 16 years ago
Attachment: | filezilla3_Err.cap added |
---|
comment:1 by , 16 years ago
Highly exotic server.
You might want to upgrade to a server supporting the well-defined, 100% sane TVFS extension.
I might be able to add support for your server if you can give me a BNF grammar with assorted semantics.
comment:2 by , 16 years ago
This is an FTP server embedded in a robot. There is no PC software you can install. FANUC provides all the software, so upgrading the server doesn't seem to be a possibility.
Looking at TVFS, it looks like there are three differences. First is that the robot server separates directory names with the "\" character instead of an "/". Also, a "\" is appended to all directory paths that end in a directory name. Lastly, the unnamed root directory "/" (or "\") is not prepended to the fully qualified pathname.
So examples of pathnames would be:
TVFS: "/md:"
Robot: "md:\"
TVFS: "/mc:/temp/bacon"
Robot: "mc:\temp\bacon\"
All this appears only related to PWD. Doing a CWD and RETR using TVFS-style pathnames, for example, seems to work just fine.
I could whip out a BNF for you if you still need it, but it might be easier to just modify the existing TVFS BNF with these three rule changes. Let me know.
Thanks
comment:3 by , 16 years ago
Component: | Other → FileZilla Client |
---|
comment:4 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Will be fixed in the next version. You will have to manually select DOS servertype in the site manager.
Ethenet capture of the error