Error 10048 In Function Bind Address Already In Use
Contents |
Address already in use Edit 3 … 0 Tags No tags Notify RSS Backlinks Source Print Export (PDF) Error bind failed with error 10048 10048 in function Bind Address already in use Table of Contents Explanation ipmsg bind error 10048 Causes Resolution See Also Explanation Most computers only have one network connection, yet lots of programs (including the SSLIP, Control, redis bind error 10048 and SMS) need to communicate on it. Each program running uses a "Port" to identify itself and communication over the network is targetted not only to the IP (computer address) but
Socket Bind Error 10048
also the port. When the SSLIP runs, it reserves ("binds") to specific ports so that SMS and Control can communicate with it. This error indicates that the ports being used are already in use. Causes In general, this error is caused by: Another program using the same port that Cyrious uses. Many programs randomly choose ports, so if the offending program is closed and winsock error 10048 address already in use reopened, the problem may not appear next time.Anti-virus software preventing Cyrious for connecting to the Internet. Resolution In most cases, the solution is to: Reboot the computer.Run the SSLIP immediately on startup (before other programs). Occassionally, you may need to change the ports used. You can do this by creating a port offset in the SSLIP and SMS or Control folders. Navigate to the Cyrious\SSLIP folderIf there is not a text file named "SSLIP_Options.txt, create one, if there is skip to the next stepEdit the text file and add a line "PortOffSet=xxx" (xxx is a 3 digit number of your choosing)Highlight and copy the "PortOffSet=xxx"Save and close the file.Navigate to the Cyrious\SMS or Cyrious\Control folder (depending on which one you have).If there is not a text file named "SMS_Options.txt" or "Control_Options.txt", create one, if there is skip to the next stepEdit the text file and paste in the line "PortOffSet=xxx" (xxx is the same number from above)Save and close the file.See Also Backlinks Page Date Edited Error 10048 in function Bind Address already in use Jun 1, 2010 SMS Unable to Open May 17, 2012 Javascript Required You need to
Calendar Gene6 FTP Server Forum > Gene6 FTP Server > Support > [EN] Support Board Guidelines View New Content Page 1 of 1 You cannot start a new topic You cannot reply to bind error 10048 in ip messenger this topic Address already in use gibberish password prompt, more Rate Topic: #1
Download A 10048 Error Repair Tool
fish New Member Group: Members Posts: 2 Joined: 09-August 04 Posted 09 August 2004 - 04:35 PM Getting error: 04/08/09 10:51:12,
Bind Error 10048 Fix
failed to listen on 192.168.3.2:21. Error 10048 in function Listen: Bind(192.168.3.2,21): Address already in useRunning G6 FTP Server 3.1.0 Build 70TCPView shows G6FTPServer was already listening on port 21 on 192.168.3.2 There are no other http://support.cyriouswiki.com/Error+10048+in+function+Bind+Address+already+in+use applications trying to listen on that port, so G6 was trying to listen on it twice?Tried connecting via FTP:C:\>ftp 192.168.3.2Connected to 192.168.3.2.200 1300User (192.168.3.2:(none)): testd ' x+?vGs¬µs*NMM¦U-¦J))J¦4PGsGs¬ss? åT¦^C- The customized welcome message was working the first day, but upon reboot, it now shows "1300" instead.- The password prompt comes up as gibberish.How do you fix the "failed to listen" error, messed up welcome message, and gibberish password prompt? 0 Back to http://www.g6ftpserver.com/forum/index.php?/topic/389-address-already-in-use/ top of the page up there ^ #2 Matthieu Addicted Member Group: Staff Posts: 1964 Joined: 22-October 03 Gender:Male Location:France : Mouy Interests:Science-fiction, World news Posted 09 August 2004 - 04:45 PM This means the remote admin is listening on the same port as the domain which is usually the consequence of entering "21" instead of leaving default "8021" value when the installer prompts you for the remote administration port or later when editing remote admin binding.To solve this, edit the file \remoteadmin\remote.ini and change 21 to 8021 in IP= line. (you will also need to edit the port in "local machine" properties in the admin client to properly connect). Gene6, SARL Do not use PM to ask for support, use the forum or support email. Special offer : 10% discount with coupon code : DISCOUNT 0 Back to top of the page up there ^ #3 fish New Member Group: Members Posts: 2 Joined: 09-August 04 Posted 09 August 2004 - 05:00 PM M.Roger, thank you very much for the fast response. I did what you said and it worked. 0 Back to top of the page up there ^ Forum Home Gene6 FTP Server |-- Announcements |-- Support |---- How to |---- [EN] Manual |---- [EN]
and both ends must ACK (acknowledge) each other's FIN packets. The FIN packets are initiated by the application performing a close(), a shutdown(), or an exit(). The ACKs are handled by the kernel http://hea-www.harvard.edu/~fine/Tech/addrinuse.html after the close() has completed. Because of this, it is possible for the process to complete before the kernel has released the associated network resource, and this port cannot be bound to another process until the kernel has decided that it is done. Figure 1 Figure 1 shows all of the possible states that can occur during a normal closure, depending on the order in which things happen. Note that if you initiate error 10048 closure, there is a TIME_WAIT state that is absent from the other side. This TIME_WAIT is necessary in case the ACK you sent wasn't received, or in case spurious packets show up for other reasons. I'm really not sure why this state isn't necessary on the other side, when the remote end initiates closure, but this is definitely the case. TIME_WAIT is the state that typically ties up the port for several minutes after bind error 10048 the process has completed. The length of the associated timeout varies on different operating systems, and may be dynamic on some operating systems, however typical values are in the range of one to four minutes. If both ends send a FIN before either end receives it, both ends will have to go through TIME_WAIT. Normal Closure of Listen Sockets A socket which is listening for connections can be closed immediately if there are no connections pending, and the state proceeds directly to CLOSED. If connections are pending however, FIN_WAIT_1 is entered, and a TIME_WAIT is inevitable. Note that it is impossible to completely guarantee a clean closure here. While you can check the connections using a select() call before closure, a tiny but real possibility exists that a connection could arrive after the select() but before the close(). Abnormal Closure If the remote application dies unexpectedly while the connection is established, the local end will have to initiate closure. In this case TIME_WAIT is unavoidable. If the remote end disappears due to a network failure, or the remote machine reboots (both are rare), the local port will be tied up until each state times out. Worse, some older operating systems do not implement a timeout for FIN_WAIT_2, and it is possible to get stuck there forever, in which case