Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

WinSCP needs to know current directory, so it can interpret relative paths correctly.
chindall

Thanks for the very quick response much appreciated. What I am learning is these "clients" love to make their own standards. With that being said, why do CuteFTP and WSFTP work successfully? I am under the asumption it is because they don't follow the standards.

Would it be possible to tell WinSCP to not send a PWD when connecting? I am scripting all this. All I need to do is connect, upload some files and disconnect.

Again thanks for your response. I am in hopes I can use WinSCP for my company's needs. They purchased CuteFTP Pro, however I much prefer WinSCP.

Craig Hindall
martin

Re: Invalid response to PWD command '<virtual directory>

According to RFC 959 (section 5.4), the only valid 2xx class response code for PWD command is 257.
chindall

Invalid response to PWD command '<virtual directory>

I am trying to implement WinSCP into my company's daily routines. We have a client that uses a secure FTP. I am unable to sucsesfully make and keep the connection to transfer files.

Here is are the logs for WinSCP and CuteFTP Pro. Both CuteFTP and WS FTP Pro are able to stay connected sucsessfully.

WinSCP log
. 2009-10-06 15:02:05.752 Using FTP protocol.
. 2009-10-06 15:02:05.752 Doing startup conversation with host.
> 2009-10-06 15:02:05.752 PWD
< 2009-10-06 15:02:05.783 230 <virtual directory>
. 2009-10-06 15:02:05.783 Got reply 1 to the command 16
. 2009-10-06 15:02:05.783 Getting current directory name.
> 2009-10-06 15:02:05.783 PWD
< 2009-10-06 15:02:05.815 230 <virtual directory>
. 2009-10-06 15:02:05.815 Got reply 1 to the command 16
* 2009-10-06 15:02:05.815 (ECommand) Error getting name of current remote directory.
* 2009-10-06 15:02:05.815 Invalid response to PWD command '<virtual directory>
* 2009-10-06 15:02:05.815 '.
. 2009-10-06 15:02:05.815 Attempt to close connection due to fatal exception:
* 2009-10-06 15:02:05.815 (Exception) Invalid response to PWD command '<virtual directory>
 
* 2009-10-06 15:02:05.815 '.
. 2009-10-06 15:02:05.815 Got reply 1004 to the command 16
. 2009-10-06 15:02:05.815 Disconnected from server

CuteFTP log:
      [10/6/2009 2:56:35 PM] 230 OK.  Logged in

STATUS:>     [10/6/2009 2:56:35 PM] Login successful.
COMMAND:>   [10/6/2009 2:56:35 PM] PWD
      [10/6/2009 2:56:35 PM] 230 <virtual directory>
STATUS:>     [10/6/2009 2:56:35 PM] Home directory: <virtual directory>
STATUS:>     [10/6/2009 2:56:35 PM] This site doesn't support the 'features' command.
STATUS:>     [10/6/2009 2:56:35 PM] This site cannot resume broken downloads.
COMMAND:>   [10/6/2009 2:56:35 PM] PBSZ 0
      [10/6/2009 2:56:35 PM] 200 PBSZ Command OK. Protection buffer size set to 0.
COMMAND:>   [10/6/2009 2:56:35 PM] PROT P
      [10/6/2009 2:56:36 PM] 200 PROT Command OK. Using Private data connection.
COMMAND:>   [10/6/2009 2:56:36 PM] PASV
      [10/6/2009 2:56:36 PM] 227 Passive mode OK (204,154,185,200,11,220)
COMMAND:>   [10/6/2009 2:56:36 PM] LIST
STATUS:>     [10/6/2009 2:56:36 PM] Connecting FTP data socket... 204.154.185.200:3036...
      [10/6/2009 2:56:36 PM] 150-Accepted data connection from 207.250.107.10
      150 Options: -l
STATUS:>     [10/6/2009 2:56:36 PM] Connected. Exchanging encryption keys...
      Session Cipher: None
STATUS:>     [10/6/2009 2:56:36 PM] SSL Connect time: 79 ms.
STATUS:>     [10/6/2009 2:56:36 PM] SSL encrypted session established.
      [10/6/2009 2:56:36 PM] 226 1 matches total
STATUS:>     [10/6/2009 2:56:36 PM] Directory listing completed.

Any help would be greatly appreciated.