tshark or dumpcap affecting RDP session on Windows Server 2012R2
Has anyone encountered RDP performance issues while running tshark or dumpcap on a remote Windows 2012R2 server?
I have found lately that when I run a persistent tshark capture (or dumpcap), using out of band network ports, writing to a file ring buffer, the in-band RDP session that I use to administer the same server suffers from RDP issues to the point where, after some time passes, I need to reboot the server to regain control. All the while, the tshark session runs merrily along.
I hope I explained this well enough.
Today, for the first time, I am trying to run the tshark capture from within a bat file being called from a scheduled task so that I dont have to be logged into the server via RDP. So far, so good. Time will tell.
Thanks in advance.
John
What does
tshark --version
report about the version of WinPcap or Npcap with which it's running?Thanks for your response. Here is the output of that command:
(more)Npcap version 0.9991
npcap is currently at 0.9997 with fixes for memory use.
Example here of upgrade helping.
Also note that 3.2.6 is the current stable release.
Thanks guys... I'll give the new version a go and see how I make out.
Cheers.