I just logged an outbound attempt from Utor (haven't ran it in weeks)

[seedUpsy]

Hey,

Utorrent just attempted to connect twice in a row while it was closed (last ran it 16 days ago). UDP out to to 53 (dns) but why?

Auto update is off so what gives here? Why is a closed app calling out?

Thanks in advance,

s u p

[jewelisheaven]

... DNS ? If there's no process running it can't make calls

[Firon]

your firewall is dumb and doesn't do anything but detect a port being in use. an incoming DHT packet hit you with that as their port.

[seedUpsy]

@jewel:

See, that's just it; it wasn't running.

The packet(s) was from pc's static ip port 1690 (2nd was 1691) to my dns server.

Log shows app as utorrent.exe, logo and all.

A quick netstat showed nothing on those ports.

I had no applications running.

[jewelisheaven]

If uT isn't running it can't be sending the data...receiving sure, like Firon said it could have been data for a DHT hash ping or whatnot.

[seedUpsy]

Strangest thing I've seen in a while...

Also - for the record - the packet was out-bound, there is no doubt. I was fully locked-down behind my router when it happened:no traffic could have even made it in to be blocked in the first place.

I'll admit it doesn't make sense (if I hadn't seen it myself I would not likely believe it either) but I still logged it, and no one was here to generate it.

I just noticed, and was surprised to see, that the comment:

"your firewall is dumb and doesn't do anything but detect a port being in use." is not only incorrect, it is the type of response I'd expect from a troll - not an Admin.