Running Tool with Windows Firewall

Jul 13, 2011 at 5:38 PM

Has anybody been successfull running the tool (specifically the client health pieces) on XP SP3 workstations with the windows firewall enabled?  The inbound ports seem to vary, so I'm not sure of a good way to handle it.  We need to address on hundreds of clients.


Jul 13, 2011 at 6:46 PM


Please refer to this article about connecting to WMI through Windows firewall:

The tool uses mostly WMI to remotely manage the clients.


Good luck,


Jul 13, 2011 at 6:53 PM

unfortunately we had both 135 and unsecapp already allowed.  It works great if the firewall is turned off  Source port is usually in the 50000 range while the destination was 2611 one time 1103 another....I'm sure there are others

Jul 13, 2011 at 7:32 PM

135 and unsecapp are required for callback data FROM remote client to yours. For the connection TO remote computer you should allow remote administration on clients by either group policy or with NETSH command provided in this article.