Problem from FileZilla

HuaMin Chen
HuaMin Chen used Ask the Experts™
on
Hi,
How to identify the reason of problem below?
Status:	Connecting to 160.96.17.69...
Response:	fzSftp started, protocol_version=8
Command:	open "pzim_ftpuser1@160.96.17.69" 22
Error:	Connection timed out after 20 seconds of inactivity
Error:	Could not connect to server
Status:	Waiting to retry...
Status:	Connecting to 160.96.17.69...
Response:	fzSftp started, protocol_version=8
Command:	open "pzim_ftpuser1@160.96.17.69" 22
Error:	Connection timed out after 20 seconds of inactivity
Error:	Could not connect to server

Open in new window

Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Jose Gabriel Ortega CastroEE Rookie/Solution Guide/Topic Advisor and CEO Faru Bonon IT
Awarded 2018
Distinguished Expert 2018

Commented:
Be sure that you have all the ports (passive mode) open in you internal firewall (windows ) and you're external firewall
There are more ideas in the comments.
https://www.youtube.com/watch?v=gBuan5sNvNI
HuaMin ChenProblem resolver

Author

Commented:
Which ports to adjust?
Jose Gabriel Ortega CastroEE Rookie/Solution Guide/Topic Advisor and CEO Faru Bonon IT
Awarded 2018
Distinguished Expert 2018
Commented:
Please read passive mode (https://wiki.filezilla-project.org/Network_Configuration)
you put the port ranges in there.

Did you try the solution in the video?
CompTIA Network+

Prepare for the CompTIA Network+ exam by learning how to troubleshoot, configure, and manage both wired and wireless networks.

Dave BaldwinFixer of Problems
Most Valuable Expert 2014

Commented:
You are trying to make an SFTP connection to that server on port 22 and it appears likely that the server does not support SFTP.  Try plain FTP and see if that works.
Commented:
The question is of  course, where do you have full control. Are you the client only, or also the server. If you are NOT in the control of the server, the other side has to help you out. As right now, there's just no fixing it without the other side. The server side should give you the correct information (server / port / user / pass).
Passive ports is totally another case, as there's no INITIAL connection being made, so passive/active has no meaning yet.
HuaMin ChenProblem resolver

Author

Commented:
I've got that I should also ensure telnet is fine, to the connection. Is this true?
Commented:
It's still not clear to me if you are PURELY the client, testing a server NOT under your control, or that you ARE the server, but just testing from an external connection.

If you are purely the CLIENT ONLY, the OTHER SIDE has either provided you with wrong info (port 22 is not the correct port), or provided you with the correct info, but you input it wrongly (ftp port ex. 21). If everything IS correct, then the other wise didn't configure the firewall/NAT correctly, or they did it correctly, but for safety reasons, they block unknown IP's (in which case, you should relay your IP to them for them to put on the whitelist).

If you ARE the server, your NAT rules are not setup yet. Make sure your server is listening on port 22, and make sure the router NAT reflects it as well.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial