Ticket #3600 (closed Bug report: fixed)

Opened 6 years ago

Last modified 8 months ago

Failed to parse returned path

Reported by: rwamz13 Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc: rwamz13, codesquid
Operating system type: Operating system version:

Description (last modified by codesquid) (diff)

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

filezilla3_Err.cap Download (1.4 KB) - added by rwamz13 6 years ago.
Ethenet capture of the error

Change History

Changed 6 years ago by rwamz13

Ethenet capture of the error

Changed 6 years ago by codesquid

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.

Changed 6 years ago by rwamz13

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

Changed 6 years ago by codesquid

  • component changed from Other to FileZilla Client
  • description modified (diff)

Changed 6 years ago by codesquid

  • status changed from new to closed
  • resolution set to fixed

Will be fixed in the next version. You will have to manually select DOS servertype in the site manager.

Note: See TracTickets for help on using tickets.