Invalid response to PWD command - Features

Advertisement

SeasonOfBytes
Joined:
Posts:
4

Invalid response to PWD command - Features

I hope you can help. I get the Invalid response to PWD command error while simply logging in and visually before any files or folders are listed.

I got this error while using the previous GUI version I had running. Today I am getting this using the latest GUI version downloaded today as well as CSharp code via the DLL.

Happens all the time in C# code via DLL.
Happens intermittently in your GUI.

FTP port 21
Passive and Active

I've attached WinSCP_Error_20140505_1517.zip which holds two log files and two screen caps. One log file created by Debug logging via your GUI and one created via CSharp app setting session logging.

Although I have masked private info in the log files, the attachment here is flagged as Private File.

Win7 Ultimate SP1, 2GB RAM
Visual Studio 2010
  • WinSCP_Error_20140505_1517.zip (57.01 KB, Private file)
Description: compressed file (ZIP) with XML log file created with your GUI but renamed to TXT, a log file created with my CSharp app, screen caps of GUI and DLL versions

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
27,252
Location:
Prague, Czechia

Re: Invalid response to PWD command - Features

Thanks for your report.
I have sent you an email with a debug version of WinSCP to address you have used to register on this forum.

Reply with quote

SeasonOfBytes
Joined:
Posts:
4

Re: Invalid response to PWD command - Features

martin wrote:

Thanks for your report.
I have sent you an email with a debug version of WinSCP to address you have used to register on this forum.

Thank you. I got the debug version and ran it. I was able to reproduce the problem. However, I examined the trace log file and found details about other sites in my configured session are recorded. I cannot release the trace log without exposing my clients and their FTP/SFTP sites.

I am looking for a way to give you the info you need to help me but without exposing the other sites.

Is there a command-line option I can use for the debug version that will only log details of the subject FTP site?

Or may I manually edit out the details of the other FTP sites from the trace log? Is that acceptable?

Let me know. Thanks for your help.

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
27,252
Location:
Prague, Czechia

Re: Invalid response to PWD command - Features

SeasonOfBytes wrote:

Or may I manually edit out the details of the other FTP sites from the trace log? Is that acceptable?
Delete whatever you do not want to share.
_________________
Martin Prikryl

Reply with quote

SeasonOfBytes
Joined:
Posts:
4

Re: Invalid response to PWD command - Features

martin wrote:

SeasonOfBytes wrote:

Or may I manually edit out the details of the other FTP sites from the trace log? Is that acceptable?
Delete whatever you do not want to share.

Just emailed to you the log file compressed as a 7Z.

Thanks for your help.

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
27,252
Location:
Prague, Czechia

Re: Invalid response to PWD command - Features

The problem is that your server violates FTP specification by sending two 230 responses to PASS command. That confused WinSCP, which from that moment matched its request with wrong responses, until this ultimately failed when trying to parse response to FEAT command as a response to PWD command. While WinSCP could theoretically be more tolerant to such a wrong behavior, a root cause is with your server.

> 2014-05-05 15:38:18.010 PASS *************
< 2014-05-05 15:38:20.452 230 User {ftp_username_masked} logged in
< 2014-05-05 15:38:20.452 230 Yu con xie n2015-02-28 23:29:42,{ftp_username_masked}    

Reply with quote

SeasonOfBytes
Joined:
Posts:
4

Re: Invalid response to PWD command - Features

martin wrote:

The problem is that your server violates FTP specification by sending two 230 responses to PASS command. That confused WinSCP, which from that moment matched its request with wrong responses, until this ultimately failed when trying to parse response to FEAT command as a response to PWD command. While WinSCP could theoretically be more tolerant to such a wrong behavior, a root cause is with your server.

> 2014-05-05 15:38:18.010 PASS *************
< 2014-05-05 15:38:20.452 230 User {ftp_username_masked} logged in
< 2014-05-05 15:38:20.452 230 Yu con xie n2015-02-28 23:29:42,{ftp_username_masked}    

For clarification, the server is not mine. The server belongs to a vendor.

I will notify the vendor of your observations about their server.

Thanks again.

Reply with quote

Advertisement

You can post new topics in this forum