Error 10048 Only One Usage Of Each
Contents |
(84)On-Premise SEARCH Knowledgebase How To Fix Error "Only one usage of each socket address (protocol/network address/port) is normally permitted" If
Error 10048 Only One Usage Of Each Socket Address
you see the error, "Only one usage of each socket address (protocol/network error 10048 tftpd32 address/port) is normally permitted" in the logs when a connection is being made, it means that you
Error 10048 In Function Bind
are exhausting all the available network ports on the machine. By default the OS only has around 4000 ports available that are not reserved by the system. What happens error 10048 in function bind address already in use is that when any network connection is closed it goes into a TIME_WAIT state for 240 seconds and cannot be reused until this wait state is over. So as an example, if there are 16 connections per second for 4 minutes (16*4*60=3840), you will exhaust all the ports shortly there after. Now if you have HAS and error 10048 origin the MTA on the same machine, this will get exhausted a lot sooner because in addition to them communicating with each other, which uses 2 ports (one for the MTA and one for HAS), the MTA uses up a lot of ports sending the mail. You can fix this by modifying the below values. 1. One of the ways is to increase the dynamic port range. The max by default is 5000. You can set this up to 65534. HKLM\System\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPort is the key to use. 2. The second thing you can do is, once the connection does get into an TIME_WAIT state, you can reduce the time it isin that state. Default is 4 minutes, but you can set this to 30 seconds. HKLM\System\CurrentControlSet\Services\Tcpip\Parameters\TCPTimedWaitDelay is the key to use. After these changes are made the system must be restarted. For more information, please refer to the following Microsoft KB article. https://msdn.microsoft.com/en-us/library/ee377084%28v=bts.70%29.aspx Comments (0) Help Desk Software by KayakoCopyright © 2016 SocketLabs, Inc.Terms of Service | Privacy Policy | Acceptable Use Policy
AlertSite API Performance Monitoring Software Testing TestComplete Automated Testing Platform TestComplete Desktop TestComplete Web
Error 10048 Origin Fix
TestComplete Mobile TestLeft Functional Testing for Developers QAComplete Test Management c# only one usage of each socket address (protocol/network address/port) is normally permitted LoadComplete Load Testing CrossBrowserTesting Cloud Testing Platform Monitoring AlertSite Application Quality & Performance Monitoring Code
System.net.sockets.socketexception: Only One Usage Of Each Socket Address
Collaboration Collaborator Code Review & Document Review Code Optimization AQtime Pro Performance Profiling Free Tools Collaborator LoadComplete Open Source SoapUI Swagger Plugins Support Support when https://support.socketlabs.com/index.php?/Knowledgebase/Article/View/61/0/how-to-fix-error-only-one-usage-of-each-socket-address-protocolnetwork-addressport-is-normally-permitted you need it Browse our support portal SmartBear technical representatives are always ready to help with your product needs. Know what you're looking for? Downloads User Guides How To Tutorials Learn QA Screencasts/Videos General Support Forums Troubleshooter FAQs Product Versions Online Help Resources Company Company About SmartBear Leadership Customers https://community.smartbear.com/t5/General-Discussions/Error-Only-one-usage-of-each-socket-address-protocol-network/td-p/75780 Careers Contact Us News Press Releases Industry News Events Awards Media Kit Community SmartBear Blog Product Forums SmartBear Developer Network Support Social Media Twitter Facebook YouTube LinkedIn Google Plus Buy Contact Blog Community Login Go to SmartBear Community Go to SmartBear Products AlertSite QAComplete Go to SmartBear Licensing System Register · Sign In · Help SmartBear Community : TestComplete : General Discussions : Error: Only one usage of each socket address (prot... General Discussions Go To SmartBear Community Community Feedback and Suggestions Community Matters Blog SmartBear Developer Network Forum for developers building plugins for SmartBear's API products TestComplete Extensions Forum for discussions about using the Collaborator API AlertSite AlertSite AlertSite Community Edition AlertSite Feature Requests AQtime AQtime AQtime Feature Requests Collaborator Collaborator Collaborator Feature Requests LoadComplete LoadComplete LoadComplete Feature Requests QAComplete and ALMComplete QAComplete and ALMComplete QAComplete Feature Requests Ready! API Platform and Tools Service Virtualization/Virtual
system fails to open a port to communicate to the domain for the service permissions check. This is generally a transitory error and is unrelated to the service. Solution: You may be able to wait for five minutes, and then restart the service successfully. http://datuhaire.blogspot.com/2014/07/howto-resolve-only-one-usage-of-each.html If the error persists, it can usually be resolved in Windows by setting the registry keys in the articles below. The referenced keys do not exist by default in the registry, so you have to make them to change the https://forum.utorrent.com/topic/41567-help-with-tracker/ system settings from their default. Another possible reason is that you are overloading the TCP/IP stack. Windows (and I think all socket stacks actually) have a limitation on the number of sockets that can be opened in rapid sequence due to error 10048 how sockets get closed under normal operation. Whenever a socket is closed, it enters the TIME_WAIT state for a certain time (240 seconds IIRC). Each time you poll, a socket is consumed out of the default dynamic range (I think it's about 5000 dynamic ports just above 1024), and each time that poll ends, that particular socket goes into TIME_WAIT. If you poll frequently enough, you will eventually consume all of the available ports, which will result in TCP error 10048. only one usage Generally, WCF tries to avoid this problem by pooling connections and things like that. This is usually the case with internal services that are not going over the internet. I am not sure if any of the wsHttp bindings support connection pooling, but the netTcp binding should. I would assume named pipes does not run into this problem. I couldn't say for the MSMQ binding. There are two solutions you can use to get around this problem. You can either increase the dynamic port range, or reduce the period of TIME_WAIT. The former is probably the safer route, but if you are consuming an extremely high volume of sockets (which doesn't sound like the case for your scenario), reducing TIME_WAIT is a better option (or both together.) Changing the Dynamic Port Range Open regedit. Open key HKLM\System\CurrentControlSet\Services\Tcpip\Parameters Edit (or create as DWORD) the MaxUserPort value. Set it to a higher number. (i.e. 65534) Changing the TIME_WAIT delay Open regedit. Open key HKLM\System\CurrentControlSet\Services\Tcpip\Parameters Edit (or create as DWORD) the TCPTimeWaitDelay. Set it to a lower number. Value is in seconds. (i.e. 60 for 1 minute delay) One of the above solutions should fix your problem. If it persists after changing the port range, I would see try increasing the period of your polling so it happens less frequently. That will give you more leeway to work around the time wait delay. I would change the time wait delay as a last res