Why am I getting masses of inbound traffic on prt 3522

  • Thread starter Thread starter Andy Bell
  • Start date Start date
A

Andy Bell

Ever since I installed my new firewall I seem to be getting a butt-load of
inbound TCP traffic blocked on port 3522. This doesn't seem to be mentioned
by any of the RCP worm bulletins (they talk about 135 & 4444) but could it
be the same thing?
Andy
 
Ever since I installed my new firewall I seem to be getting a butt-load of
inbound TCP traffic blocked on port 3522. This doesn't seem to be mentioned
by any of the RCP worm bulletins (they talk about 135 & 4444) but could it
be the same thing?
Click to expand...

3552 shows here as unassigned and not a trojan/worm port. Open your
firewall and create a rule to block port 3522 TCP inbound and see what
happens. That's what firewalls allow rule creation for.
 
Sorry you might have misread my post. My problem is 3522 rather than 3552
which is
coming up as "DistributedObjects over NSSocketPort" whatever that means...
Incidentally I noticed this on my firewall log as it is already being
blocked (~ once every 10s) as an "unrequested" inbound.
Andy
 
Sorry you might have misread my post. My problem is 3522 rather than 3552
which is
coming up as "DistributedObjects over NSSocketPort" whatever that means...
Incidentally I noticed this on my firewall log as it is already being
blocked (~ once every 10s) as an "unrequested" inbound.
Click to expand...

I did misread your post and for that I am sorry. Port 3522 is still
unassigned (dynamic) and used by the localhost (your system) when it
needs to do so. It is not a known trojan port and leave it to access
out but no inbound access. See what happens.
 
Back
Top