One reason it appears is when the IP address is restricted on the SSH Server end of the connection.
The following could be posted under the SSH Server forum as well, but during the connecting event of the SSH Server COM component, if you set the action = deny, the SFTP.NET client will receive that error in response.
that could be one of the reasons. But I think error says it all - connection was just closed by remote peer for no obvious reason. There can be millions of reasons, I doubt we can enumerate all of them in the helpfile.
We have recently completed a large 1200+ location project where reliable Telnet and SSH connectivity was required. wodSSH worked flawlessly and allowed our staff to complete our project ontime and within budget.
James Sievers
Harbor Technologies
Congratulations on an excellent product and first rate support!
Sander Pool
Rhapsody Networks
You have been great as far as offering support is concerned and has been extremely responsive to both support requests and suggestions for product enhancements.
David Keenan
Serengeti Systems Incorporated
The wodCrypt product is great and we appreciate your effort to add support for UNIX Crypt.
William Ruf
Siemens Information and Communication Networks
Just thought you'd like to know that my gateway app with your SMTP Server component held the line against a DDOS attack today...
Chris Langsenkamp
Clever Technologies
I would highly recommend this to anyone who needs a good quality SFTP solution.
Ian D. Mead, author of UltraEdit-32
IDM Computer Solutions
...with WOD's excellent support I was able to bypass Winsock and focus on the task at hand...
Sander Pool
Rhapsody Networks
I really like these products - they are consistently first rate!
David Witten
WWR Development, Inc.
Thank you for the great customer service ... I am really impressed with the wodSSH ActiveX control.
Andrew Ross
Kiwi Enterprises
Count us as a satisfied WeOnlyDo customer. We appreciate your terrific support to get the secure Telnet working properly.