martin wrote:
Well that's normal, isn't it? TCP connect remain in TIME_WAIT state few minutes after it is closed, to keep the local port reserved to avoid mixing stray data.
Thank you for your reply.
I consulted with the rental server contractor and investigated the cause succeedingly.
1. Reappearance Existence in Another PC
With another PC (notebook PC of Windows7 32bit), I tried on WinSCP (Ver5.5.4).
As a result, fault occurred.
For this reason, I think that it is not a problem peculiar to client PC.
2. Reappearance Existence in Another FTP Software
With PC (desktop PC of Windows7 Ultimate 64bit) currently used usually, I tried on FFFTP (Ver1.98g2) again.
As a result, fault did not occur.
With PC (desktop PC of Windows7 Ultimate 64bit) currently used usually, I tried on FileZilla (Ver3.8.1).
As a result, fault occurred.
For this reason, since it generates also in Filezilla although it does not generate in FFFTP, it is not likely to be a soft bug peculiar to WinSCP, either.
3. About TIME_WAIT
In addition, when it tried on FFFTP, it checked by "netstat -n", but so many TIME_WAIT status remained that it could not display on a command prompt.
As a result, it is not the cause of this fault that the thing of TIME_WAIT status remains.
About this, I think that it is right what you were said.
I am sorry.
These results were reported to the rental server contractor.
I will report immediately after getting a reply.
Thank you for your consideration.