Re: Question for Windows "security" experts

On Feb 14, 7:53 pm, Carl Banks <pavlovevide...@xxxxxxxxx> wrote:
On Feb 14, 7:07 pm, Va Beach Hokie <wjlm...@xxxxxxxxx> wrote:





On Feb 14, 6:59 pm, Carl Banks <pavlovevide...@xxxxxxxxx> wrote:

Not being a Windows expert, since I almost never use it (other than at
work where other people administer it), I have a question about
protecting my ports.

My current firewall solution is to disable my Ethernet adapter.  Which
heretofore has worked great for me.

Unfortunately, a case has come up where I will need a smidgen of
Internet access for the occasional instances when I boot into Windows.

I still want to completely block almost all ports, incoming and
outgoing.  The only outgoing connection that should be allowed is port
80, and then only to a specific IP address.  In particular, I want to
completely deny all of those automatic connections like Windows
Update.  I guess I'd also need the DHCP port open (whatever it is).
No incoming connections at all.

Just do exactly this,either in windows firewall or on your router.
Close all ports except 80, and define the specific IP address.
Shouldn't be too hard.

As I said the external firewall is not doable at the moment, otherwise
this question wouldn't even exist.

Windows Firewall (sic) doesn't give me control over that stuff, unless
there's some secret configuration file or advanced tab somewhere I'm
not aware of.  It doesn't appear to block outgoing connections at all,
nor does it specify specific IPs for incoming.  Plus forgive me if I
don't exactly trust Windows Firewall (sic) to block Windows Update
connections to microsoft.com.


For inbound stuff you can block all incoming traffic then create an
exception for individual programs, including specifying port and
address. At least, I can do this in Vista. My XP system is 250
miles away so I can't play with it right now.

For outbound, I'm not certain. Maybe something like ZoneAlarm, which
can block both directions. Is this a dual OS box? If so, I'd be way
outside my pay grade.
.

Relevant Pages

  • RPC Connection problems with XP Firewall, dispite proper exeptions
    ... So there seems to be a problem with DCOM or RPC over the Windows XP SP2 ... Windows Firewall: Allow local program exceptions ... If you enable this policy setting, Windows Firewall allows the computer to ... does not open TCP port 135 or 445. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: keeping ports open
    ... If a port is open, it means that 1) a software or service is running on your ... and 2) you're not using a firewall or your firewall isn't ... Use firewall software and hardware and antivirus software that is ... Follow the instructions for hardening Windows and IIS at ...
    (microsoft.public.security)
  • Re: Opening port 135
    ... Windows Server 2003 doesn't have built-in firewall. ... open port 135 on the firewall. ... This behavior occurs because Windows Firewall has blocked the request. ... Before you use this method try both Method 1 and Method 2 in the workaround ...
    (microsoft.public.windows.server.general)
  • [Full-Disclosure] ron1n phone home, episode 4
    ... Hacking from Windows 3.x, 95 and NT ... Use secret Windows 95 DOS commands to track down and port surf computers ... Download hacker tools such as port scanners and password crackers designed ... Now you have the option of eight TCP/IP utilities to play with: telnet, ...
    (Full-Disclosure)
  • Re: How to Maintain an IIS Server?
    ... > server running on a Windows 2000 server. ... before a firewall and antivirus have been installed]. ... open ports; however, this will not identify which program is using the port. ...
    (microsoft.public.inetserver.iis.security)