Connection established, initializing TLS

[terrywhitejr2000]

2012-02-03 10:07:45 6240 3 Status: Selected port usually in use by a different protocol.
2012-02-03 10:07:45 6240 3 Status: Connecting to 70.61.249.5:21...
2012-02-03 10:07:45 6240 3 Status: Connection established, initializing TLS...
2012-02-03 10:09:51 6240 3 Error: Could not connect to server
2012-02-03 10:09:51 6240 3 Status: Waiting to retry...
2012-02-03 10:09:56 6240 3 Status: Connecting to 70.61.249.5:21...
2012-02-03 10:09:56 6240 3 Status: Connection established, initializing TLS...
2012-02-03 10:12:06 6240 3 Error: Could not connect to server

[boco]

Could you post the complete log? Concerning the first warning, are you trying to connect on the wrong port maybe (e. g. FTP on port 80 or 22)?

[terrywhitejr2000]

2012-02-03 10:07:45 6240 3 Status: Selected port usually in use by a different protocol.
2012-02-03 10:07:45 6240 3 Status: Connecting to 70.x.x.x:21...
2012-02-03 10:07:45 6240 3 Status: Connection established, initializing TLS...
2012-02-03 10:09:51 6240 3 Error: Could not connect to server
2012-02-03 10:09:51 6240 3 Status: Waiting to retry...
2012-02-03 10:09:56 6240 3 Status: Connecting to 70.x.x.x:21...
2012-02-03 10:09:56 6240 3 Status: Connection established, initializing TLS...
2012-02-03 10:12:06 6240 3 Error: Could not connect to server
2012-02-03 10:14:33 6240 3 Status: Selected port usually in use by a different protocol.
2012-02-03 10:14:33 6240 3 Status: Connecting to 70.x.x.x:21...
2012-02-03 10:14:33 6240 3 Status: Connection established, initializing TLS...
2012-02-03 10:16:41 6240 3 Error: Could not connect to server
2012-02-03 10:16:41 6240 3 Status: Waiting to retry...
2012-02-03 10:16:46 6240 3 Status: Connecting to 70.x.x.x:21...
2012-02-03 10:16:46 6240 3 Status: Connection established, initializing TLS...
2012-02-03 10:18:56 6240 3 Error: Could not connect to server
2012-02-03 12:52:45 6240 3 Status: Selected port usually in use by a different protocol.
2012-02-03 12:52:45 6240 3 Status: Connecting to70.x.x.x:21...
2012-02-03 12:52:45 6240 3 Status: Connection established, initializing TLS...
2012-02-03 12:54:10 6240 3 Error: Connection attempt interrupted by user
2012-02-03 12:54:33 6240 3 Status: Selected port usually in use by a different protocol.
2012-02-03 12:54:33 6240 3 Status: Connecting to 70.x.x.x:22...
2012-02-03 12:54:44 6240 3 Error: Connection attempt interrupted by user
2012-02-03 12:55:01 6240 3 Status: Selected port usually in use by a different protocol.
2012-02-03 12:55:01 6240 3 Status: Connecting to 70.x.x.x:21...
2012-02-03 12:55:01 6240 3 Status: Connection established, initializing TLS...
2012-02-03 12:57:10 6240 3 Error: Could not connect to server
2012-02-03 12:57:10 6240 3 Status: Waiting to retry...
2012-02-03 12:57:15 6240 3 Status: Connecting to 70.x.x.x:21...
2012-02-03 12:57:15 6240 3 Status: Connection established, initializing TLS...
2012-02-03 12:59:25 6240 3 Error: Could not connect to server

[boco]

Do you try to connect on port 21 using Implicit FTP over TLS (FTPS)? If using Implicit you need to use port 990. On port 21, you'd have to select FTP over TLS Explicit (FTPES).

FYI, the default ports: FTP and FTPES use port 21. FTPS uses 990, and SFTP uses port 22.

[terrywhitejr2000]

Im am trying on 21, when I try on 22 the server dont respond my guess is its not listening on that port.

[boco]

Im am trying on 21

Yes, but did you select FTP over TLS Explicit or Implicit?

[terrywhitejr2000]

