Failed to bind the listen socket

[soneal]

I am running Filezilla server version 0.9.31 beta and have been successfully for well over a year. My Filezilla server is used at a business and is accessed every day. However, I have had a reoccurring problem in that about every 2-3 months I see the error below in the log file and the server goes offline. All I have to do is access the server, open Filezilla server, click the Server tab, and recheck the Active option and the server is fine for another few months. Is there a fix to or thought on why this happens? Thanks. - Scott

FileZilla Server version 0.9.31 beta started
Initializing Server.
Creating listen socket on port 21...
Failed to bind the listen socket on port 21 to the following IPs: 172.xxx.xxx.xxx
Creating listen socket on port 990...
Failed to bind the listen socket on port 990 to the following IPs: 172.xxx.xxx.xxx
Server not online.

[botg]

Are you using any firewalls?

[mucisland]

Same here:

----
FileZilla Server version 0.9.32 beta started
Initializing Server.
Creating listen socket on port 21...
Failed to bind the listen socket on port 21 to the following IPs: 5.x.y.z
----

I bound FZS to two IPs, one is working fine, the other (5.x.y.z, Hamachi) not.

The error occurs only if I start FZS with a dedicated ftpserver user account. Under the SYSTEM account I can connect from both networks.

I followed this guide for creating a separate user account: http://wiki.filezilla-project.org/Secur ... stallation

Is the socket binding also subject to ACL security?

Best Regards,
Dirk

[botg]

Is the socket binding also subject to ACL security?

No idea, ask Microsoft.

[fileZillaGio]

Did someone solve this problem?
I think there is some privilege than "LocalSystem" has and my user don't.
Any idea?