Re: TCP traffic to port 16882
From: JED (res1emv4_nospam__at_verizon.net)
Date: 03/02/04
- Next message: JED: "Re: how to create 'allow destination unreachable' in Sonicwall"
- Previous message: Frank van Meurs: "Re: Tiny Personal Firewall - which version?"
- Next in thread: Torsten Brasch: "Re: TCP traffic to port 16882"
- Reply: Torsten Brasch: "Re: TCP traffic to port 16882"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 01 Mar 2004 23:37:04 GMT
> This goes on and on, dozens of entries per hour. You can see the
timestamps
> on the above examples.
> So I found myself wondering what all this traffic to port 16882 is about.
I
> first thought it might be caused by some software running on one of my
> machines. But even if no machine is up, I still get all this traffic.
>
> Any idea, what that is all about?
Infected computers on the web sending out worms/trojans/viruses/nasties (?)
We are getting a load of pings from different computers (forget now which
worm is responsible.)
What kills me is how many computers around my local commumity (not to
mention the entire web) have no protection. Was talking to a woman who runs
a local health food store and she told me she has no firewall (what's a
firewall?) but DOES have Norton's Anti Virus.
"Ever run NAV", I asked?
"Sure"
"What was the results"?
"Oh, it found so many things I knew that I figured that it was finding good
things too, and because I didn't know what was good or bad, I figured I had
better not delete anything."
<heh>
Just checked my log and the autitor showed 216 hits to port 135 in the last
hour. Also taking hits on 445
You can find a listing of known Trojans and the ports they atrtack at
http://www.simovits.com/sve/nyhetsarkiv/1999/nyheter9902.html
16882 isn't listed however, but it's probably out-of-date anyways.
- Next message: JED: "Re: how to create 'allow destination unreachable' in Sonicwall"
- Previous message: Frank van Meurs: "Re: Tiny Personal Firewall - which version?"
- Next in thread: Torsten Brasch: "Re: TCP traffic to port 16882"
- Reply: Torsten Brasch: "Re: TCP traffic to port 16882"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|