localhost: timeout occured due to inactivity (wodSFTP / wodSFTP.NET / wodSFTPdll)
I trying to connect to my local Core FTP mini-sftp-server .
Using WinSCP it's no problem but using wodSFT.NET 3.4.1.103 gives me a
- timeout occured due to inactivity Exception.
- have also tried setting Timeout to 0
- have tried with and without proxy settings but localhost should not require a proxy (WinSCP does not rquire it too)
sftp = new SFTP();
sftp.LicenseKey = XXXXXXXX ;
sftp.Hostname = this.GetParamValue(Hostname);
sftp.Login= this.GetParamValue(Login);
sftp.Password = this.GetParamValue(Password);
sftp.Timeout = 30;
sftp.Port = 22;
sftp.Blocking = true;
sftp.Connect();
Please help ! Thanks.
Re: localhost: timeout occured due to inactivity
Hi,
What happens if you instead localhost use IP for value inside Hostname Property?
Does that help maybe?
Regards,
Drazen
Re: localhost: timeout occured due to inactivity
using 127.0.0.1 gives me invalid ip adress exception: Es wurde eine ungültige IP-Adresse angegeben . But cmd >ping 127.0.0.1 works fine.
This is the log from WinSCP: Notice the first error message Failed to connect but the connect finally succeeds!
. 2013-06-05 10:08:55.263 Looking up host localhost
. 2013-06-05 10:08:55.264 Connecting to ::1 port 22
. 2013-06-05 10:08:56.264 Failed to connect to ::1: Network error: Connection refused
. 2013-06-05 10:08:56.264 Connecting to ::1 port 22
. 2013-06-05 10:08:56.267 Server version: SSH-2.0-CoreFTP-0.3.2
. 2013-06-05 10:08:56.267 Using SSH protocol version 2
. 2013-06-05 10:08:56.267 We claim version: SSH-2.0-WinSCP_release_5.1.5
. 2013-06-05 10:08:56.267 Using Diffie-Hellman with standard group group14
. 2013-06-05 10:08:56.267 Doing Diffie-Hellman key exchange with hash SHA-1
. 2013-06-05 10:08:56.588 Verifying host key rsa2 xxxxxxx5 with fingerprint ssh-rsa 1024 31:bc:5b:5a:b8:5a:e2:aa:4b:95:3b:e1:52:f2:6f:c3
Re: localhost: timeout occured due to inactivity
Hi,
It works on my side without any problem. I'm using wodSFTP.NET and CoreFTP SFTP server.
Do you have maybe some firewall or something like that? Is there any chance you can disable it and try it again?
Regards,
Drazen