Can't connect to latest Progressive WS FTP Server

Need help with FileZilla Client? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Post Reply
Message
Author
jimbo2
504 Command not implemented
Posts: 6
Joined: 2015-01-15 14:52
First name: jim
Last name: bushee

Can't connect to latest Progressive WS FTP Server

#1 Post by jimbo2 » 2024-01-12 18:37

I upgraded my FTP server. My old was was using WS FTP Server using 7.6 on Windows Server 2008. My new one is using WS FTP Server 8.8 on Windows Server 2019. For the most part I have it all set up the same. I can connect to the old one with Filezilla using port 21 or 22. But on my new one it times out due to inactivity for port 21.Port 22 connects right away. It sees the server and starts to connect but, errors out. When I look at the log on the server it tells me unknown security mechanism with Filezilla. . I can connect to this same server with port 21 with Fetch and WS FTP Client. CyberDuck acts the same as Filezilla and refuses to connect on port 21. I have tried adjusting the conection settings but, nothing helps.

here is what filezilla says.
first part when it does not connect is port 21. Then after I change it to 22 and connects fine.
Status: Resolving address of venow2.net
Status: Connecting to 50.231.9.230:21...
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: TLS connection established.
Status: Logged in
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/ve12" is current directory
Command: TYPE I
Response: 200 Transfer mode set to BINARY
Command: PASV
Response: 227 Entering Passive Mode (50,231,9,230,213,212).
Command: MLSD
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
Status: Disconnected from server
Status: Resolving address of venow2.net
Status: Connecting to 50.231.9.230:21...
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: TLS connection established.
Status: Logged in
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/ve12" is current directory
Command: TYPE I
Response: 200 Transfer mode set to BINARY
Command: PASV
Response: 227 Entering Passive Mode (50,231,9,230,213,213).
Command: MLSD
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
Status: Disconnected from server
Status: Connecting to venow2.net...
Status: Using username "ve12".
Status: Connected to venow2.net
Status: Retrieving directory listing...
Status: Listing directory /ve12
Status: Directory listing of "/ve12" successful

User avatar
botg
Site Admin
Posts: 35566
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: Can't connect to latest Progressive WS FTP Server

#2 Post by botg » 2024-01-12 23:17

Most likely some firewall or NAT router is interfering with the connection. Since you changed the server, it's most likely a server-side firewall or NAT router that is interfering with the connection.

Post Reply