New Server 2016 cannot read remote directory

Advertisement

gwatchma
Joined:
Posts:
5
Location:
milwaukee

New Server 2016 cannot read remote directory

To All,

I am setting up a new Server2016 within a domain and have installed IIS FTP, added a user for the purpose of FTP, made sure that the FTP user has rights to the ftp root which is c:\inetpub\wwwroot. The log below shows how I can create a secure connection but fail to read the remote directory. I am a programmer much more than a server expert and use the FTP to publish my websites to the server from my development platform. I set this up fine on my Server2012 machine years ago without encryption but very much wish to use encryption for the new 2016 Server. Any help appreciated!

Greg

. 2020-06-10 19:36:13.263 Using TLSv1.2, cipher TLSv1/SSLv3: FCDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA, FCDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=RSA Enc=ASGCM(256) Mac=AEAD
. 2020-06-10 19:36:13.272 TLS connection established. Waiting for welcome message...
> 2020-06-10 19:36:13.272 USER myusernameishere
< 2020-06-10 19:36:13.272 331 Password required
> 2020-06-10 19:36:13.272 PASS *********
< 2020-06-10 19:36:13.301 230 User logged in.
> 2020-06-10 19:36:13.301 SYST
. 2020-06-10 19:36:13.302 The server is probably running Windows, assuming that directory listing timestamps are affected by DST.
< 2020-06-10 19:36:13.302 215 Windows_NT
> 2020-06-10 19:36:13.302 FEAT
< 2020-06-10 19:36:13.303 211-Extended features supported:
< 2020-06-10 19:36:13.303 LANG EN*
< 2020-06-10 19:36:13.313 UTF8
< 2020-06-10 19:36:13.313 AUTH TLS;TLS-C;SSL;TLS-P;
< 2020-06-10 19:36:13.313 PBSZ
< 2020-06-10 19:36:13.313 PROT C;P;
< 2020-06-10 19:36:13.313 CCC
< 2020-06-10 19:36:13.313 HOST
< 2020-06-10 19:36:13.313 SIZE
< 2020-06-10 19:36:13.313 MDTM
< 2020-06-10 19:36:13.313 REST STREAM
< 2020-06-10 19:36:13.313 211 END
> 2020-06-10 19:36:13.313 OPTS UTF8 ON
< 2020-06-10 19:36:13.313 200 OPTS UTF8 command successful - UTF8 encoding now ON.
> 2020-06-10 19:36:13.313 PBSZ 0
< 2020-06-10 19:36:13.313 200 PBSZ command successful.
> 2020-06-10 19:36:13.313 PROT P
< 2020-06-10 19:36:13.313 200 PROT command successful.
. 2020-06-10 19:36:13.336 Connected
. 2020-06-10 19:36:13.337 --------------------------------------------------------------------------
. 2020-06-10 19:36:13.337 Using FTP protocol.
. 2020-06-10 19:36:13.337 Doing startup conversation with host.
> 2020-06-10 19:36:13.351 PWD
< 2020-06-10 19:36:13.352 257 "/" is current directory.
. 2020-06-10 19:36:13.352 Getting current directory name.
. 2020-06-10 19:36:13.386 Retrieving directory listing...
> 2020-06-10 19:36:13.386 TYPE A
< 2020-06-10 19:36:13.387 200 Type set to A.
> 2020-06-10 19:36:13.387 PASV
< 2020-06-10 19:36:13.388 227 Entering Passive Mode (14,111,0,91,209,196).
> 2020-06-10 19:36:13.388 LIST -a
. 2020-06-10 19:36:13.388 Connecting to 14.111.0.91:53700 ...
< 2020-06-10 19:36:13.391 150 Opening ASCII mode data connection.
. 2020-06-10 19:36:28.992 Timeout detected. (data connection)
. 2020-06-10 19:36:28.992 Could not retrieve directory listing

Reply with quote

Advertisement

gwatchma

Arggg

Figured it out. I missed the comment that the Microsoft FTP service does not make changes to its behavior until the service is restarted. Just restarted it and all is good.

Greg

Reply with quote

Advertisement

You can post new topics in this forum