Serv-u cannot connect to server 127.0.0.1, Port 43958 solution _ftp Server

Serv-u "Cannot connect to server 127.0.0.1, Port 43958" reason
Always do not understand the problem where, after the Internet to check the data, the approximate reasons are as follows:
43958, this is the SERV-U local management port, only allow 127.0.0.1 connection, this port is not connected, because:
1. Permissions are wrong. (I will add system again, and give default permissions, problem resolution.) ）
2. The problem of the software itself may also prohibit the 127.0.0.1 connection;
3. This problem can also occur with hacker attacks.

Serv-u "Cannot connect to server 127.0.0.1, Port 43958" error
1. How to Solve
After installing the Serveu plug-in, Seru cannot run online
After installing the Serveu plug-in, Seru cannot run online
Just join in the Servudaemon.ini
[EXTERNAL]
Eventhookdll1=bbsftp.dll
Clientcheckdll1=bbsftp.dll

I encountered problems and solutions:
Because the Serv-u service's running permissions were given to another user, because the user password that ran the Serv-u service was modified just now, the workaround is as follows:
Run services.msc to find Serv-u server name

First into user management (computer-right key properties-user management) modify password
Then in the picture above, the following password to modify the password, you can. Run the problem solved.

or refer to the following methods:
Because of the need to transfer files between the two computers, in their own computer installed Serv-u, years ago very good, after the new year to find bad use, in another with CUTEFTP landing hint failed, and then go to the local inspection
Execute serv-u Management program, prompt: Unable to connect to server 127.0.0.1, Port 43958
Always do not understand the problem where, after the Internet to check the data, the approximate reasons are as follows:

43958, this is the SERV-U local management port, only allow 127.0.0.1 connection, this port is not connected, because:

1. Permissions are wrong.

2. The problem of the software itself may also prohibit the 127.0.0.1 connection;

3. This problem can also occur with hacker attacks.

4, because serv-u more for cracked version, check whether the antivirus software will delete some files or quarantine.

The last one gave me a revelation:
It could be a problem with a soft or a firewall, so it's all closed and the problem remains.
View Task Manager No SERVU daemon, service not up,
Go to Computer Management to start the service and find the file is not found.
Go to the installation directory to see the next one, compared to another server, a few files. Estimated to be killed soft upgrade to remove.
No way to reload, reload in C or not, the main is to kill soft monitoring. There is a problem with the installation process, some files have just been installed on the kill soft Kill, configure the server prompts unable to access the file.
Pack in the safe area to remove the soft scan. Solve the problem.
Service normal needs:
Make sure the software is ok (mainly serial numbers and file integrity)
Ensure processes and services are normal
Make sure the firewall allows traffic and open the associated ports
Prevent the killing of soft manslaughter. (Put in safe area, exclude monitor, scan)