I did as said: made sure that svchost.exe (and system) are set to allow, then I set the alert level to very high. I let the pc run for some time with out doing any thing, and still it got disconnected. I did this twice (see alert logs disconnect1+2.html).
I then set the “do not show any alerts for the application certified by COMODO” and did “scan for known applications” I restarted COMODO, but still I got disconnected (see disconnect3.html)
I’m using a cable modem, with PPTP VPN. My ISP IP is 172.26.255.17. On this session I received IP 172.25.137.141
Welcome to the forums! It looks like your cable ISP is using a GRE protocol as part of maintaining your active connection. By default, GRE is blocked by the Network Monitor. Thus, their attempt to contact you (whatever that may be) is being blocked; I would guess that after a period of inactivity this causes a disconnect.
I say this because there’s a lot of blocks on Incoming GRE from 172.26.255.17 to the session IP you gave. GRE could go out (with default rules) but not in.
You may want to try adding this rule to the Network Monitor. Right-click on the bottom Block & Log IP In/Out rule, select Add/Add Before. In the rules dialog box, create as follows:
Source IP: Single IP: 172.26.255.17
Destination IP: Any
IP Details: GRE
Click OK. A reboot may be helpful to clear the memory and set the new rule. IF that IP address doesn’t remain constant, you’ll have to find out what Range of IP addresses your ISP uses for this purpose, and then set the Source IP to a Range instead of Single IP.