User guide

that uses DCOM) connects to a target server initially using port 135, and the target responds with a

dynamic port number for WMI to use for the rest of the session. This port can be in one of the ranges

above, which are quite large by default.

To address this, you can easily specify a custom range for RPC dynamic ports. You may have

already done this in your environment in order to enable networked DCOM access for other

applications. It is recommended that you start no lower than port 50000, and allocate no fewer than

255 dynamic ports.

For example, to do this on Server 2008, you can use this command:

netshintipv4setdynamicporttcpstart=50000num=255

You may need to reboot. More info: http://support.microsoft.com/default.aspx/kb/929851

On other Windows versions, you can use DCOM config in Component Services

(http://support.microsoft.com/kb/300083) or the registry (http://support.microsoft.com/kb/154596).

You will need to reboot.

You will also need to have your network administrator open up the same port range on the firewall

between the SQL Sentry Server machine and any servers monitored with PA.

How to configure RPC dynamic port allocation to work with firewalls

http://support.microsoft.com/kb/154596

How To Restrict TCP/IP Ports on Windows 2000 and Windows XP

http://support.microsoft.com/kb/300083

How to troubleshoot WMI-related issues in Windows XP SP2

http://support.microsoft.com/kb/875605

DCOM port range configuration problems

http://support.microsoft.com/default.aspx/kb/217351

The default dynamic port range for TCP/IP has changed in Windows Vista and in Windows Server 2008

http://support.microsoft.com/default.aspx/kb/929851

Service overview and network port requirements for the Windows Server system

http://support.microsoft.com/kb/300083