An existing connection was forcibly closed by the remote hos (wodFtpDLX / wodFtpDLX.NET)
Hi Tau.
Local debugging will probably not say much, since connection just drops. From client's perspective, if all is running and suddenly connection is lost, I don't think we can manage to determine the reason.
In any case, we can create special version that will dump to local file current state of the component, so we can see on which packets it will drop.
Would you be so kind to send email to techsupport - at - weonlydo.com so we can attach debugging version there?
Kind regards,
Jasmine.
Complete thread:
- An existing connection was forcibly closed by the remote hos - Tau, 2015-08-28, 15:47
- An existing connection was forcibly closed by the remote hos - Jasmine, 2015-08-29, 15:42
- An existing connection was forcibly closed by the remote hos - Tau, 2015-08-31, 15:56
- An existing connection was forcibly closed by the remote hos - Jasmine, 2015-08-31, 16:07
- An existing connection was forcibly closed by the remote hos - Tau, 2015-09-01, 23:14
- An existing connection was forcibly closed by the remote hos - Jasmine, 2015-09-02, 09:11
- An existing connection was forcibly closed by the remote hos - Tau, 2015-09-07, 16:43
- An existing connection was forcibly closed by the remote hos - Jasmine, 2015-09-02, 09:11
- An existing connection was forcibly closed by the remote hos - Tau, 2015-09-01, 23:14
- An existing connection was forcibly closed by the remote hos - Jasmine, 2015-08-31, 16:07
- An existing connection was forcibly closed by the remote hos - Tau, 2015-08-31, 15:56
- An existing connection was forcibly closed by the remote hos - Jasmine, 2015-08-29, 15:42