Sorry for the late reply but this is what I am getting now.
2012-02-03 10:07:45 6240 3 Status: Selected port usually in use by a different protocol.
2012-02-03 10:07:45 6240 3 Status: Connecting to 70.x.x.x.x...
2012-02-03 10:07:45 6240 3 Status: Connection established, initializing TLS...
2012-02-03 10:09:51 6240 3 Error: Could not connect to server
2012-02-03 10:09:51 6240 3 Status: Waiting to retry...
2012-02-03 10:09:56 6240 3 Status: Connecting to 70.x.x.x:21...
2012-02-03 10:09:56 6240 3 Status: Connection established, initializing TLS...
2012-02-03 10:12:06 6240 3 Error: Could not connect to server
2012-02-03 10:14:33 6240 3 Status: Selected port usually in use by a different protocol.
2012-02-03 10:14:33 6240 3 Status: Connecting to 70.x.x.x:21...
2012-02-03 10:14:33 6240 3 Status: Connection established, initializing TLS...
2012-02-03 10:16:41 6240 3 Error: Could not connect to server
2012-02-03 10:16:41 6240 3 Status: Waiting to retry...
2012-02-03 10:16:46 6240 3 Status: Connecting to 70.x.x.x:21...
2012-02-03 10:16:46 6240 3 Status: Connection established, initializing TLS...
2012-02-03 10:18:56 6240 3 Error: Could not connect to server
2012-02-03 12:52:45 6240 3 Status: Selected port usually in use by a different protocol.
2012-02-03 12:52:45 6240 3 Status: Connecting to 70.x.x.x:21...
2012-02-03 12:52:45 6240 3 Status: Connection established, initializing TLS...
2012-02-03 12:54:10 6240 3 Error: Connection attempt interrupted by user
2012-02-03 12:54:33 6240 3 Status: Selected port usually in use by a different protocol.
2012-02-03 12:54:33 6240 3 Status: Connecting to 70.x.x.x:22...
2012-02-03 12:54:44 6240 3 Error: Connection attempt interrupted by user
2012-02-03 12:55:01 6240 3 Status: Selected port usually in use by a different protocol.
2012-02-03 12:55:01 6240 3 Status: Connecting to 70.x.x.x:21...
2012-02-03 12:55:01 6240 3 Status: Connection established, initializing TLS...
2012-02-03 12:57:10 6240 3 Error: Could not connect to server
2012-02-03 12:57:10 6240 3 Status: Waiting to retry...
2012-02-03 12:57:15 6240 3 Status: Connecting to 70.x.x.x:21...
2012-02-03 12:57:15 6240 3 Status: Connection established, initializing TLS...
2012-02-03 12:59:25 6240 3 Error: Could not connect to server
2012-02-06 09:36:15 3336 3 Status: Selected port usually in use by a different protocol.
2012-02-06 09:36:15 3336 3 Status: Connecting to 70.x.x.x:21...
2012-02-06 09:36:15 3336 3 Status: Connection established, initializing TLS...
2012-02-06 09:38:23 3336 3 Error: Could not connect to server
2012-02-06 09:38:23 3336 3 Status: Waiting to retry...
2012-02-06 09:38:28 3336 3 Status: Connecting to 70.x.x.x:21...
2012-02-06 09:38:28 3336 3 Status: Connection established, initializing TLS...
2012-02-06 09:40:38 3336 3 Error: Could not connect to server
2012-02-08 08:03:22 7424 3 Status: Connecting to 70.x.x.x:21...
2012-02-08 08:03:22 7424 3 Status: Connection established, waiting for welcome message...
2012-02-08 08:03:23 7424 3 Response: 220 Microsoft FTP Service
2012-02-08 08:03:23 7424 3 Command: AUTH TLS
2012-02-08 08:03:23 7424 3 Response: 234 AUTH command ok. Expecting TLS Negotiation.
2012-02-08 08:03:23 7424 3 Status: Initializing TLS...
2012-02-08 08:03:23 7424 3 Status: Verifying certificate...
2012-02-08 08:03:27 7424 3 Command: USER msoftpuser
2012-02-08 08:03:27 7424 3 Status: TLS/SSL connection established.
2012-02-08 08:03:27 7424 3 Response: 331 Password required for msoftpuser.
2012-02-08 08:03:27 7424 3 Command: PASS ***********
2012-02-08 08:03:27 7424 3 Response: 230-You have connected to the Secure USACECOMS FTP Server.
2012-02-08 08:03:27 7424 3 Response: 230 User logged in.
2012-02-08 08:03:27 7424 3 Command: SYST
2012-02-08 08:03:27 7424 3 Response: 215 Windows_NT
2012-02-08 08:03:27 7424 3 Command: FEAT
2012-02-08 08:03:27 7424 3 Response: 211-Extended features supported:
2012-02-08 08:03:27 7424 3 Response: LANG EN*
2012-02-08 08:03:27 7424 3 Response: UTF8
2012-02-08 08:03:27 7424 3 Response: AUTH TLS;TLS-C;SSL;TLS-P;
2012-02-08 08:03:27 7424 3 Response: PBSZ
2012-02-08 08:03:27 7424 3 Response: PROT C;P;
2012-02-08 08:03:27 7424 3 Response: CCC
2012-02-08 08:03:27 7424 3 Response: HOST
2012-02-08 08:03:27 7424 3 Response: SIZE
2012-02-08 08:03:27 7424 3 Response: MDTM
2012-02-08 08:03:27 7424 3 Response: REST STREAM
2012-02-08 08:03:27 7424 3 Response: 211 END
2012-02-08 08:03:27 7424 3 Command: OPTS UTF8 ON
2012-02-08 08:03:27 7424 3 Response: 200 OPTS UTF8 command successful - UTF8 encoding now ON.
2012-02-08 08:03:27 7424 3 Command: PBSZ 0
2012-02-08 08:03:27 7424 3 Response: 200 PBSZ command successful.
2012-02-08 08:03:27 7424 3 Command: PROT P
2012-02-08 08:03:27 7424 3 Response: 200 PROT command successful.
2012-02-08 08:03:27 7424 3 Status: Connected
2012-02-08 08:03:27 7424 3 Status: Retrieving directory listing...
2012-02-08 08:03:27 7424 3 Command: PWD
2012-02-08 08:03:28 7424 3 Response: 257 "/" is current directory.
2012-02-08 08:03:28 7424 3 Command: TYPE I
2012-02-08 08:03:28 7424 3 Response: 200 Type set to I.
2012-02-08 08:03:28 7424 3 Command: PASV
2012-02-08 08:03:28 7424 3 Response: 227 Entering Passive Mode (70,61,249,5,46,225).
2012-02-08 08:03:28 7424 3 Command: LIST
2012-02-08 08:03:28 7424 3 Response: 150 Opening BINARY mode data connection.
2012-02-08 08:03:49 7424 3 Error: GnuTLS error -53: Error in the push function.
2012-02-08 08:03:49 7424 3 Error: Directory listing aborted by user
2012-02-08 08:04:06 7424 3 Response: 550 Data channel timed out.
2012-02-08 08:04:11 7424 3 Status: Disconnected from server
2012-02-08 08:04:11 7424 3 Status: Connecting to 70.x.x.x:21...
2012-02-08 08:04:11 7424 3 Status: Connection established, waiting for welcome message...
2012-02-08 08:04:11 7424 3 Response: 220 Microsoft FTP Service
2012-02-08 08:04:11 7424 3 Command: AUTH TLS
2012-02-08 08:04:11 7424 3 Response: 234 AUTH command ok. Expecting TLS Negotiation.
2012-02-08 08:04:11 7424 3 Status: Initializing TLS...
2012-02-08 08:04:11 7424 3 Status: Verifying certificate...
2012-02-08 08:04:11 7424 3 Command: USER msoftpuser
2012-02-08 08:04:11 7424 3 Status: TLS/SSL connection established.
2012-02-08 08:04:11 7424 3 Response: 331 Password required for msoftpuser.
2012-02-08 08:04:11 7424 3 Command: PASS ***********
2012-02-08 08:04:11 7424 3 Response: 230-You have connected to the Secure USACECOMS FTP Server.
2012-02-08 08:04:11 7424 3 Response: 230 User logged in.
2012-02-08 08:04:11 7424 3 Command: OPTS UTF8 ON
2012-02-08 08:04:11 7424 3 Response: 200 OPTS UTF8 command successful - UTF8 encoding now ON.
2012-02-08 08:04:11 7424 3 Command: PBSZ 0
2012-02-08 08:04:11 7424 3 Response: 200 PBSZ command successful.
2012-02-08 08:04:11 7424 3 Command: PROT P
2012-02-08 08:04:11 7424 3 Response: 200 PROT command successful.
2012-02-08 08:04:11 7424 3 Status: Connected
2012-02-08 08:04:11 7424 3 Status: Retrieving directory listing...
2012-02-08 08:04:11 7424 3 Command: PWD
2012-02-08 08:04:11 7424 3 Response: 257 "/" is current directory.
2012-02-08 08:04:11 7424 3 Command: TYPE I
2012-02-08 08:04:12 7424 3 Response: 200 Type set to I.
2012-02-08 08:04:12 7424 3 Command: PASV
2012-02-08 08:04:12 7424 3 Response: 227 Entering Passive Mode (70,61,249,5,46,224).
2012-02-08 08:04:12 7424 3 Command: LIST
2012-02-08 08:04:12 7424 3 Response: 150 Opening BINARY mode data connection.
2012-02-08 08:04:33 7424 3 Error: GnuTLS error -53: Error in the push function.
2012-02-08 08:04:51 7424 3 Response: 550 Data channel timed out.
2012-02-08 08:04:51 7424 3 Error: Failed to retrieve directory listing

