FZ will connect to Firestick on wifi, but not eithernet

[scottpi]

I have an Amazon Fire Stick. I have ES File Manager on it.

When the Stick is on Wifi, I go to Remote Manager in ES File Manager, and "turn on". It says Connected, and the ftp://192.168.1.97:3721

I input those on FileZilla, and connect just fine. I can move files, and view folders. Works great. On Wifi.

But my wifi is far away, and weak. So transfers are very slow. Glacial.

I have an ethernet cable running from the router to the stick. So . . .

Using that for the stick to access the internet, I go to Remote Manager in ES File Manager, turn it on, and it says Connected, ftp://192.169.49.1:3721

And the stick IS on the internet. I can open a browser, and go to sites. Good connection speed.

BUT, FZ will not connect using ethernet using that 192.168.49.1 address. On ethernet, I get:

Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Disconnected from server
Status: Connecting to 192.168.49.1:3721...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Waiting to retry...
Status: Connecting to 192.168.49.1:3721...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server

The weird part is, when I first got the stick, and began using FZ, it worked great on the ethernet. Lasted fine for 3 months.
Then, One day, it would not connect. I checked the ES File Manager, and the ftp address had changed.
I don't remember what it had been, but the "new" address would no longer work. I don't think it had 49 in the 3rd set of numbers.

So, I check the stick itself, and IT says it's IP address is 192.168.1.16. when on the ethernet.
This is confirmed when I check the ASUS router Network Map. Same IP.

But that's not what the ES File manager says. It says 192.168.49.1:3721

So, I put the stick's address in FZ. 192.168.1.16:3721

And FZ connects, but can't read anything:

Status: Connecting to 192.168.1.16:3721...
Status: Connection established, waiting for welcome message...
Status: Insecure server, it does not support FTP over TLS.
Status: Logged in
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 (192,168,49,1,7,209).
Command: LIST
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing


So, how can I connect from my laptop (ethernet to ASUS router) to the stick on ethernet, at 192.168.1.16?

Or how do I get ES File Manager to let in thru this IP address?

Frustrating. Especially since it worked great for 3 months, then something change . . . I don't know what.
The adaptor that lets the ethernet connect thru the stick's USB port can't be the problem, since I bought a new one, same result.

Thanks

[boco]

The problem doesn't have anything to do with FileZilla. THe whole issue is that the stick is picking up a bogus IP address which doesn't seem to work. Unfortunately, it also configured the FTP server with that IP.

Command: PASV
Response: 227 Entering Passive Mode (192,168,49,1,7,209).

That's why it stops. Same wrong IP.


You need to check why the stick is picking up that rogue IP, in the first place. If it isn't configured manually anywhere, my best guess would be a rogue DHCP server giving out the bogus IPs.

[scottpi]

Ok, that's a start.

The ES File Manager gives me that ftp address.
I installed Amaze File Manager, same 192.168.49.1 address, with different port.

The stick itself says it's ip address is 192.169.1.16.

Why would they be different?

But when I try THAT address in FZ, it will connect but not read files.
If it connects, why won't it read files?

So. I don't see where to go from here.

[boco]

I already answered that. The FTP server FileZilla connects to announces a wrong IP in the Passive reply (see the red part). Passive data connections are separate from the initial one and use the IP and port from the PASV reply. Files cannot be read as the data connection attempts to connect to the given (wrong) IP.

The whole problem is with that wrong IP. As ES File Explorer seems to assign that IP, you should start checking there.

[scottpi]

Yes, I was wondering about ES File Explorer.

So I download Amaze File Explorer on the Stick.

Under ftp in Amaze, it gives the same address as ES -- 192.168.49.1

However, ES says port 3721, while Amaze says port 2211.

Not sure how that works. Tried both, no reading of files.

I know you said the stick is "picking up the wrong address", but it actually says, in its network settings, the right address.

And when I put that right address in FZ, it connects, but won't read the files.

I don't understand how any of this works, so I don't know why that is.

The ES File manager gets the right ip when the stick is on wifi. So the stick gets that right, and FZ gets full access, by wifi.

But when on ethernet, it gives a non-working ip address to both file manager programs I've tried.

I'm afraid I'm old and retired, and this is exceeding my understanding . . . Thanks for trying.

[scottpi]

I spoke with Amazon Fire Stick tech service.

Then acknowledge that they did a major software update, and rolled it out right when I lost access.

They say they are working on figuring out what happened.

Scott