[FIXED] SFTP help needed

[MarkFilipak]

Win10 1803
TC 9.51 64 bit (2020-03-25)

Hello, All,

I need expert help.

I downloaded (http://www.totalcommander.ch/win/fs/sftpplug.zip) and installed the SFTP plug-in today. I can't get it to work when I attempt to connect to my friend's computer. SFTP to my friend's computer does work in a Linux VM via Filezilla. I'm now trying to get it to work in the Windows Host via TC.

I punched a hole through Windows's outbound firewall that has only 1 limit: the IP must be my friend's IP.

I used F7 to create a new connection named "myfriend', with the following settings:
Connect to: xxx.xxx.xxx.xxx:22 //comment: this is my friend's IP
User name: mark
Password: *************** //comment: this password is known to work
[x] Use SCP for data transfers (faster!)

I'm awfully ignorant. What am I doing wrong?

Help will be rewarded in Heaven,
Mark.

[Stefan2]

Are you sure that 22 is the correct port for the current configuration of your friend? What does Filezilla use?
And me think it is not need at all to declare the port there, at the end it is a dedicated Tool which already know about the port???or it just try them all?not sure?

Just some ideas to try out...




 

[Dalai]

What exactly happens when you try to connect?

2Stefan2
Port 22 is the default port for SSH which SFTP is based on, so it's probably correct (assuming the SFTP server listens on this port).

Regards
Dalai

[Stefan2]

Thx.

Default yes, but not mandatory. That's why I asked, as it is one possibility of failure.





 

[gdpr deleted 6]

Have you tried running Filezilla on the Windows host with the exact same Filezilla settings you used in the Linux VM?
Doing so would narrow the problem area down to either an issue is with your Windows box/network environment (in case SFTP through Filezilla on Windows is not working either), or an issue specifically related to TC's SFTP plug-in [*] (in case SFTP through Filezilla on Windows works).



[*] An issue related to the SFTP plug-in does not necessarily have to originate from TC or the plug-in itself. While not that likely, it could be possible that there is another active Firewall rule you missed to spot which prevents the TC process from establishing a connection...

[MarkFilipak]

You folks are very kind.

I can ping myfriend in both Linux & Windows but Filezilla in Windows fails: "Connection refused". Does that mean that Filezilla couldn't get through the firewall or that myfriend's server refused the connection? I know you folks can't answer that question.

I think the logical thing to do is to try to connect to an SFTP test server that's known good and always connects. Is there such a test server?

I include the info below as supplement.

I installed Filezilla in Windows -- I didn't think of that [Duh!] -- punched a new firewall outbound hole for it.

Status: Connecting to xxx.xxx.xxx.xxx...
Response: fzSftp started, protocol_version=9
Command: open "mark@xxx.xxx.xxx.xxx" 22
Error: FATAL ERROR: Network error: Connection refused
Error: Could not connect to server

So, the only logical conclusion is that this is not a TC problem.

[Dalai]

"Connection refused" usually means the target system is there and reachable, but the requested port it not opened. This is especially true when this error occurs with no delay after trying to connect. If there is a delay of several seconds, packets are most likely dropped on the way instead of being rejected.

I suggest to make doubly sure the IP address or name of the target system is correct (and the name resolves to the IP address you intend to connect to) as well as the port 22.

Hope this helps you on the quest of finding the culprit.

Regards
Dalai

[MarkFilipak]

Thanks folks. False alarm. It's not TC's problem.

My friend did some diddling of something that worked, and broke it without telling me. He changed from bridged to NAT (which should be okay) and added :22 (i.e. port number, which is not okay as the OS port maps). It's working now.

Thanks for your views. Be Safe and Happy.