Page 1 of 1

PDH Counter no data received

Posted: Thu Jul 17, 2025 8:56 am
by steak1986
Hey we recently had to update nsclient from a very old version (0.3.9) to a new version (0.9.6). When we did this we had to rebuild the ini file we had been using since the syntax was very different. I was able to update the INI and deploy to our 120 servers.

Out of the 120 servers with the updated nsclient, 10 of them are having issues with Windows Network checks, net_recv net_send net_tot. These three checks appear as unknown now. I have done a lot of googling and seemingly ever article says the issue is with windows counters. I have attempted to rebuild them, and believe i have followed the directions correctly, but no change. I can run the powershell command

Get-Counter -Counter '\Network Adapter(vmxnet3 Ethernet Adapter)\Bytes Received/sec'

and i receive data so the counters look good to me. However i am at a loss as to why i cannot get the network cards to work on these 10 systems. Outside of nsclient being uninstalled\installed there was no change to the systems.

I am hoping someone can help me out at least with stuff to look at, as i am at a loss right now. I have attached the ini file.

Re: PDH Counter no data received

Posted: Mon Jul 21, 2025 4:11 am
by sufferflashy
On one of the problem servers, open `services.msc` (Run -\> `services.msc`). Find the "NSClientpp" service. Right-click -\> `Properties` -\> `Logon` tab. Is it running as the `Local System Account`? Or a specific user account?
- If `Local System`: This account usually has broad permissions, but can still have problems sometimes.
- If Specific User Account: Make sure this user account is a member of the "Performance Monitor Users" group. Make sure this user account has read permissions to the relevant registry keys where the performance counter data is stored (although this is less common if `Get-Counter` works). Temporarily change the service to run as the local Administrator account (just to test, revert later) and restart the service. If the tests start working, then it is definitely a permissions issue.