Re: TCP Port selection
From: Steven L Umbach (sumbach_at_nospam-ameritech.net)
Date: 01/29/04
- Next message: S.Felmey: "Audit feature??"
- Previous message: mattc: "RE: Windows Update KB832483"
- In reply to: D Comeau: "TCP Port selection"
- Next in thread: Karl Levinson [x y] mvp: "Re: TCP Port selection"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 29 Jan 2004 20:11:39 GMT
I don't know of a way to do that [other than for rpc]. You should consider
using a stateful packet inspection firewall with a default block all
outbound rule and then configure just the exceptions for allowed
services/applications. A rule for internet access would have to allow return
traffic from any port, but only from traffic you intiated to port 80 tcp for
instance. It is the job of the firewall to track the "state" of the
connection so that uninitiated traffic from any other port or ip address is
not allowed in. --- Steve
http://www.netscreen.com/products/firewall/security/stateful_inspection.jsp
"D Comeau" <wysiwyg08620@yahoo.com> wrote in message
news:6b1b01c3e69e$5f15c7b0$a001280a@phx.gbl...
> Can I configure W2k to utilize a specific range of ports
> (or even restrict the use of a range of ports)? We have
> configured ACL's on our routers that restrict connections
> to dest ports 3127 to 3198 in an attempt to reduce the
> affects of the MyDoom worm. However, Windows randomly
> uses ports to connect to systems. As an example, I open
> my web browser to www.microsoft.com and I use TCP port
> 3127 as my source port, the packet goes out to
> www.microsoft.com port 80, but the return packet does not
> get through.
- Next message: S.Felmey: "Audit feature??"
- Previous message: mattc: "RE: Windows Update KB832483"
- In reply to: D Comeau: "TCP Port selection"
- Next in thread: Karl Levinson [x y] mvp: "Re: TCP Port selection"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
