Error 10048 Only One
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
address/port) is normally permitted .NET Framework > Windows Communication Foundation, Serialization, and Networking Question 1 Sign in to vote I have developped an application that call a WCF service Two error 10048 origin fix ChannelFactory
Origin Error 10048 Fifa 15
operation is carried out in a while condition and it's executed 30000 times. while (i<30000){try{OPen ChannelFactory
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies http://stackoverflow.com/questions/1339142/wcf-system-net-socketexception-only-one-usage-of-each-socket-address-protoco of this site About Us Learn more about Stack Overflow the company Business Learn more 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: error 10048 Sign up WCF: System.Net.SocketException - Only one usage of each socket address (protocol/network address/port) is normally permitted up vote 28 down vote favorite 10 I have a WCF service and a Web application. Web application makes calls to this WCF service in a continous manner a.k.a polling. In our production environment, I receive this error very rarely. Since, this is an internal error 10048 only activity users were not aware of when this error is thrown. Could not connect to http://localhost/QAService/Service.svc. TCP error code 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted 127.0.0.1:80. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted 127.0.0.1:80 I am having trouble in reproducing this behaviour in our dev/qa environment. I have made sure that the client connection is closed in a try..catch..finally block. Still don't understand what is causing this issue .. any one aware of this? Note: I've looked at this SO question, but not seems to be answering my problem, so it is not repeated questions. asp.net wcf socketexception share|improve this question asked Aug 27 '09 at 6:12 asyncwait 2,02042546 Is that because the web service is using port 80, which is in use by IIS? Which port does your service use in production? Which port, is IIS configured on in production? –shahkalpesh Aug 27 '09 at 6:20 It is same 80 for both applications. WCF service is configu