10048 Error
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 10048 error origin & platforms Xamarin ASP.NET C++ TypeScript .NET - VB, C#, F# Server download a 10048 error repair tool Windows Server SQL Server BizTalk Server SharePoint Dynamics Programs & communities Students Startups Forums MSDN Subscriber downloads Sign socketspy error 10048 in Search Microsoft Search Windows Dev Center Windows Dev Center Explore What’s new for Windows 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build for enterprise Windows Store windows socket error 10047 opportunities Docs Windows apps Get started Design and UI Develop API reference 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
Error 10048 Ipsec
for enterprise Windows Store opportunities Docs Windows apps Get started Design and UI Develop API reference 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 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 imm
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 Only One Usage
asking and answering questions! Learn more Top Tags 5705× prtg 1832× snmp 1458× error 10048 tftp sensor 928× wmi 616× notifications 459× maps View all Tags How can I solve an error "10048 (Address already in use.)" error 10048 logmein 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 https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx 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 https://kb.paessler.com/en/topic/1213-how-can-i-solve-an-error-10048-address-already-in-use-in-webserver-stress-tool 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
in Use Sidebar General FAQ How To's Video Tutorials Reference Guide Troubleshooting how_to:10048 Socket Error 10048 - Specified Address Already in Use This https://wiki.pscs.co.uk/how_to:10048 error only normally occurs during VPOP3 startup. It occurs if some other software running on the same machine as VPOP3 is using one of the ports that VPOP3 is already using. This could be a proxy like WinGate, WinProxy or anti-virus software that acts as a proxy, an LDAP server (e.g. Active Directory) error 10048 or another mail server program (e.g. Exchange Server). The latter two causes are particularly common on server versions of Windows. To prevent this problem you should either remove the conflicting service from the other software or change the port which either that other software or VPOP3 uses for that mail service. You 10048 error origin can change the ports that VPOP3 uses for its various services on the Services page in the VPOP3 settings. There are two ways to find out which program is using the conflicting port number. Each provides different evidence so if the results of one method are unclear try the other. Method 1 Open a command prompt and at the prompt type in telnet