WS_FTP server 5.0 and SSL (General questions)

I'm trying to connect to a WS_FTP server, passive ftp, without a certificate - and it seems ok, besides the timeout on the data channel when I try to list the files...
I've tried with the WS_FTP pro client and it works ok - also transferring files.
There's a small difference in the way the session initiates - that is the WS_FTP client is using AUTH SSL, but the component is using AUTH TLS. Is this a problem ? At the same time the WS_FTP client is sending XAUT:

[2006.02.16 13:49:16.390] 220 xxxx.xxxx.xxX2 WS_FTP Server 5.0.2 (158563027)
[2006.02.16 13:49:16.390] AUTH SSL
[2006.02.16 13:49:18.343] 234 SSL enabled and waiting for negotiation
[2006.02.16 13:49:18.937] SSL Session Started.
[2006.02.16 13:49:18.953] Host type (1): WS_FTP Server
[2006.02.16 13:49:18.953] XAUT 2 B785<7>6:2718;>5<:<5<:>@<@5259A<;:687:A:
[2006.02.16 13:49:18.968] 230 user logged in
[2006.02.16 13:49:18.968] Host type (I): WS_FTP Server

Also using FTPSwithdata as protocol with the component.

Any hints or solution ? I've spent a lot of time dealing with this problem, and using the ws_ftp client is not an option
Help! My customer is getting grumpy on this matter...

My own logging:
IwodFtpNotify_StateChange
IwodFtpNotify_PreTranslateReply Code:220 ->220 xxxx.xxxx.xx X2 WS_FTP Server 5.0.2 (138378355)
IwodFtpNotify_FTPReply : (220) 220 xxxx.xxxx.xx X2 WS_FTP Server 5.0.2 (138378355)
IwodFtpNotify_StateChange
IwodFtpNotify_PreTranslateCommand
IwodFtpNotify_PreTranslateReply Code:234 ->234 SSL enabled and waiting for negotiation
IwodFtpNotify_FTPReply : AUTH TLS (234) 234 SSL enabled and waiting for negotiation
IwodFtpNotify_StateChange
IwodFtpNotify_PreTranslateCommand
IwodFtpNotify_PreTranslateReply Code:200 ->200 PBSZ=0
IwodFtpNotify_FTPReply : PBSZ 0 (200) 200 PBSZ=0
IwodFtpNotify_PreTranslateCommand
IwodFtpNotify_PreTranslateReply Code:200 ->200 PRIVATE data channel protection level set
IwodFtpNotify_FTPReply : PROT P (200) 200 PRIVATE data channel protection level set
IwodFtpNotify_StateChange
IwodFtpNotify_PreTranslateCommand
IwodFtpNotify_PreTranslateReply Code:331 ->331 Password required
IwodFtpNotify_FTPReply : USER xxxxxxxx (331) 331 Password required
IwodFtpNotify_PreTranslateCommand
IwodFtpNotify_PreTranslateReply Code:230 ->230 user logged in
IwodFtpNotify_FTPReply : PASS xxxxxxxxx (230) 230 user logged in
IwodFtpNotify_PreTranslateCommand
IwodFtpNotify_PreTranslateReply Code:211 ->211-Extensions supported
SIZE
MDTM
MLST size*;type*;perm*;create*;modify*;
LANG EN*
REST STREAM
TVFS
UTF8
AUTH SSL;TLS-P;
PBSZ
PROT C;P;
211 end
IwodFtpNotify_FTPReply : FEAT (211) 211-Extensions supported
SIZE
MDTM
MLST size*;type*;perm*;create*;modify*;
LANG EN*
REST STREAM
TVFS
UTF8
AUTH SSL;TLS-P;
PBSZ
PROT C;P;
211 end
IwodFtpNotify_PreTranslateCommand
IwodFtpNotify_PreTranslateReply Code:257 ->257 /users/xxxxxxx is current directory
IwodFtpNotify_FTPReply : PWD (257) 257 /users/xxxxxxx is current directory
IwodFtpNotify_PreTranslateCommand
IwodFtpNotify_PreTranslateReply Code:200 ->200 PBSZ=0
IwodFtpNotify_FTPReply : PBSZ 0 (200) 200 PBSZ=0
IwodFtpNotify_PreTranslateCommand
IwodFtpNotify_PreTranslateReply Code:200 ->200 PRIVATE data channel protection level set
IwodFtpNotify_FTPReply : PROT P (200) 200 PRIVATE data channel protection level set
IwodFtpNotify_StateChange
IwodFtpNotify_Connected
IwodFtpNotify_StateChange
IwodFtpNotify_StateChange
IwodFtpNotify_PreTranslateCommand
IwodFtpNotify_PreTranslateReply Code:200 ->200 Type set to ASCII.
IwodFtpNotify_FTPReply : TYPE A (200) 200 Type set to ASCII.
IwodFtpNotify_StateChange
IwodFtpNotify_PreTranslateCommand
IwodFtpNotify_PreTranslateReply Code:250 ->250 CWD successful
IwodFtpNotify_FTPReply : CWD /users/xxxxxxx/ (250) 250 CWD successful
IwodFtpNotify_StateChange
IwodFtpNotify_StateChange
IwodFtpNotify_PreTranslateCommand
IwodFtpNotify_PreTranslateReply Code:227 ->227 Entering Passive Mode (172,28,1,5,39,9).
IwodFtpNotify_FTPReply : PASV (227) 227 Entering Passive Mode (17

Ronny,

have you tried any other independent client to see if this is server of client issue, something that is not coming from WS_FTP group? Can you try FTP Voyager agains that server, if it works then problem is in wodFtpDLX. But if it doesn't work, then it could be server issue.

Kreso

Ronny,

have you tried any other independent client to see if this is server of client issue, something that is not coming from WS_FTP group? Can you try FTP Voyager agains that server, if it works then problem is in wodFtpDLX. But if it doesn't work, then it could be server issue.

Kreso

(my post 'died' so I'll make a short version...)

I've not tried any other packages, and it's not an option to install Voyager in the production environment. I'm working in a larger company with outsourced servers... so that's the negative side.
I'll also see what I can do from home...

I'll ask the owners of the ftp server we connect to - to see if there's any other packages used to connect.

Are there any technical differences in using AUTH TLS and AUTH SSL ?

Ronny.

Ronny,

well, yes and no. wodFtpDLX sends AUTH TLS. If it fails, then it sends AUTH SSL too - for older services. It also sends PROT command to negotiate data connection privacy. I see server replies correctly to all of those.

I can't know what's causing this until problem is isolated. We have to see if this is server or client issue, since I've seen problems with that kind of server before too, but other clients didn't work as well.

Kreso