Data Socket: SSL protocol error (wodFtpDLX / wodFtpDLX.NET)

A couple of clients are having problems where PutFile function is failing. We're getting a Data Socket: SSL protocol error (returned from GetLastErrorText method) and I can't find this in the enumerated errors list in the help file.

Can you explain to me what this means?

Jason,

does this happen with particular type of FTP(FTP+SSL) server, or different ones? This means that data socket could not negotiate SSL connection.

How can I duplicate that?

Jason,

does this happen with particular type of FTP(FTP+SSL) server, or different ones? This means that data socket could not negotiate SSL connection.

How can I duplicate that?

We are only using implicit ssl on port 990 right now and we only send to one server. As far as I know, this is the only client reporting this issue.

Our support team is contacting the server to see if something is wrong on their end.

Jason,

did you try with both Passive property settings (True/False)? Perhaps that will help.

Kreso

Jason,

did you try with both Passive property settings (True/False)? Perhaps that will help.

Kreso

There is no way for me to set this on the client without rebuilding and sending a new version to them. That's not an option right now.

Is there an internet setting or firewall setting that could be causing this?

Thanks

Jason,

only thing that comes to my mind is windows firewall, under network connection properties. This is only thing you can change.

Of course, if you have ZoneAlarm or something similar you may want to look there too.

Is the above mentioned problem solved, if so how?

I'm getting a similar error when I try to connect to an FTPS server on port 990 (FTPSimplicit).

The error I get is :

Run-time error '60000':
SSL Protocol Eror

I have no firewall on my system or on the router.

[code]
Private Sub Connect()

With m_FtpDLX
If .State <> Connected Then

.HostName = my.test.host
.Port = 990
.Protocol = ProtocolsEnum.FTPSimplicit
.Encryption = EncryptionsEnum.encAny
.Blocking = True
.Login = username
.Password = password
.Passive = True
.Connect
End If
End With

End Sub
[/code]

Any help is appreciated.

I think the reason why I was getting the error is because I had the protocol property set to FTPSwithdata.

After changing to FTPSimplicit the problem went away.

Hi Jason,

Nice, I did small test with your code on my Serv-U Server and FTPSimplicit protocol and I connect to my server with no problem.

Regards,
Drazen

I've tested every setting for protocol and encryption can't get the damn thing connected [:sad:]

.. I was not finished writing yet [:happy:]

I can connect to the very same server with the FileZilla client.
I use the following settings for the connection:
[code]
Host: some.host
Port: 990
Servertype: FTP over SSL (explicit encryption)
Logontype: Normal
Use passive mode: Yes
[/code]

Now, wat should be the equivalent settings I should use with wodFtpDLX?

Hi Jason,

In last post you mention that you change protocol to FTPSimplicit and didn't get error any more?
Is this correct or I miss something?

Regards,
Drazen

Hi Jason,

In last post you mention that you change protocol to FTPSimplicit and didn't get error any more?
Is this correct or I miss something?

Regards,
Drazen

Well, unless I'm thinking of a different error... Let me see if I can search my postings.

OK, I made a mistake.

This error was not fixed by changing the protocol property. I was thinking of this forum discussion: http://www.weonlydo.com/index.asp?forum=1&action=view&topic=1143221393.

Apparently, one of our clients is still getting the error, but if they try again immediately it goes through.

Hi Aram,

Please try something like this:

------------------------------------------------
Set dlx1 = New wodFtpDLXCom

dlx1.HostName = your_server_name
dlx1.Protocol = FTPSimplicit
dlx1.Passive = True
dlx1.Login = your_login
dlx1.Password = your_password
//dlx1.Blocking = True
dlx1.Connect
------------------------------------------------

You can also add Blocking= True just to be sure that you are connected to that server.

More help for Blocking Property find here:
http://www.weonlydo.com/FtpDLX/Help/wodFtpDLXLib~wodFtpDLX~Blocking.html

Hope I helped.

Regards,
Drazen

Hi Aram,

Please try something like this:

------------------------------------------------
Set dlx1 = New wodFtpDLXCom

dlx1.HostName = your_server_name
dlx1.Protocol = FTPSimplicit
dlx1.Passive = True
dlx1.Login = your_login
dlx1.Password = your_password
//dlx1.Blocking = True
dlx1.Connect
------------------------------------------------

You can also add Blocking= True just to be sure that you are connected to that server.

More help for Blocking Property find here:
http://www.weonlydo.com/FtpDLX/Help/wodFtpDLXLib~wodFtpDLX~Blocking.html

Hope I helped.

Regards,
Drazen

See my first posting with the sourcecode I'm using. Is more or less the same. I use the blocking mode.

Hi Aram,

It would be best if we can somehow connect to your server and try to duplicate your problem, is this possible?
Please send us your information to techsupport@weonlydo.com if you can.

You can also try to connect to that server with our sample that comes with our component.
Please try with 1.Simple under FtpDLXSamplesVBComponent1. Simple folder.

Hope I helped.

Regards,
Drazen

Found the problem:

You should first set the protocol and then the port. If you do it the way around, the protocol setting will also adjust the port setting to an default. In my case I needed to communicate on port 990, but the default port for the protocol FTPSnodata seems to be 21.

Maybe a note in the manual about this behaviour could prevent this kind of troubles in the future.

Thanks for all the help.

Aram,

Yes, I agree with you. I presume that Drazen overlooked that.
I will add this immediately in Knowledgebase.

Glad that you resolved your problem.

Regards,
Alan