Offline solution of serv_U domain

1. Caused by IIS service conflict

Because IIS is installed on Windows Server, the system's IIS service is enabled, and the IIS service has a default FTP site. The default port is 21, the default port in the SERV-U is 21, which happens to be a conflict (you can modify the iis or serv_u service port ).
[Solution] So I stopped the FTP service in IIS (or changed the FTP service port in IIS, or changed the default port of Serv-U ), you can use SERV-U normally.

Not all of them work. I found that Serv-U still prompts "domain is offline ". Simply think about it and you will be able to understand it. In my opinion, FTP in IIS service is stopped, but the status in Serv-U domain is still not refreshed or changed. Therefore, you only need to change the current status of Serv-U or log out of Serv-U and log on again.

In fact, another important issue is registration information. Check whether your Serv-U has been successfully registered.

2. Incorrect permission settings

If our resume has an FTP space. The corresponding permissions are set in the SERV-U. But FTP still login can not upload files, check the disk and directory permissions identified by the SERV-U, if there is no serv account in the permission account, we manually add a and set the corresponding read and write permissions.

Iii. Automatic offline Serv-U domain

It is strange that the Serv-U domain is automatically offline when the server is started and the domain IP address is re-entered in the self-built FTP in the next few days. After the application, it will be normal. However, after the restart, the FTP connection fails.
View the Serv-U log:

Wed 29Apr09 07:58:56-server is not listening on ip 172.16.88.202: Trying to use non-existent IP address?
Normally:

Wed 29Apr09 09:07:24-FTP Server listening on port number 21, IP 172.16.88.202, 127.0.0.1
View windows Event Logs and application-related events:

FTP Server listening on port number 43958, IP 127.0.0.1
Server is not listening on ip 172.16.88.202: Trying to use non-existent IP address?
In the System Event Log:

Your computer failed to renew the IP address (from the DHCP server) for the NIC whose network address is 0015600F1E28 ). The following error occurs:
The Traffic Signal timeout time has reached. The computer will continue to try to obtain the address from the network address (DHCP) server. Based on this, I think there is a problem with IP Address allocation through DHCP, so the Serv-U domain is automatically offline. Therefore, I changed the IP address of the Serv-U domain to "use any available IP Address ".

Based on this, I think there is a problem with IP Address allocation through DHCP, so the Serv-U domain is automatically offline. Therefore, I changed the IP address of the Serv-U domain to "use any available IP Address ".

In this way, FTP can be normally used to replace any IP address.
However, I still haven't figured out what went wrong when DHCP obtained the IP address.