Hi,
Whenever I try to add a Windows Network Card type sensor, I get the following error (or very similar to it, depending on the machine):
Failed to find valid network cards. Interface names ['Microsoft Virtual Machine Bus Network Adapter _5','MS TCP Loopback interface'] WMI Table [Win32_PerfRawData_Tcpip_NetworkInterface]
The odd thing this is that the PROBE's "Windows Network Card" sensors work just fine... just not for any other windows device on the network.
Regards,
Dave
Article Comments
Please use our WMI Tester, run it on the PRTG Host (or host of the Remote Probe) and scan against this particular target, with the following queries:
SELECT Description, IPAddress, MACAddress FROM Win32_NetworkAdapterConfiguration SELECT Name, BytesTotalPerSec FROM Win32_PerfRawData_Tcpip_NetworkAdapter SELECT Name, BytesTotalPersec FROM Win32_PerfRawData_Tcpip_NetworkInterface
Please then send us the results of these scans.
Mar, 2015 - Permalink
I have the exact same problem on various virtual machines.
Where can I send the results of the WMI query?
Apr, 2015 - Permalink
Send it to us via email to support@paessler.com with screenshots showing the error in PRTG.
Apr, 2015 - Permalink
Hi Arjan an Torstein,
I have an open case with Paessler that has been open since the 30th march 2015.
They say they are investigating the problem and have suggested to use SNMP to monitor bandwidth / traffic as a fall back measure.
You can also use the "contact support" feature from within your PRTG setup to send them additional diagnostic info that will hopefully help solve this issue.
I am eagerly awaiting a response to my support case from Paessler!
Regards,
Dave
Apr, 2015 - Permalink
Dave, your issue was caused by a bug in PRTG, that is fixed in current canary builds, and will reach stable with version 15.x.17. Please bear with us.
Apr, 2015 - Permalink
We ran into this same error. What we found is the "#" in the device name caused the error. You can see it in the name "Microsoft Virtual Machine Bus Network Adapter _5", it's substituting an _ for the #. Remove the # altogether and you don't have that issue.
You can change it in the registry. You'll find the "FriendlyName" somewhere in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ for the NIC. That key has special permissions so the easiest way is to use psexec.
1. Open a command prompt as Administrator
2. Run psexec -s -i regedt32.exe
3. Navigate to registry key, change the FriendlyName to something without the #
4. Reboot
EDIT BY MOD: Changed formatting
May, 2015 - Permalink
Sorry to resurrect an old topic, but I am not in a position where I can edit the mentioned registry values.
Is there another alternative?
Jul, 2015 - Permalink
Hello acurus_ds,
This bug shouldn't be a problem anymore, the bug is fixed in the latest 15.3.17.xxxx version.
Make sure you're running the latest version (PRTG > Setup > Auto-Update) and try adding the sensors again, if you're still receiving and error, please contact us using the Contact Support form within PRTG so that we can properly troubleshoot your issue.
Jul, 2015 - Permalink
I still have this issue, I have 2 BCM5709C Nics teamed together. I tried to change the "friendlyname" in the registry, and after a reboot , it would add the Number back so I would get "_44 #44".
Any Ideas?
Aug, 2015 - Permalink
Hello jmmarch, as of PRTG version 15.3.17 and onward the issue should be fixed, hence the registry hack shouldn't be necessary anymore.
Note: Teamed adapters are only supported on Windows 2012 and 2012R2 using the built-in teaming support, third party teaming solutions are not supported by the Windows Network Card sensor.
In such cases consider monitoring via SNMP instead, you can use the following sensor:
Best Regards,
Aug, 2015 - Permalink
I am not sure this relevant this is what i did "I Changed WinHttpAutoProxySvc service from Disabled to Automatic and Started the IP helper service"
Jun, 2020 - Permalink
Hi ramvenkey,
Could you please let me know in which version your workaround helped to solve the issue?
Jun, 2020 - Permalink
Some additional information on this:
The WMI Network issues only started once going from free/trial edition to the paid edition where I had to install the paid edition of PRTG software.
I've also added a new probe to a brand new network, server is only 3 months old running server 2012r2. Same WMI network sensor problem. I've also tried temporarily disabling windows firewall, still the same problem occurs. The server has also been rebooted along with the external PRTG monitoring server.
The correct windows credentials are being used, and also the PRTG WMI tool can read WMI information without a problem.
.NET Framework 4 is installed as well.
See below for error when adding WMI Network Sensor:
Failed to find valid network cards. Interface names ['WAN Miniport [IP]','WAN Miniport [IPv6]','WAN Miniport [Network Monitor]','Microsoft Kernel Debug Network Adapter','Broadcom NetXtreme Gigabit Ethernet','Broadcom NetXtreme Gigabit Ethernet _2','Intel[R] Gigabit 2P I350-t Adapter','Intel[R] Gigabit 2P I350-t Adapter _2','Local Area Connection* 1','Local Area Connection* 2','Local Area Connection* 3','Local Area Connection* 4',isatap.<3F9E4A04-4F91-44ED-91FC-81B6A63FC935>,'Local Area Connection* 11'] WMI Table [Win32_PerfRawData_Tcpip_NetworkAdapter]
Mar, 2015 - Permalink