edtFTPnet/PRO - Secure FTP component for .NET | Free Trial | Pricing

How to diagnose problems

edtFTPnet/PRO has a rich API and provides complex capabilities. There are a wide variety of FTP, FTPS and SFTP servers in existence, which may or may not implement the relevant standards.

If difficulties are experienced in connecting to a server or performing operations, a number of steps can be taken to try to resolve the problem.

  1. Ensure that you can connect using FileZilla using the same credentials. If you cannot connect with FileZilla, it is likely that other clients (such as this one) will also experience difficulties connecting. Make sure you select the correct protocol.
  2. For SFTP, alternatively (or also) use a command-line ssh client to connect to the server using the authentication method of your choice, and ensure that this works. ssh -vvv can be used to provide helpful debugging information.
  3. If you can connect using FileZilla, try using the appropriate Example Viewer example (with suitable settings) provided with the distribution.
  4. Generate a log file exhibiting the error with the level set to LogLevel.All. This may provide you (and us) with a clue to the problem.
  5. If possible, obtain the server log file to see if it contains any clues to the problem.
  6. Search the question & answer board to see if the problem has been reported and a resolution posted. The forum is fully searchable and contains advice and answers to many issues that developers have faced when using this library. Also check the Frequently Asked Questions.
  7. Consult the product's revision history to see if your problem has been resolved in a later version of the software. If your support agreement is current, download the latest version (or request it from support, even if your problem is not listed. If you are unable to resolve the problem and you have a current support agreement, you may need to contact support. We will do our best to resolve the problem, including issuing patches if necessary.

When emailing support with a problem, always include your purchase reference (or note that you are using the trial), a stack trace (if applicable) and a relevant section of the log file that illustrates the problem. Include as much information as possible. It will save us emailing you to ask for it.