Hello, to all...
Hopefully a technical answer will come from this...
I have been a regular user of TeamV since v.7 - all family and friends remote work helping them.
I love the functions and tools, the layout, ease of use and much more, what a pgm, hats off to the designers...but I have noticed something peculiar lately when booting up my PC, and I probably wouldn't have noticed it if I didn't have my external speakers plugged in. What I hear through my speakers is a LAN signal coming from my PC yet emitting a 5 pulse, tick, tick, tick, tick, tick then a 6 second pause then it repeats.
First thing I thought was my speakers must be the issue, going bad, cable issue, whatever...but then it dawned on me it was a signal so I opened tskmgr to see if anything out of the norm was running.
This prompted me to run CP as Admin and do a simple "netstat -ano" to see what if anything was connecting.
2 things are running an established connection each time after I boot - explorer.exe which is normal for Win8, and TeamV.
Well I know from past experimenting if you kill the process of explorer.exe Poof! it shuts everything down, so this leaves good old TeamV to kill. So I kill the process and TeamV is gone, but count to 5 and there it is again, back in tskmgr.
Kill it again and count to 5 and there it is again. Only after the 3rd attempt will it completely be gone.
So back to CP - copy the IP - I did the standard trace on 2 sites "whois" and "IP Address Hostname Lookup" - Ripe.net comes up with "whois" and the Hostname leads back to TeamV. My question is, why is TeamV calling home?
I know something is being sent from TeamV as I see in Tskmgr memory usage is up from normal idle by 5,000k and jumps up and down - avg for TeamV 18,040k while the cpu jumps from 00 to 01, 02 then back to 00...as if it were sending small blocks of data intermittently.
Now I know what you are thinking, yes I got my original version of TeamV from the home site. I allow updates when asked so I know each new version is from the source and secure.
I do not allow anything but Google chrome through my firewall and that's only because they wrote a code that turns its self back on anytime their browser is ran or opened, I got tired of fighting them. I have numerous inbound and outbound rules set up for all pgms running in my O/S including TeamV. All pgms have been deleted in my firewall and rules set blocking everything. I allow nothing to call home and prompted if anything tries.
Now I am not trying to make a big thing out of this, but after allowing TeamV to call out just to see how long it would run (btw: 30 to 45 min) has me puzzled. This duration rules out my theory that it could be Team's protocol of establishing a connection for readiness or quickness when the pgm is called upon.
I am curious if anyone else has noticed the same behavior or be willing to run a few tests on their own rig and report their findings here? I still love and plan to use Team, dam I would be sad if I couldn't I think, I just want to make sense of what this is...
Sorry if this Question is out of the norm for this Board.
Thanks in advance for any insight and your findings...
DBOBA
