failed to create listen socket...server not online

[ibanez7]

Hello
I've read and searched the forum but am still not getting anywhere.
I have installed Filezilla server on a PC and keep getting the error :
Failed to create a listen socket on port 21. Failed to create a listen socket on any port specified. Server is not online.
So i installed the Filezilla server on another computer and all works perfectly. The only problem is that it's not the computer that this needs to be installed on. Since it's working on another PC I know for a fact that my port forwards and ACL work well and are not the problem.
I then did a : netstat -a -n on both the PC that works and the one that it doesn't so here are the results from both:

Here are the results on PC that work correctly:

C:\Documents and Settings\admin>netstat -a -n

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:21 0.0.0.0:0 LISTENING **** tcp port 21 is listening
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1028 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1683 127.0.0.1:14147 ESTABLISHED ****this is the default server
TCP 127.0.0.1:1806 127.0.0.1:1807 ESTABLISHED
TCP 127.0.0.1:1807 127.0.0.1:1806 ESTABLISHED
TCP 127.0.0.1:1809 127.0.0.1:1810 ESTABLISHED
TCP 127.0.0.1:1810 127.0.0.1:1809 ESTABLISHED
TCP 127.0.0.1:5152 0.0.0.0:0 LISTENING
TCP 127.0.0.1:5152 127.0.0.1:1808 CLOSE_WAIT
TCP 127.0.0.1:14147 0.0.0.0:0 LISTENING
TCP 127.0.0.1:14147 127.0.0.1:1683 ESTABLISHED
TCP 127.0.0.1:30606 0.0.0.0:0 LISTENING
TCP 172.16.2.11:139 0.0.0.0:0 LISTENING
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:4500 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:1930 *:*
UDP 172.16.2.11:123 *:*
UDP 172.16.2.11:137 *:*
UDP 172.16.2.11:138 *:*
UDP 172.16.2.11:1900 *:*

Here are the results on PC that requires the filezilla server installation:
C:\Documents and Settings\pc2>netstat -a -n

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:21 0.0.0.0:0 LISTENING *****it's listening here on 21
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2002 0.0.0.0:0 LISTENING
TCP 0.0.0.0:10115 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1038 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1044 127.0.0.1:2002 ESTABLISHED
TCP 127.0.0.1:2002 127.0.0.1:1044 ESTABLISHED
TCP 127.0.0.1:2906 127.0.0.1:2907 ESTABLISHED
TCP 127.0.0.1:2907 127.0.0.1:2906 ESTABLISHED
TCP 127.0.0.1:2911 127.0.0.1:2912 ESTABLISHED
TCP 127.0.0.1:2912 127.0.0.1:2911 ESTABLISHED
TCP 127.0.0.1:3683 127.0.0.1:30606 CLOSE_WAIT
TCP 127.0.0.1:3794 127.0.0.1:30606 ESTABLISHED
TCP 127.0.0.1:5152 0.0.0.0:0 LISTENING
TCP 127.0.0.1:5152 127.0.0.1:3801 CLOSE_WAIT
TCP 127.0.0.1:30606 0.0.0.0:0 LISTENING
TCP 127.0.0.1:30606 127.0.0.1:3794 ESTABLISHED
TCP 172.16.2.12:139 0.0.0.0:0 LISTENING
TCP 172.16.2.12:3795 64.94.18.153:443 ESTABLISHED
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:3456 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:10115 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:3416 *:*
UDP 172.16.2.12:123 *:*
UDP 172.16.2.12:137 *:*
UDP 172.16.2.12:138 *:*
UDP 172.16.2.12:1900 *:*

I don't see the TCP 127.0.0.1:14147 ESTABLISHED part on this computer. Could this be the problem and if yes how do i go at fixing this ?

Thanks

[botg]

Did you accidentally select 21 as administration port during setup?

[ibanez7]

Ok
I configured my windows server 2003 as an ftp server, connected it to my network and all works perfectly. I would however still like to figure out why filezilla server works on some PC's but not on others if anyone has any ideas. Like i mentionned before i got it working on 1 PC but not on the other. There has to be a simple explanation and way to get this going.
The reason i'd like to get it going is that this is for lab purposes and I don't usually have my wk3 server on except for when it's required. If I can get filezilla server working on that PC then i can use it for configurations and server at the same time.
Anyone have any ideas to try?

[ibanez7]

thanks for the help botg.

No i left it with the default 14147. I installed and removed it at least 4 times but still won't become active.

[ibanez7]

Here's the cause and the fix to the problem:

fix: Failed to create listen socket on port 21 : Filezilla

You have installed Filezilla server and tried to start it.
From the log, you find out that the following error has happened :

“FileZilla Server version 0.9.33 or 0.9.34 beta started
Initializing Server.
Creating listen socket on port 21…
Failed to create listen socket on port 21
Server not online.”

What to do ?

Reason
Port 21 is already being used. Thats why Filezilla server can’t bind on it.

Solution
1. Find out who is using it. Execute the following command in command prompt

$ netstat -abn

look for mention of “21″ in its output.

If you get “inetinfo.exe” associated with 21, it means that IIS server is running on your machine and he is listening on port 21. Disable IIS from running his FTP server.

2. Stop IIS FTP server

Control Panel -> Administrative Tools -> Internet Information Server -> right click on FTP -> Stop

[boco]

You should stay away as far as possible from that IIS crap.

[urchin]

I have had the same with a win2k computer in the past. From your "listening"list it also seems the http server of IIS is listening (port 80 and 443). Don't know if you need it, already shut down IIS in total or that you already use http with some other server, but otherwise it might be worth looking into...

urchin

[tx9999]

Creating listen socket on port 5000...
Creating listen socket on port 5000...
Failed to create listen socket on port 5000
Server online
------------------------------------------


Along the lines of the failed to create listen socket, why does it say this twice, but then say online?

The connections work fine to the server also. Works great!

[boco]

Did you try to assign the FTPS listening port to the same as the standard listening port? The FTPS port (in the SSL settings) must be different.

[tx9999]

Did you try to assign the FTPS listening port to the same as the standard listening port? The FTPS port (in the SSL settings) must be different.

Why yes it is. I wanted to use a specific port, 5000. What should I set it at to keep the port 5000?

[boco]

The normal port in General settings is for normal FTP and explicit FTPES. The port in the SSL/TLS settings is for implicit FTPS. Both can be chosen freely but CANNOT be the same.

You seem to have set them to the same port, which is not possible.

[tx9999]

It works though. I want ssl. Should i set one for 5000 and one for 5001? I dont want to use 21 to help prevent attacks.

[boco]

You need to set the port in SSL/TLS settings only if you want IMPLICIT SSL/TLS.

Should i set one for 5000 and one for 5001?

Yes, OK, they just cannot be set both to the same port.

[tx9999]

You need to set the port in SSL/TLS settings only if you want IMPLICIT SSL/TLS.

Should i set one for 5000 and one for 5001?

Yes, OK, they just cannot be set both to the same port.

It makes sense, but it does work fine with both of them set the same.

Well, which one should I use? I simply want a good SSL security method.

[boco]

It makes sense, but it does work fine with both of them set the same.

No, it does not. While the normal listening port is set correctly, setting the implicit FTPS fails, so it is not online.

Well, which one should I use? I simply want a good SSL security method.

I recommend to clear the implicit FTPS port field. The best TLS option is using explicit FTPES. Explicit connections use the normal listening port to connect and then switch to TLS/SSL via the AUTH TLS command. So I'd go with explicit.