Filezilla server does not want to listen

[CrimpOn]

I am SO SLOW. Of course there is a reason to specify an IP address for the Server Listeners:

The server computer may have more than one network interface, each with a different IP address, and FileZilla is to listen only to a specific network connection (or, perhaps, require different connection parameters on different network connections).
0.0.0.0 means "Listen on all network connections."

(Additional ignorance) Is it possible to bind more than one program to one network port? Could it be that another process is running on the computer and has taken port 21 before FileZilla is started?

[boco]

Here are two commands that'll show configured addresses better than ipconfig /all

Code: Select all

netsh int ipv4 show ipaddr
netsh int ipv6 show addr

Will display lease times also, and not reveal the hardware (MAC) addresses of your interfaces (except when not using IPv6 privacy extensions).

_____

As for the question, a port alone cannot be bound to. We are speaking of sockets here. A socket is simply a combination of a specific IP address and a port number. One example for a socket is 127.0.0.1:21.
0.0.0.0 and :: are non-specific IP addresses, more like a placeholder. 0.0.0.0:21 is therefore NOT a socket, it means "create a socket for any configured specific IP address and port 21, and bind to each of them. So, it would result at least in bindings to 127.0.0.1:21 and 192.168.1.2:21, plus, same for all the IPv6 addresses with remaining lifetime.

Yes, it can very well be that another FTP server has bound to the sockets FileZilla Server is attempting to use. Microsoft's IIS has such an FTP server (although an inferior one) and could block the ports. No idea if the WSL (Windows Subsystem for Linux) and WSA (Windows Subsystem for Android) can also occupy sockets, but it's possible.

Enter

netstat -a -b

into an administrative command shell (cmd.exe, Powershell or Terminal) and watch out for the 0.0.0.0:21 and [::]21 lines. It will try to identify the listening process on the line after.

Example from my system:

Code: Select all

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:21             ipv6:0                 LISTENING
 [filezilla-server.exe]
  TCP    0.0.0.0:22             ipv6:0                 LISTENING
 [filezilla-server.exe]
 
 .
 .
 .
 
  TCP    [::]:21                telemetry:0            LISTENING
 [filezilla-server.exe]
  TCP    [::]:22                telemetry:0            LISTENING
 [filezilla-server.exe]

[NikNikovsky]

Alright, will be tested.

[NikNikovsky]

I tried the netstat command and this is what i got:

Code: Select all

Proto  Local Address          Foreign Address        State
         TCP    0.0.0.0:21                        name               LISTENING
 [filezilla-server.exe]
         TCP    0.0.0.0:135                      name               LISTENING
  RpcSs

What do I do now?

[boco]

So, FileZila Server IS listening. Does it answer if you connect to 127.0.0.1 on the same machine?

[NikNikovsky]

Yes, it does.
It does not when i do it on the virtual machine (on the same pc)

[boco]

Virtual machines are, although virtual, different machines. The default network setting for a virtual machine is usually called NAT (or very similar). It puts another virtual router in front of the VM, which you need to configure, too, if the server is installed in the VM. With the server being installed on the Host machine, access from the VM out should work, provided you'll be using the LAN IP or computer name of the Host machine, and not localhost/127.0.0.1 (these won't work as it is, in fact, not the same machine).
However, setting the network type of the VM to Bridged mode will remove the virtual router and make the VM just another machine in your LAN. Then, it should work both ways.


If you are still getting red error messages, then something blocks just only your LAN IP. In that case, do the netstat command again but this tile look for "<yourLANaddress>:21". If something occupies that port, it should be listed here.

[NikNikovsky]

I changed the VM network settings to bridged, it still does not work.
There is also nothing using the 21 port.

[NikNikovsky]

I think I finally was able to get it up and running (in my VMs)!