IE Blocking - Is this slowing me down?

  • Outpost 2.1 log reporting an outbound request being refused at just about every web site I visit as follows:

    App: iexplore.exe,
    Protocol: TCP
    Direction: OUT REFUSED
    Remote Host: www.outpostfirewall.com (site could be anywhere)
    Remote Port: HTTP
    Reason: Packet to closed port
    Local Host:192.168.0.*
    Local Port: 4365

    This seems to occur about every five seconds, but always with a different local port number in the range 3000 - 5000

    Surfing seems to have slowed over the days/weeks since I set OP up with the recommended configuration.

    On every request from OP to create a setting for IExplore I have accepted its recommendation.

    Running OP .21 build 304, XP pro SP1 up to date

    Any clues?


  • Hi David

    No remote hosts in rules, but Activate Stateful Inspection is listed in the FTP rule. As I say, I have only used the rules OP has asked me to set.


  • I'd agree with Manny here - it would appear that IE is attempting multiple connections and an "unwanted passenger" could certainly have this effect. Also make sure that IE is fully patched.


  • Hi Joe,

    It is a little confusing to me why 'Packet to Closed Port' would be the reason for a blocked Outbound connection unless for some reason the remote host (web site) was having a problem. Even then, I am unsure that this should happen with an Outbound connection.

    In the case of FTP, it is correct to have stateful inspection activated.

    Unless you feel that there is the potential for some sort of malware (trojan, worm, virus, etc.) being on your system, I would not let this bother me. A virus and trojan scan should put your mind at ease in this case.


  • A parasite seems likely to me. It looks like it's trying to connect offsite using IE. I presume the sites are not ones you are trying to connect with. The reason for the block is puzzling but I suggest you check for parasites: The Parasite Fight! (http://aumha.org/a/parasite.htm)


  • Hi Joe,

    In the case of an Outbound connection, don't give any consideration to the Local Port. Generally Outound connections will be on a local port above 1023 and a remote port that matches the service being accessed on the remote host. For web servers, that would be port 80.

    Are you using the preset (common rules) for IE? Hopefully you are not specifying remote hosts or using stateful inspection in any of your IE rules. Those are a few things to look at.

    I have to go for the moment, but there are a lot of others online at the moment who can pick this issue up.

    Have a good day. :)







    • #If you have any other info about this subject , Please add it free.#
    Your name:
    E-mail:
    Telphone:

    Your comments:


    If you have any other info about IE Blocking - Is this slowing me down? , Please add it free.

    5 January 2009 | cameltoepants.com | edit