Error 10048 In Function Listen
Contents |
ease planning, as well. Free PRTG Download >> What is this? This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by error 10048 in function bind asking and answering questions! Learn more Top Tags 5731× prtg 1832× snmp 1462×
Error 10048 In Function Bind Address Already In Use
sensor 932× wmi 621× notifications 463× maps View all Tags How can I solve an error "10048 (Address already in use.)"
Error 10048 Only One Usage Of Each Socket Address
in Webserver Stress Tool? Votes:0 Your Vote: Up Down In Webserver Stress Tool, I get an error message # 10048 Address already in use. Where does it come from and how can I solve this
Error 10048 Tftpd32
issue? error networking registry webserver-stress-tool Created on Feb 24, 2010 9:05:50 AM by Daniel Zobel [Paessler Support] Last change on Jul 21, 2010 1:54:37 PM by Daniel Zobel [Paessler Support] Permalink 1 Reply Accepted Answer Votes:0 Your Vote: Up Down Avoiding "10048 (Address already in use.)" Errors in Webserver Stress Tool For high traffic scenarios this message shows a problem on the workstation running Webserver Stress Tool. The IP stack can't error 10048 origin create additional outgoing TCP/IP connections because it runs out of available socket numbers for the IP address(es) that you have configured in Webstress. This error occurs when your workstation cannot allocate new sockets. On Windows the default limitation is 5000 - 1024 open sockets (5000 is the default max user port setting and the first 1024 ports are reserved). You can increase the default maximum socket value in the registry: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Tcpip/Parameters and add or modify the MaxUserPort value. See Also Microsoft article: "When you try to connect from TCP ports greater than 5000 you receive the error 'WSAENOBUFS (10055)'" The Cable Guy article: "Windows TCP/IP Ephemeral, Reserved, and Blocked Port Behavior" Add comment Created on Feb 24, 2010 9:10:15 AM by Daniel Zobel [Paessler Support] Last change on Sep 1, 2015 8:07:43 AM by Erhard Mikulik [Paessler Support] Permalink Please log in or register to enter your reply. Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available. © 1998 - 2016 Paessler AG Solutions • Imprint • Contact • Sitemap • Privacy Policy • Uninstall • Terms
360 games PC games error 10048 origin fix Windows games Windows phone games Entertainment All Entertainment origin error 10048 fifa 15 Movies & TV Music Business & Education Business Students & educators winsock error 10048 Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet https://kb.paessler.com/en/topic/1213-how-can-i-solve-an-error-10048-address-already-in-use-in-webserver-stress-tool Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/173619 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this http://stackoverflow.com/questions/31912162/wsa-error-10048-when-binding-server-sockets site About Us Learn more about Stack Overflow the company Business Learn more http://hea-www.harvard.edu/~fine/Tech/addrinuse.html about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up WSA error 10048 error 10048 when binding server sockets up vote 2 down vote favorite I started with the simple server tutorial on the msdn website in order to learn how to use sockets in client and server applications. Once I was done following thet tutorial, I started adapting the client and server code into multithreaded proggrams in order to make a tchat client and server. Everything was going error 10048 in very well until I ran into WSA error 10048. I tried using different ports for each socket but it still did not solve the error. Here is my server code : #undef UNICODE #define WIN32_LEAN_AND_MEAN #include
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 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 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 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