Mdxy-dxy font: [
increase
Reduced] type: reprint
Today, when I configured filezilla for a client, Filezilla Failed to create the listen Socket on port 21 for IPv4. It turned out that the 21 port was occupied, so it was ok to change the port
When Windows Server 2003 USES Filezilla, once installed, clicking on “Active” may report the following error
Creating listen socket on port 21…
Failed to create listen socket on port 21 for IPv4
Failed to create listen socket on port 21 for IPv6
Failed to create a listen socket on any of the specified ports. Server is not online!
Creating listen socket on port 21…
Failed to create listen socket on port 21 for IPv4
Failed to create listen socket on port 21 for IPv6
Failed to create a listen socket on any of the specified ports. Server is not online!
Creating listen socket on port 21…
Failed to create listen socket on port 21 for IPv4
Failed to create listen socket on port 21 for IPv6
specific solutions:
this is usually the case because port 21 is occupied, first use this command to query
copy code code as follows:
netstat -abn |findstr 21
check to see if your iis built-in FTP is turned on, or if you have installed some other FTP software, stop first, then enable filezilla, it is ok.
Read More:
- The Tomcat connector configured to listen on port 8080 failed to start. The port may already be in u
- The Tomcat connector configured to listen on port 7014 failed to start
- Solution to the problem that listen TCP 0.0.0.0:3306: bind: address already in use port is occupied in Linux centos7
- Through PID (process identification) to find the port (port) occupied applications, to solve the problem of port occupied
- socket.error : [errno 10048] and view PID process number and port number
- FileZilla server failed to initialize SSL Library
- Centos Failed to Modify the port of SSH: error: Bind to port 27615 on 0.0.0.0 failed: Permission denied.
- Error starting userland proxy: listen TCP 0.0.0.0:9000: Listen: address already in use
- Port 4200 is already in use.Use ‘-port’ to specify a different port error Reasons
- Error: listen eadrinuse::: 8000 solution
- Node start – create a server listening port.
- The error record when docker starts Nacos, and the solution to the problem of port occupation
- License Error: “Failed to Open the TCP Port Number in the License” Ultimate Solution
- [Linux] curl: (7) failed to connect to 127.0.0.1 port 1086: connection reused solution
- On fileZilla unable to connect FATAL ERROR: Connection union
- InternalError: Failed to create session. Error and solution
- What should be paid attention to in socket programming — bind socket error: address already in use
- FileZilla 425 Can’t open data connection
- View port and resolve port conflict in Windows
- [Windows] Socket Server Failed to bind, error 10048