Port Exhaustion and You (or, why the Netstat tool is your friend)

Directory Services: Port Exhaustion

Directory Services: Port Exhaustion — Thu, 30 Oct 2008 12:13:08 GMT

PingBack from http://www.ditii.com/2008/10/30/directory-services-port-exhaustion/

re: Port Exhaustion and You (or, why the Netstat tool is your friend)

dsmvp — Thu, 30 Oct 2008 18:20:31 GMT

Great post David. I'm going to have remember this one. Oh and you're right Fallout 3 does RULE.

Port Exhaustion on ISA Server 2006 while Publishing Outlook Anywhere

Yuri Diogenes's Blog — Tue, 18 Nov 2008 03:14:03 GMT

Last week we (ISA Server Team in Texas) faced an interesting issue where remote Outlook Clients using

re: Port Exhaustion and You (or, why the Netstat tool is your friend)

rhcellxion — Tue, 06 Jan 2009 00:52:23 GMT

I'm having this exact issue. After running netstat, I show many instances of the server having established connections to it's loopback address 127.0.0.1:9400. Port 9400 is the port that our application uses. Is it uncommon for these connections to be happening?

re: Port Exhaustion and You (or, why the Netstat tool is your friend)

NedPyle — Tue, 06 Jan 2009 01:18:10 GMT

Not if the application is written (intentionally or otherwise ;-) ) to do this... it is entirely up to the app, not Windows.

- Ned

re: Port Exhaustion and You (or, why the Netstat tool is your friend)

rhcellxion — Tue, 06 Jan 2009 19:54:28 GMT

is there a manual way to kill the connections short of rebooting the server?

re: Port Exhaustion and You (or, why the Netstat tool is your friend)

NedPyle — Tue, 06 Jan 2009 20:17:47 GMT

If the application/service is stopped, all ports associated with that application should be closed within 4 minutes by default. There should be no need to restart the server.

- Ned