I'm trying to monitor bandwidth usage of a VPS running Windows Server 2012 R2 using the Windows Network Card sensor. This sensor worked fine on a dedicated server we had in the past, but on the VPS it only measures Packets (volume) and Packets (speed). Total (volume), Total (speed), Traffic In (volume), Traffic In (speed), Traffic Out (volume) and Traffic Out (speed) are all 0 on every single interval check. Any idea why this sensor isn't working properly on the VPS?
Article Comments
I've already added the Windows Network Card sensor for both available interfaces. Both sensons are showing the same problem.
Mar, 2016 - Permalink
Hello,
thank you for your reply.
Please download our WMI Tester, run it on the PRTG Host (or host of the Remote Probe) and scan against this particular target, please perform the "Network" test from the Advanced tab, you'll also have to provide valid credentials on the "Basic" tab. Please share the result of the test. (Please perform the test at lease twice, this will allow us to confirm whenever any counters are increasing.
Please also see our extensive WMI Troubleshooting Guide:
Mar, 2016 - Permalink
Here are the test results:
BytesReceivedPersec;BytesSentPersec;BytesTotalPersec;Caption;CurrentBandwidth;Description;Frequency_Object;Frequency_PerfTime;Frequency_Sys100NS;Name;OffloadedConnections;OutputQueueLength;PacketsOutboundDiscarded;PacketsOutboundErrors;PacketsPersec;PacketsReceivedDiscarded;PacketsReceivedErrors;PacketsReceivedNonUnicastPersec;PacketsReceivedPersec;PacketsReceivedUnicastPersec;PacketsReceivedUnknown;PacketsSentNonUnicastPersec;PacketsSentPersec;PacketsSentUnicastPersec;TCPActiveRSCConnections;TCPRSCAveragePacketSize;TCPRSCCoalescedPacketsPersec;TCPRSCExceptionsPersec;Timestamp_Object;Timestamp_PerfTime;Timestamp_Sys100NS
0;0;0;"";1000000000;"";0;3579545;10000000;Intel[R] PRO_1000 MT Network Connection;0;0;0;0;20650424;0;0;0;16451996;16451996;0;0;4198428;4198428;0;0;0;0;0;633471858725;131021220439130000
0;0;0;"";1000000000;"";0;3579545;10000000;Intel[R] PRO_1000 MT Network Connection _2;0;0;0;0;6926722;0;0;0;886551;886551;0;0;6040171;6040171;0;0;0;0;0;633471858725;131021220439130000
0;0;0;"";100000;"";0;3579545;10000000;isatap.{8DCA0BD4-E7C5-4A2B-8CA1-3DADBE34B41A};0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;633471858725;131021220439130000
0;0;0;"";100000;"";0;3579545;10000000;isatap.{68070EF0-2960-4A53-B63B-8E03B05566BF};0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;633471858725;131021220439130000
1643;1082;2725;"";300000000;"";0;3579545;10000000;6TO4 Adapter;0;0;0;0;35;0;0;0;17;17;0;0;18;18;0;0;0;0;0;633471858725;131021220439130000
BytesReceivedPersec;BytesSentPersec;BytesTotalPersec;Caption;CurrentBandwidth;Description;Frequency_Object;Frequency_PerfTime;Frequency_Sys100NS;Name;OffloadedConnections;OutputQueueLength;PacketsOutboundDiscarded;PacketsOutboundErrors;PacketsPersec;PacketsReceivedDiscarded;PacketsReceivedErrors;PacketsReceivedNonUnicastPersec;PacketsReceivedPersec;PacketsReceivedUnicastPersec;PacketsReceivedUnknown;PacketsSentNonUnicastPersec;PacketsSentPersec;PacketsSentUnicastPersec;TCPActiveRSCConnections;TCPRSCAveragePacketSize;TCPRSCCoalescedPacketsPersec;TCPRSCExceptionsPersec;Timestamp_Object;Timestamp_PerfTime;Timestamp_Sys100NS
0;0;0;"";1000000000;"";0;3579545;10000000;Intel[R] PRO_1000 MT Network Connection;0;0;0;0;20656885;0;0;0;16457317;16457317;0;0;4199568;4199568;0;0;0;0;0;633633181706;131021220889820000
0;0;0;"";1000000000;"";0;3579545;10000000;Intel[R] PRO_1000 MT Network Connection _2;0;0;0;0;6926812;0;0;0;886638;886638;0;0;6040174;6040174;0;0;0;0;0;633633181706;131021220889820000
0;0;0;"";100000;"";0;3579545;10000000;isatap.{8DCA0BD4-E7C5-4A2B-8CA1-3DADBE34B41A};0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;633633181706;131021220889820000
0;0;0;"";100000;"";0;3579545;10000000;isatap.{68070EF0-2960-4A53-B63B-8E03B05566BF};0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;633633181706;131021220889820000
1643;1082;2725;"";300000000;"";0;3579545;10000000;6TO4 Adapter;0;0;0;0;35;0;0;0;17;17;0;0;18;18;0;0;0;0;0;633633181706;131021220889820000
Edit: Improved formatting.
Mar, 2016 - Permalink
There are basically the results (with some formatting):
Test 1
| Name | BytesReceivedPersec | BytesSentPersec | BytesTotalPersec |
|---|---|---|---|
| Intel[R] PRO_1000 MT [...] | 0 | 0 | 0 |
| Intel[R] PRO_1000 MT [...]_2 | 0 | 0 | 0 |
| isatap.{8DCA0BD4 [...] | 0 | 0 | 0 |
| isatap.{68070EF0 [...] | 0 | 0 | 0 |
| 6TO4 Adapter* | 1643 | 1082 | 2725 |
Test 2
| Name | BytesReceivedPersec | BytesSentPersec | BytesTotalPersec |
|---|---|---|---|
| Intel[R] PRO_1000 MT [...] | 0 | 0 | 0 |
| Intel[R] PRO_1000 MT [...]_2 | 0 | 0 | 0 |
| isatap.{8DCA0BD4 [...] | 0 | 0 | 0 |
| isatap.{68070EF0 [...] | 0 | 0 | 0 |
| 6TO4 Adapter* | 1643 | 1082 | 2725 |
As you can see, reported values were exactly the same on both tests, these values are simply reported as 0(other counters like Packets Received or Packets Sent have values) and this is what PRTG reports. Unfortunately we're not able to tell you why this happens, please check with the VPS provider or with the operating system's vendor for further investigation.
Alternatively, please check our WMI troubleshooting guide:
- KB: My WMI sensors don't work. What can I do?
- I have tried a lot of things to fix my WMI. What else can I try to avoid reinstalling Windows?
Best Regards,
Mar, 2016 - Permalink
Hello there arjancs,
we appreciate your contact.
When adding the Windows Network Card Sensor please check whenever there are other interfaces available and if you've select the "correct one". I recommend creating a sensor for each interface and then checking which one delivers "correct" data.
Best Regards,
Mar, 2016 - Permalink