Personally, I'd add Domain Controllers or find out why you get port exhaustion on them. Typically a pair of DCs can serve thousands of AD objects without being tasked, but depending on what's getting bogged down and the fuctional level you would want to consider the dynamic port ranges, and other AD necessary ports (i.e. 53, 88, etc). http://technet.microsoft.com/en-us/library/dd772723(v=ws.10).aspx I've found SCOM's 'port monitor' to be finicky, but this blog has a nice reliable script that monitors each server/agent locally rather than SCOM polling for it. http://operatingquadrant.com/2009/08/13/scom-locallly-monitoring-a-listening-tcp-port/ B. Wright

Personally, I'd add Domain Controllers or find out why you get port exhaustion on them. Typically a pair of DCs can serve thousands of AD objects without being tasked, but depending on what's getting bogged down and the fuctional level you would want to consider the dynamic port ranges, and other AD necessary ports (i.e. 53, 88, etc). http://technet.microsoft.com/en-us/library/dd772723(v=ws.10).aspx I've found SCOM's 'port monitor' to be finicky, but this blog has a nice reliable script that monitors each server/agent locally rather than SCOM polling for it. http://operatingquadrant.com/2009/08/13/scom-locallly-monitoring-a-listening-tcp-port/ B. Wright

Hello, I am looking to set a default set of port monitoring for all Windows servers within our server environment, some of our systems have encountered the TIME_WAIT port exhaustion issue and at times been unable to log onto the Domain. I'm thinking of ports such as LDAP 389 and 1433 - 1434 for SQL servers. LDAP 389 for Windows application servers, would there be any other ports recommended for alerting against this port exhaustion issue, these servers are added to a patching rotation within SCCM but downtime windows as far as time are a challenge for some of these hosts. Reboots are a challenge as a result of these downtime constraints. Thanks In Advance