Transfer channel can't be opened

Advertisement

Guest

Transfer channel can't be opened

Seems this error below is fairly common and usually caused by firewall or NAT. I'm not experienced in resolving those issues and hope to get some pointers on what I should be looking for. I have attached log file with identifiable info removed, Thanks for any help.

It was working fine, as I had just pulled files down and it stopped working during transfer after many files had already moved. I have tried reconnecting many times and get the same error every time now.
Transfer channel can't be opened. Reason: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Could not retrieve directory listing
Data channel timed out.

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
41,541
Location:
Prague, Czechia

Re: Transfer channel can't be opened

Indeed that error is mostly caused by firewalls:
Transfer channel can’t be opened

But if it started occurring after some successful transfers, it looks implausible. Unless someone changed some firewall settings meanwhile. Can anyone transfer files to/from that server from any other machine?

Reply with quote

diehnel
Guest

I have this problem but found out why

I get the same message with DreamWeaver and WinSCP on my website server. The problem is an issue with the host security certificate. When I use FileZilla to connect I get a return message about the certificate and have to respond to continue. DreamWeaver and WinSCP does NOT return that message, they just time out because the message has not been answered.

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
41,541
Location:
Prague, Czechia

Re: I have this problem but found out why

@diehnel: Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Reply with quote

Advertisement

You can post new topics in this forum