slow browsing

Discussion in 'ESET Smart Security v4 Beta Forum' started by s4u, Nov 18, 2008.

Thread Status:
Not open for further replies.
  1. cupez80

    cupez80 Registered Member

    Joined:
    Jun 28, 2005
    Posts:
    617
    Location:
    Surabaya Indonesia
    i got this error and its realated to FW... disable FW web browser doing fine
     
  2. silverflare

    silverflare Registered Member

    Joined:
    Jan 10, 2009
    Posts:
    1
    Solution for slow browsing and 404 / 403

    To everyone experiencing this sort of issue:

    Make sure your Network's Subnet (like when you are using a router) isn't marked as UNTRUSTED in Firewall -> Zone Settings.


    1. Switch to Display: "Advanced mode"
    2. Select "Setup".
    2. Select subcategory "Personal Firewall"
    3. Select "Advanced Personal Firewall setup"
    4. In the new Window select the subcategory "Rules and zones"
    5. In the section "Zone and rule editor" click "Setup"
    6. In the "Zone and rule setup"-Window click the TAB "Zones"
    7. Lookout in the list for the entry: "Networks automatically marked as untrusted", select it and click the "EDIT"-button on the bottom.
    8. Make sure your Network's Subnet isn't listed here (as it is by default for some).
    9. If it is -> Remove it and make an entry in "Trusted zone" insted.
    10. Your problems should be gone ;-)

    Greetings silverflare.

    €:

    I guess that was just another part of it, it's still happening but a bit more unfrequent.

    After investigating my log files I found three messages happening exactly right when all sites but a few (like wildersecurity.com) get blocked.

    10.01.2009 16:39:33 Detected TCP Flooding attack 192.168.178.1:1725 192.168.178.25:14013 TCP
    10.01.2009 16:28:00 Detected TCP Flooding attack 192.168.178.1:1626 192.168.178.25:14013 TCP
    10.01.2009 11:40:22 Detected TCP Flooding attack 192.168.178.1:4555 192.168.178.25:14013 TCP

    For information purpose:
    I'm behind an Fritz Box Router right now which has got the IP 192.168.178.1. Ah yeh, and I'm connected via WLAN.

    Now if i wait for a few minutes every site will work like before. Disabling the Web-Scan won't do anything here, just disabling the Firewall module - but after reenabling it's not gone ... you still have to wait for a few minutes.

    My personal guess:

    An missfunctioning blocking method which is part of the Personal Firewall module that might confuse the type of traffic which is comming trought or at least won't register that this is an Local Network Connection.
     
    Last edited: Jan 10, 2009
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.