wokaround for bad ftp server welcome message

Advertisement

markizs
Joined:
Posts:
2

wokaround for bad ftp server welcome message

i want to connect to odd ftp server, that has wrong welceme message format.

instead, of standards complying
220 (vsFTPd 1.1.3 bla bla)    

it returns
Running the FTPD
                Got past fork
                             changed group
                                          opened tty
                                                    /home/directory/bla/bla/log
/system/ftpd.logdoing signal
                            signal
                                  listening
                                           220 strange FTP server (Version 5.437
 Fri Dec 24 08:39:24 CST 2004) ready.    

which of course is completely non-standard and doesnt comply to ftp prodotocl.
however, i have actualy found one ftp client that manages to get 220 out of this mess, and after that everything works fine. This client is CuteFTP Pro. Problem is, that none of other ftp clients (windows default, windows commander, ultraedit built in, filezilla) i have tried, understands that, and i would really like to use open source client instead of expensive and bloated cuteftp.

So, question is - could it be possible to do some kind of workaround in winscp, using some script/configuration or whatever, to get through this odd welcome message?

Is there something i can do, apart of downloading source and building my own custom version of winscp client?

Reply with quote

Advertisement

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

Re: wokaround for bad ftp server welcome message

Please post a full log file showing the problem.

To generate log file, enable logging, log in to your server and do the operation and only the operation that causes the error. For posting extensive logs you may use pastebin or similar application. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you may email it to me. You will find my address (if you log in) in my forum profile. Please include link back to this topic in your email. Also note in this topic that you have emailed the log.
_________________
Martin Prikryl

Reply with quote

markizs
Joined:
Posts:
2

. 2010-02-23 18:28:40.453 WinSCP Version 4.2.6 (Build 721) (OS 5.1.2600 Service Pack 3)
. 2010-02-23 18:28:40.453 Login time: otrdiena, 2010. gada 23. februāris 18:28:40
. 2010-02-23 18:28:40.453 --------------------------------------------------------------------------
. 2010-02-23 18:28:40.453 Session name: user@server.org
. 2010-02-23 18:28:40.453 Host name: server.org (Port: 7021)
. 2010-02-23 18:28:40.453 User name: user (Password: No, Key file: No)
. 2010-02-23 18:28:40.453 Tunnel: No
. 2010-02-23 18:28:40.453 Transfer Protocol: FTP
. 2010-02-23 18:28:40.453 Ping type: C, Ping interval: 30 sec; Timeout: 15 sec
. 2010-02-23 18:28:40.453 Proxy: none
. 2010-02-23 18:28:40.453 FTP: FTPS: None; Passive: No [Force IP: No]
. 2010-02-23 18:28:40.453 Local directory: default, Remote directory: home, Update: No, Cache: Yes
. 2010-02-23 18:28:40.453 Cache directory changes: Yes, Permanent: Yes
. 2010-02-23 18:28:40.453 DST mode: 1
. 2010-02-23 18:28:40.453 --------------------------------------------------------------------------
. 2010-02-23 18:28:40.453 Password prompt (no password provided or last login attempt failed)
. 2010-02-23 18:28:44.796 Connecting to server.org:7021 ...
. 2010-02-23 18:28:45.093 Connected with server.org:7021. Waiting for welcome message...
. 2010-02-23 18:28:59.453 Timeout detected.
. 2010-02-23 18:28:59.453 Connection failed.
. 2010-02-23 18:28:59.453 Got reply 1004 to the command 1
* 2010-02-23 18:28:59.468 (ESshFatal) Connection failed.
* 2010-02-23 18:28:59.468 Timeout detected.
* 2010-02-23 18:28:59.468 Connection failed.
. 2010-02-23 18:29:04.468 Password prompt (no password provided or last login attempt failed)
* 2010-02-23 18:29:22.531 (ESshFatal) Authentication failed.    

and as i posted in previous post - problem is on the server side, it sends bad welcome message. what i want to achieve is some workaround so winscp would ignore that.

Reply with quote

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

OK thanks. I see. Well let's see if more people use such a server.
_________________
Martin Prikryl

Reply with quote

Kieran
Guest

I also use this kind of server

I have no control over what welcome message the server sends as i am not admin, winscp is able to verify the ssl connection but is unable to comply with the welcome message.

Reply with quote

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

Re: I also use this kind of server

Kieran wrote:

I have no control over what welcome message the server sends as i am not admin, winscp is able to verify the ssl connection but is unable to comply with the welcome message.
Please attach a complete session log file.
_________________
Martin Prikryl

Reply with quote

Advertisement

You can post new topics in this forum