Filezilla Server does not accept connections on server startup or reboot

[Michael Kadel]

I have installed 0.9.3.1 beta on Windows Server 2003. I have it running as a system service. After install and setup I had no issues connecting with either an FTP client or via the FileZilla Server Administration Console.

After rebooting the server, FileZilla Server doesn't accept connections from the administration console. The administration console run locally shows that it has connected to the server and then says
"connected, waiting for authentication"

It stops there.

If I run the administration console on another machine it can't connect to the server at all.

This can be resolved if I go into Task Manager on the server and kill the FileZilla Server.exe process, then start the FileZilla Server service either by going to services.msc or using the shortcut in the start menu. After I restarting the service connections are accepted normally from FTP clients, the local admin console, and an admin console run on a another computer.

IIS is installed on the server but all the services related to it are set to manual and are not running (IIS Admin Service, FTP Publishing Service, HTTP SSL, World Wide Web Publishing Service). When I first discovered this problem I thought these services were at fault so I set them to manual and stopped them but it did not resolve the issue.

We also have McAfee antivirus 8.5i installed and running and windows system firewall is off.

[Michael Kadel]

I forgot to say: The FileZilla Server service does say that it is started when the machine first boots up. So it appears to be running, just not accepting connections.

[Michael Kadel]

Figured this out. I had to edit the registry on the server so the FileZilla Server service depends on the McShield service. (McAffee VirusScan 8.5.) Apparently when FileZilla Server started up before McShield it would keep it from accepting connections.

[Tim Kosse]

In other words, totally broken virus scanner. They all are.