Quantcast
Channel: General
Viewing all articles
Browse latest Browse all 7363

After LIST command, connection time out (and, additional "quick" question, hopefully!)

$
0
0

Hi,

So, I have set up an ftp-server, in IIS, that I can access remotely, using IisManagerAuth.

When I connect using Windows command line tool FTP, i can after entering user and pw, i can use "binary", and then "ls", to successfully, get a listing of files/folders at the server.

However, using FileZilla, and the same user/pw combination, I get the following output:

Status: Resolving address of my-domain.com
Status: Connecting to xxx.xxx.xxx.xxx:21...
Status: Connection established, waiting for welcome message...
Response: 220 Microsoft FTP Service
Command: USER OPTA
Response: 331 Password required for OPTA.
Command: PASS ***********
Response: 230 User logged in.
Command: OPTS UTF8 ON
Response: 200 OPTS UTF8 command successful - UTF8 encoding now ON.
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: TYPE I
Response: 200 Type set to I.
Command: PASV
Response: 227 Entering Passive Mode (31,18,71,68,236,249).
Command: LIST
Response: 150 Opening BINARY mode data connection.
Error: Connection timed out
Error: Failed to retrieve directory listing

Most of the time.

It seems to work, "intermittently", but usually, returns that error.

I have no idea why? Firewall Settings, etc., should be correct, and, the fact that it seems to work sometimes, i think, supports that, so, what can be causing this?

P.S.: While we're at it, I'll ask one more question, instead of using an extra thread, for that.

I have a client requirement, that "Responses of the FTP server should be “unix-like”."".

Is it possible to set this, in IIS, or is it, possibly, even, how the ftp server acts, by default?

Thanks for any help, on either of these questions!

Cheers!


Viewing all articles
Browse latest Browse all 7363

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>