Custom Query (8142 matches)

I recently had ATT install their "Fixed Wireless" service for Internet at my house. The ATT Fixed Wireless system uses an antenna on the roof to receive signal from the ATT cellular network to deliver Internet via a wire to a new router they installed the home. It is NOT a "hotspot." Anyway, after it was installed, I found I could no longer use FileZilla to connect via secure FTP to my server (I previously never had any trouble). Fortunately, I had not yet disconnected the previous Internet connection, so I switched to that router and was able to connect as I had previously.

I called ATT Fixed Wireless for some help and, although I ended up getting disconnected before I was connected to tech support, the "receptionist" opined that the issue could be related to lack of support for "port forwarding" in their ATT Fixed Wireless service. I do not have sufficient knowledge to know if that is the issue, but mention it in case there is any relevance.

The settings that I have always used for this server are:

Protocol: FTP - File Transfer Protocol Host: ecbiz198.inmotionhosting.co Port: (blank) Encryption: Use explicit FTP over TLS is available Logon: Normal

Here is the dialog text for FAILURE TO CONNECT using ATT Fixed Wireless:

Status: Resolving address of ecbiz198.inmotionhosting.com Status: Connecting to 104.193.142.7:21... Status: Connection established, waiting for welcome message... Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ---------- Response: 220-You are user number 5 of 150 allowed. Response: 220-Local time is now 04:49. Server port: 21. Response: 220-This is a private system - No anonymous login Response: 220-IPv6 connections are also welcome on this server. Response: 220 You will be disconnected after 30 minutes of inactivity. Command: AUTH TLS Response: 502 AUTH TLS OK. Command: AUTH SSL Error: Could not read from socket: ECONNRESET - Connection reset by peer Error: Could not connect to server Status: Waiting to retry... Status: Resolving address of ecbiz198.inmotionhosting.com Status: Connecting to 104.193.142.7:21... Status: Connection established, waiting for welcome message... Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ---------- Response: 220-You are user number 5 of 150 allowed. Response: 220-Local time is now 04:49. Server port: 21. Response: 220-This is a private system - No anonymous login Response: 220-IPv6 connections are also welcome on this server. Response: 220 You will be disconnected after 30 minutes of inactivity. Command: AUTH TLS Response: 502 AUTH TLS OK. Command: AUTH SSL Error: Could not read from socket: ECONNRESET - Connection reset by peer Error: Could not connect to server

Here is the dialog text for SUCCESSFUL CONNECTION using DSL:

Status: Resolving address of ecbiz198.inmotionhosting.com Status: Connecting to 209.182.196.149:21... Status: Connection established, waiting for welcome message... Status: Initializing TLS... Status: Verifying certificate... Status: TLS connection established. Status: Logged in Status: Retrieving directory listing... Status: Directory listing of "/" successful

I tried the two other "secure" protocols available in FileZilla (using the ATT Fixed Wireless network) and the result was the same unsuccessful connection attempt. Then I tried the standard unencrypted FTP over Port 21 and that worked fine (e.g. the ATT Fixed Wireless successfully connected me to my server using vanilla FTP, but would not work with any secure method).

I did not try SFTP because I have never been successful in getting that set up on the server or client side.

It is hard to believe this is not something I can resolve with a tweak to an existing setting (which I do not know about), but if not, it seems to me that is is going to prevent me from using FileZilla and I certainly hope that is not the outcome, because the ATT Fixed Wireless connection is 20 times faster than my now-disconnected DSL.

Can't use SFTP on any version after 3.20.1 to the Lenovo ix2-dl NAS.

Status:	Connecting to xxx.ddns.net:1977...
Response:	fzSftp started, protocol_version=9
Command:	open "ftp@xxx.ddns.net" 1977
Command:	Pass: ********
Error:	FATAL ERROR: Remote side sent disconnect message
Error:	type 11 (by application):
Error:	"Unsupported protocol sequence"
Error:	Could not connect to server

Note: 1977 port is forwarded to 22 on router.

Works fine with 3.20.1 and below. Also tested with latest versions of other ftp clients such as CyberDuck and FireFTP and they work fine.

Downloading the installer triggers an antivirus warning on Windows 10 security

I understand that the installer has a spyware / adware installer that can be bypassed by not agreeing to the terms, but in the past this was categorized as a Adware, not Trojan.

Trojan:Win32/Casdet!rfn

The MD5 is 7223E53696865C0728AB2971009C4DA9

See the VirusTotal here: ​https://www.virustotal.com/gui/file/eaebaea7ff465cd3aeb57d595883813c170748a810336759d2526cce3ac873ed/detection