07-28-2023 02:21 AM - edited 07-28-2023 02:31 AM
Good day
I'm experiencing an issue where I'm receiving influx of alerts related to this netsh tool.
I got this arlticle and I was wondering if you can assist me in finding the cause of this behaviour.
10-24-2023 08:56 AM
I've noticed this too.
04-23-2024 08:38 AM
Has anyone found why this action takes place?
04-23-2024 09:13 AM
I opened a support ticket.
Per support this IS expected behavior.
04-23-2024 06:46 PM
Thanks for sharing @KenGutierrez , did they include any other details?
04-24-2024 10:01 AM
The explanation given was that netsh is a tool for troubleshooting built-in to MS. Said but not said was that if GP encountered an issue it triggers the usage of netsh in assisting the troubleshooting of the GP connection. In my case when the trace was triggered coincided with my rebooting of a firewall that I was GP connected to (remote firewall location). I was upgrading/patching my firewall and needed to reboot, this dropped my GP connection (as expected). Since GP saw that as an abnormal behavior (or error of some type) that triggered the netsh trace process. That is the best I can deduce as to why the trace action was taken - as I said all I received from support was that netsh usage is "expected" behavior. The rest was my deduction what was taking place at the time. Hope that helps someone else.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
