Ephemeral port range windows 2008

Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Note The FTP 7. Note To support ASP. Note You must be sure to set the commit parameter to apphost when you use AppCmd. In this article. Optional int attribute. Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information. 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. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta.

New post summary designs on greatest hits now, everywhere else eventually. Linked 7. Related Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled. Accept all cookies Customize settings. 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. Sockets are technically file handles. Some are normal, but large numbers of them are not hundreds to thousands. Close the process in question. If that restores outbound connectivity, then you have further proven that the app is the cause.

Contact the vendor of that app. Finally, if the above methods did not help you isolate the process, we suggest you collect a complete memory dump of the machine in the issue state. The dump will tell you which process has the maximum handles. As a workaround, rebooting the computer will get the it back in normal state and would help you resolve the issue for the time being. However, when a reboot is impractical, you can also consider increasing the number of ports on the machine using the below commands:.

This will set the dynamic port range to start at port and to end at port ports.