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.
Your support is fantastic.
Douglas Michael Panchyshyn
The Net Software Group
You did a great job on wodSSH and wodSSHServer! I got a lot for very little money. Thanks!
Dirk Bulinckx
bvba Woodstone
This has been, by far, the best experience I have ever had dealing with a support entity in my long career in the technical arena
Frank Kloskowski
GlobalCare Inc.
...with WOD's excellent support I was able to bypass Winsock and focus on the task at hand...
Sander Pool
Rhapsody Networks
...what I really like is that wodSSH and wodSFTP components work excellently and are constantly being improved...
Steven Jones
SABIEN project
Count us as a satisfied WeOnlyDo customer. We appreciate your terrific support to get the secure Telnet working properly.
Don Fitzpatrick
InterNetworx Systems
Your customer service was excellent, and I will look at your products in the future for precisely that reason.
Charles Taylor
InterWeave, Inc.
Thank you very much for the rapid responses. I was a little nervous about dealing with a company that is on a different continent from me. You have proven my concerns to be unfounded.
Robert Pacheco
Surebridge, Inc.
Your professionalism is reflected into your email, your product and your web site. I am confident that these will make the difference.
Sylvain Paquette
R&D Analyst at InfoPharm Inc.
Your component works really great. With minor effort I have been able to convert my delphi application...