Error In Binding A Socket 10048
Contents |
Studio 2015 products Visual Studio Team Services Visual Studio Code Visual Studio Dev Essentials Office Office Word/Excel/PowerPoint Microsoft Graph Outlook OneDrive/Sharepoint Skype Services Store Cortana Bing Application Insights Languages & platforms Xamarin ASP.NET C++ TypeScript error 10048 binding socket vpn .NET - VB, C#, F# Server Windows Server SQL Server BizTalk Server SharePoint couldn t bind socket winsock error 10048 Dynamics Programs & communities Students Startups Forums MSDN Subscriber downloads Sign in Search Microsoft Search Windows Dev Center Windows Dev Center windows socket error 10048 on api bind Explore What’s new for Windows 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build for enterprise Windows Store opportunities Docs Windows apps Get started Design and UI Develop API reference
Socket Error 10048 Maya
Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Why Windows Dashboard Explore What’s new for Windows 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build for enterprise Windows Store opportunities Docs Windows apps Get started Design and UI Develop API reference Publish Monetize error binding socket addr='af_unix(/dev/log)' error='address already in use (98)' Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Why Windows Dashboard Networking and Internet Windows Sockets 2 Winsock Reference Winsock Reference Windows Sockets Error Codes Windows Sockets Error Codes Windows Sockets Error Codes Socket Options Winsock IOCTLs Winsock Annexes Winsock Enumerations Winsock Functions Winsock Structures and Typedefs Winsock Tracing Events Winsock SPI Windows Sockets Error Codes TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Windows Sockets Error Codes Most Windows Sockets 2 functions do not return the specific cause of an error when the function returns. For information, see the Handling Winsock Errors topic. The WSAGetLastError function returns the last error that occurred for the calling thread. When a particular Windows Sockets function indicates an error has occurred, this function should be called immediately to retrieve the extended error code for the failing function call. These error codes and a short text description associated with an error code are defined in the Winerror.h header file. The FormatMessage function can be u
360 games PC games error binding socket addr='af_inet Windows games Windows phone games Entertainment All Entertainment
Error Binding Socket (3420)
Movies & TV Music Business & Education Business Students & educators
Socket Error 10038
Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx 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/819124 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
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 https://kb.paessler.com/en/topic/1213-how-can-i-solve-an-error-10048-address-already-in-use-in-webserver-stress-tool to get involved by asking and answering questions! Learn more Top Tags 5738× prtg 1835× snmp 1464× sensor 934× wmi 622× notifications 465× maps View all Tags How can I solve an error "10048 (Address already in use.)" 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 error 10048 come from and how can I solve this 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 error binding socket problem on the workstation running Webserver Stress Tool. The IP stack can't 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