Re: Probes on Port 135 and 445 continue

From: Bernd Felsche (bernie_at_innovative.iinet.net.au)
Date: 10/14/04 

Date: Thu, 14 Oct 2004 13:42:05 +0800

Greg Mortensen <thevision@pobox.com> writes:

>In <MPG.1bd78090e19d9f6798985b@news-server.columbus.rr.com> Leythos <void@nowhere.org> writes:

>>The box blocks all inbound unsolicited and the
>>following outbound ports 135,136,137,138,139,444,1433,1434,2500 and not
>>one of the ladies has complained about anything not working.

> ...and 1433, 1434, and 2500 are all valid ephemeral ports. What happens
>when their web/mail/whatever client legitimately tries to use port 1433?

I've not had substantial complaints when blocking all outbounds
ports up to 10000.

OK; some of the owned PCs started running at a crawl... but for most
users the transparent proxying of HTTP(S) and insistence that the
mail server be used to sanitise and relay outbound works without a
hitch. The only thing they notice is that they get downloads much
more quickly on average; and the virus alert software on their PC
doesn't complain every few seconds. 

-- 
/"\ Bernd Felsche - Innovative Reckoning, Perth, Western Australia
\ /  ASCII ribbon campaign | I'm a .signature virus!
 X   against HTML mail     | Copy me into your ~/.signature
/ \  and postings          | to help me spread!

Relevant Pages

  • Re: Probes on Port 135 and 445 continue
    ... >>following outbound ports 135,136,137,138,139,444,1433,1434,2500 and not ... I've not had substantial complaints when blocking all outbounds ... mail server be used to sanitise and relay outbound works without a ...
    (comp.security.misc)
  • Re: Unable to use RWW with new Fortigate 50B appliance
    ... All outbound traffic is unrestricted, I will begin locking down once I have ... can RDP directly to port 3389. ... outbound ports, you need to allow port 4125 for RWW-RDP to work. ... desktop or server it wont let me, gives an error "The client could not ...
    (microsoft.public.windows.server.sbs)