This support article provides solutions on what to do when you see an error in the Windows Server event viewer that contains:. The full error message is at the bottom of this article. Under certain conditions it is possible that the available ports in the default range will be exhausted. A new client connection will be refused if all ports are used and a message will be written to the event log.
When a FileHold Server application is very busy with client requests, each FileHold client is making repeated, authenticated calls to the FileHold server application, and consequently there is repeated and continuous open and closing of connections. By default there are ports available in Windows because the usable port range is between port and port The FileHold web services communicate with the authenticated client repeatedly.
On a very busy server the FileHold application can run into these port bottlenecks within the Windows server. By default on Windows servers the operating system allows socket connections to be established between the ports — ; this equates to a little over 13, user ports. Fixes for netstat, back-ported to R2, allowed Netstat. See Windows Server R2: Ephemeral ports hotfixes to learn more. Open the server. If you do not find any entries, then the server is still not out of ports. If you find them, then you can confirm that the server is under port exhaustion.
The key is to identify which process or application is using all the ports. Below are some of the tools that you can use to isolate to one single process. Start by looking at the netstat output. Alternately, you can also run the below PowerShell command to identify the process:. Most port leaks are caused by user-mode processes not correctly closing the ports when an error was encountered.
At the user-mode level ports actually sockets are handles. Both TaskManager and ProcessExplorer are able to display handle counts which allows you to identify which process is consuming all of the ports. If method 1 does not help you identify the process prior to Windows 10 and Windows Server R2 , then have a look at Task Manager:. Sort the column handles to identify the process with the highest number of handles. Usually the process with handles greater than could be the culprit except for processes like System, lsass.
If any other process than these has a higher number, stop that process and then try to login using domain credentials and see if it succeeds. If Task Manager did not help you identify the process, then use Process Explorer to investigate the issue. Download Process Explorer and run it Elevated. Examine the processes with higher handle counts than the rest will likely be over 10, if you can't make outbound connections. In the lower pane, the handles listed as below are sockets.
During performance testing completed for this guide it was observed that Windows Server appears to be tuned by default. Modification of registry settings should only be done after a careful analysis of the effects on the system.
The MaxUserPort value controls the maximum port number used when an application requests any available user port from the system. Normally, short-lived ports are allocated in the range from through The port range is now truly a range with a starting point and with an endpoint.
The new default start port is , and the default end port is This range is in addition to well-known ports that are used by services and by applications.
Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Windows Server x64 edition separately, contact Microsoft for technical support. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback?
0コメント