Long pings/(traffic?) cause system wide network latency until app is restarted

Comodo Internet Security - CIS Resolved/Outdated Issues - CIS
1

I have 3 windows 7 64bit ultimate pcs, 2 of them run CIS 64bit the other does not. I can reproduce this problem on both that run Comodo:

If I leave a ping.exe running for a few hours, I see my latency climb at a steady pace, after about 5 hours it’ll be 8ms higher, overnight I’ve seen it as high as 25ms higher (pinging a node on my LAN)

It also causes weird issues with other apps, firefox will hang, my iscsi devices will drop off, etc.

Some diagnostic tools that I’ve been playing with and other interesting findings:

Using the pscx 1.2 powershell addon, I can reproduce this in a matter of a few minutes:
PS C:> ping-host -Count 10000000 192.168.1.1
Reply from 192.168.1.1 bytes=32 time=0ms TTL=62
Reply from 192.168.1.1 bytes=32 time=0ms TTL=62
Reply from 192.168.1.1 bytes=32 time=0ms TTL=62
Reply from 192.168.1.1 bytes=32 time=0ms TTL=62
… …
Reply from 192.168.1.1 bytes=32 time=16ms TTL=62
Reply from 192.168.1.1 bytes=32 time=16ms TTL=62
Reply from 192.168.1.1 bytes=32 time=16ms TTL=62
Reply from 192.168.1.1 bytes=32 time=17ms TTL=62
(here I hit ^C and up->enter to restart the command)
PS C:> ping-host -Count 10000000 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1 bytes=32 time=17ms TTL=62
Reply from 192.168.1.1 bytes=32 time=17ms TTL=62
Reply from 192.168.1.1 bytes=32 time=16ms TTL=62
Reply from 192.168.1.1 bytes=32 time=16ms TTL=62
Reply from 192.168.1.1 bytes=32 time=16ms TTL=62
…

I open a dos window:

C:>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=16ms TTL=62
Reply from 192.168.1.1: bytes=32 time=17ms TTL=62
Reply from 192.168.1.1: bytes=32 time=17ms TTL=62
Reply from 192.168.1.1: bytes=32 time=17ms TTL=62

As you can see as long as powershell open it adds this latency to all apps, now when I run a ping -t and then close powershell you’ll instantly see the latency drop even though powershell is doing nothing:

C:>ping 192.168.1.1 -t

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=17ms TTL=62
Reply from 192.168.1.1: bytes=32 time=17ms TTL=62
Reply from 192.168.1.1: bytes=32 time=17ms TTL=62
Reply from 192.168.1.1: bytes=32 time=17ms TTL=62
Reply from 192.168.1.1: bytes=32 time=17ms TTL=62
Reply from 192.168.1.1: bytes=32 time<1ms TTL=62
Reply from 192.168.1.1: bytes=32 time<1ms TTL=62
Reply from 192.168.1.1: bytes=32 time<1ms TTL=62
Reply from 192.168.1.1: bytes=32 time<1ms TTL=62
Reply from 192.168.1.1: bytes=32 time<1ms TTL=62

Ping statistics for 192.168.1.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 17ms, Average = 8ms
Control-C
^C
C:>

I can reproduce this using ping.exe, powershell, and cping.exe from colosoft

I’m running CIS 3.13.126709.581 / virus 3717
on windows 7 64bit - clean install of CIS (no upgrade)

2

Since you seem very technical. Does the increase in ping time correlate to an increase in the amount of Deferred Procedure Calls?

3

It’s hard to say, a couple of apps are slow to start, but non-socket apps seem to be fairly unaffected.