What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Why is port 1341 involved in WMI?

Votes:

0

I am testing the trial version of PRTG and have run into a bizarre problem. Both the PRTG computer and the target computer are VM guests on a Windows 2008 R2 Hyper-V server. I want to monitor a few WMI values, and have a Group Policy rule to allow incoming WMI, also to allow echo requests. These settings work fine for Spiceworks, but PRTG only retrieves WMI info when I also open port 1341 TCP.

I found this port number by examining the Windows Firewall log. This error appeared:

2011-03-08 17:14:58 DROP TCP 192.168.60.7 192.168.60.2 1030 1341 413 AP 3286503447 2969398679 65264 - - - RECEIVE

It seems there is an initial contact on port 135, then more contact on 1341 ... is this normal?

firewall ports wmi

Created on Mar 9, 2011 12:55:23 PM



1 Reply

Votes:

0

PRTG is simply using the Windows mechanism of asynchronous calls. please see: http://msdn.microsoft.com/en-us/library/aa389286%28VS.85%29.aspx As for why this affects port 1341 we don't know either.

To avoid possible trouble with DCOM complexities our recommendation is to use remote probes for monitoring WMI across domains.

Kind regards,

- Volker

Created on Mar 10, 2011 12:17:47 PM by Volker Uffelmann [Paessler Support]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.