Re: Firewall for use with AOL

From: JonBoy (No_at_invalid.jp)
Date: 08/19/03

  • Next message: optikl: "Re: Firewall for use with AOL" 
    Date: 19 Aug 2003 02:12:29 GMT

    "optikl" <optikl@comcast.net> wrote in
    news:JEe0b.184732$Ho3.25305@sccrnsc03:

    >
    > "JonBoy" <No@invalid.jp> wrote in message
    > news:Xns93DC93439E6BJONxxx@130.133.1.4...
    >> Please can anyone help with answers to the following:
    >>
    >> Does the Windows XP ICF work OK with AOL 8.0?
    >>
    >> Which software firewall(s) are compatible with AOL 8.0?
    >>
    >> JB
    >
    > Why would you think some would not be? Sygate, Kerio and Outpost
    > can all be made to work with AOL, quite easily. I suspect the
    > same is true of Look n' Stop and NPF and others.
    >

    Test results:

    1) Dial a non-AOL ISP with ICF switched on. A Shields Up! scan from grc.com
    shows all tested ports 'stealthed' and no ping responses. Result as expected.

    2) Repeat that test after dialing AOL with ICF switched on and I get:

    Results from scan of ports: 0, 21, 23, 25, 79, 80, 110, 113,
                                119, 135, 139, 143, 389, 443, 445,
                                1002, 1024-1030, 1720, 5000

        2 Ports Open
       20 Ports Closed
        3 Ports Stealth
    ---------------------
       25 Ports Tested

    Ports found to be OPEN were: 1025, 5000

    Ports found to be STEALTH were: 135, 139, 445

    Other than what is listed above, all ports are CLOSED.

    TruStealth: FAILED - NOT all tested ports were STEALTH,
                       - NO unsolicited packets were received,
                       - A PING REPLY (ICMP Echo) WAS RECEIVED.

    3) When I tried Sygate Personal Firewall with ICF switched off, dialling AOL,
    showed ports 1025 and 5000 were still open, the remainder were stealthed, and
    no ping reply was received. Better but still not as expected.

    How can a firewall designed to block inbound connections be working yet there
    be inbound ports openable?

    When you say "...can be made to work..." have you actually checked they are
    blocking the inbound ports. Or do you mean they don't crash or report errors?

  • Next message: optikl: "Re: Firewall for use with AOL"

    Relevant Pages

    • Re: Pings and firewalls
      ... Stealth is good as long as you're behind a router because the unsolicited ... The more important thing is that ports are *closed* not that the ... I have the ICF to work on the laptop when I'm on a wi-fi ...
      (comp.security.firewalls)
    • Re: Firewall now has numerous ports???
      ... >connected/listening. ... >> My ICF on XP show about nine ports. ... all email and internet has slowed to a crawl ...
      (microsoft.public.windowsxp.security_admin)
    • Re: Blocking Instant Messaging Programs
      ... > I am trying to block the use of AOL Instant Messenger, MSN Messenger, ... > thing applies to web based email (Hotmail, Yahoo, AOL, Gmail, etc). ... Does anyone know these ports or port ranges or where I ...
      (microsoft.public.isaserver)
    • Re: Cannot Disable Firewall in XP Home
      ... was hard to enable ICF in the first place. ... problems with AOL and thought it might be related to ICF. ... >Of course, if you have such a connection, your built-in ...
      (microsoft.public.windowsxp.security_admin)
    • Re: How to disable the built in firewall
      ... All of my experiences supporting customers' PCs with AOL ... ICS and ICF rely upon being able to adjust the properties of said ... connectoid. ...
      (microsoft.public.windowsxp.security_admin)
    • Quantcast