[terrywhitejr2000]

Encryption is set to require explicit FTP over TLS

[boco]

Normally I'd ask you to test your server against our https://ftptest.net/ site. Unfortunately it doesn't support TLS, yet. Something seems to block the server's data ports.

As a workaround you could try configuring FileZilla and switch to Active mode (Network Configuration), but in the long run Passive is better, so you should check if the problem is with the server (e. g. by connecting from a different system/network).

[terrywhitejr2000]

I got it to work late yesterday, it seems that it is using more than port 21. A tcpdump noted that it was jumping to several other ports. We opened the other ports and it works like a charm.

[boco]

Yes, of course, the Passive data range. Only the initial connection is on the listening port.

[commmo]

I had a similar problem with Filezilla and my provider, why I read the http://wiki.filezilla-project.org/Netwo ... a_sabotage again and again.

I then noticed this area:

Therefore, having protocol specific features enabled in a NAT router by default can create significant problems. The solution to all this, then, is to know your router's settings, and to know the configuration abilities of a router before you set it up. A good NAT router should always be fully protocol-agnostic. The exception is if you as the user have explicitly enabled this feature, knowing all its consequences.

I then went through my CISCO router configuration for the 5th time, and noticed this little feature: IPS Function.
Turns out, it has Anomaly Detection for the most common protocols where FTP is part of this.

I disabled this setting - and a few days frustration was finally put to rest.

I hope this can help other in situations like mine.