Docking@home pinging proxy servers the world over?

[Canai]

Alright, I'm really not sure about this at all, but since I switched from rosetta@home to docking@home, peerguardian is blocking a ton (>500/day) of connection attempts from my comp to proxy servers, mostly hosted at universities, but some public as well. Even though the connections are blocked on my end, docking@home has no problem reporting results.

The destination port is always 8080, origin port starts low and goes up by one after three blocked connections. Does docking@home (or BOINC) do anything like that?

I really hope it's d@h, otherwise there's a trojan or something hiding away somewhere. I've done full scans and looked for anything else out of the ordinary, but nothing's come up.


Update: It was adblock filterset G doing it. No idea why, couldn't find any info on it other than one person who posted something a month ago in the reviews on firefox's addons page. No info in their forums about it either.

Oh well, I'm glad it wasn't BOINC 🙂

 

[Fardringle]

Suspend BOINC (or stop the BOINC service) and see if the connection attempts stop as well.

 

[RaySun2Be]

Almost sounds like you are running the DIMES DC project but I don't think it is a BOINC project.

But I agree with what Fardringle suggests. Stop the BOINC project and see if the connection attempts continue.

 

[Canai]

The attempts do stop when BOINC is halted or not running, which is one of the reasons I think it may be BOINC related. Also, since switching to docking@home, BOINC automatically starts crunching when the comp starts, even if I don't launch BOINC, so I don't know if that's just a new feature or if I just never noticed it before.