TimeOut problem

Discussion of open issues, suggestions and bugs regarding network security and data protection solution - SecureBridge
Post Reply
jscoulter
Posts: 14
Joined: Mon 09 Feb 2009 12:19

TimeOut problem

Post by jscoulter » Mon 09 Feb 2009 12:23

Hi. I am using the latest trial download fro Delphi (7) and have it a problem I am not sure "IS" a problem or is me.
Take the following code:
ScSSHClient1.User:=txtUsername.text;
ScSSHClient1.Password:=txtPassword.text;
ScSSHClient1.HostName:=txtIPAddress.text;
ScSSHClient1.timeout:=1;
screen.cursor:=crHourglass;
try
ScSSHClient1.Connect;
except
Messagedlg('Unable to connect to server', mtWarning,[mbOk],0);
end;
screen.cursor:=crDefault;

You will notice I have set the timeout to 1 which according to the help file is meant to be 1 second, however, it takes 35 seconds to time out !

Is there something I am doing wrong or is this something to do wiht it being a trial version.

Thanks, Jeremy

Dimon
Devart Team
Posts: 2910
Joined: Mon 05 Mar 2007 16:32

Post by Dimon » Mon 09 Feb 2009 14:50

Please specify what error do you get after timeout.

jscoulter
Posts: 14
Joined: Mon 09 Feb 2009 12:19

Post by jscoulter » Mon 09 Feb 2009 18:21

the error is:

'Socket error on connection. WSAGetLastError return 10060($247C)'

10060 is a connection error if I am correct which would be correct as the server is no even running, but does not explain why 1 econd becoms 35 ;-)

Jeremy

Dimon
Devart Team
Posts: 2910
Joined: Mon 05 Mar 2007 16:32

Post by Dimon » Tue 10 Feb 2009 07:22

Thank you for the information. We will investigate the possibility of changing this behaviour in the near future. As soon as we solve this problem we will let you know.

jscoulter
Posts: 14
Joined: Mon 09 Feb 2009 12:19

Post by jscoulter » Tue 10 Feb 2009 08:58

um....change the behaviour?? dont you mean fix it :-)
do you have a time frame for this to be sorted? We are ready to order, but would like this fixed first if possible.

Dimon
Devart Team
Posts: 2910
Joined: Mon 05 Mar 2007 16:32

Post by Dimon » Wed 18 Feb 2009 14:20

We are fixing this problem. This fix will be included in the next SecureBridge build.

Post Reply