After install, quarantine, reboot, no Internet

Discussion in 'ESET Smart Security' started by VarzilTheGood, Mar 12, 2009.

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

    VarzilTheGood Registered Member

    Joined:
    Mar 12, 2009
    Posts:
    5
    I installed ESS4 on an XP SP3 system. As soon as it finished installing it popped up to say it had detected a couple of bad files. The messages didn't stay on the screen, but I believe one filename was wsock3.dll. It asked to reboot and I said sure, why not.

    After reboot I got a little triangle-exclamation over the network icon in the tray, and I didn't have any connectivity. I tried to right-click and Repair, but the message was "Windows cannot finish... Renewing your IP address'.

    I followed the FAQ about disabling certain IDS elements, but that didn't help.

    I appreciate getting rid of a bad file :) but I'd rather not throw my Internet connection out along with it :'( . What to do??
     
  2. Kosak

    Kosak Registered Member

    Joined:
    Jul 25, 2007
    Posts:
    711
    Location:
    Slovakia
    Try to use this tool.
     
  3. VarzilTheGood

    VarzilTheGood Registered Member

    Joined:
    Mar 12, 2009
    Posts:
    5
    WinSockFix repaired the connection :D but broke ESET Smart Security 4! :'(

    It now says "No filtering mode defined. The Personal Firewall is malfunctioning. A computer restart may be required". I *did* restart, and the message didn't change.

    I went into Advanced settings and changed it from Automatic Mode to Interactive Mode, clicked OK, changed it back to Automatic Mode, clicked OK. I thought that might "shake loose" the problem. No joy. It is still *broken*.

    What do I use to fix the problem that the first solution created??
     
  4. Adramalech

    Adramalech Registered Member

    Joined:
    Apr 17, 2005
    Posts:
    79
    Winsockfix does a 'netsh IP reset' or similar. Repair ESSv4 and you should be good with.
     
  5. VarzilTheGood

    VarzilTheGood Registered Member

    Joined:
    Mar 12, 2009
    Posts:
    5
    This seems to be excellent advice. Except, what I'm asking is HOW to repair ESSv4.

    Oh, wait, it's in the Uninstall, I bet. Yeah!

    I ran a repair, rebooted, and the problem is NOT FIXED. :'( What next?
     
  6. Rmuffler

    Rmuffler Former Eset Moderator

    Joined:
    Jun 26, 2008
    Posts:
    995
    Location:
    San Diego, CA USA
    Hello VarzilTheGood,

    Please run a full uninstall and reinstall.

    Thank you,
    Richard
     
  7. VarzilTheGood

    VarzilTheGood Registered Member

    Joined:
    Mar 12, 2009
    Posts:
    5
    I did a full uninstall / reinstall and the problem with ESET firewall "broken" is fixed.

    I have the ORIGINAL problem again on a different machine. ESET cleaned it up but left it with no connectivity. I don't consider the solution that uses WinSockFix to fix the connectivity problem but break ESET as a good solution.

    Is there no way to *cleanly* recover connectivity after it's broken by collateral damage from ESET cleanup?
     
  8. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,032
    Location:
    California
    Hello,

    Can you take a look at the log file from the second computer and tell us exactly what was detected and removed from the system? Here's how to quickly view the log file:
    1. Open the ESET Smart Security from its icon in the system notification tray area, or by selecting Start → Programs → ESET → ESET Smart Security (menu item) → ESET Smart Security (program icon). The User Interface window will appear.
    2. In the User Interface window, press Ctrl+M to toggle the display into Advanced Mode.
    3. In the right pane, select the Tools option. The Tools screen will appear in the right pane.
    4. In the right pane, select Log Files and set the view to Detected Threats. The detected malware will be listed.
    5. Highlight the malware by single-clicking on it (use Shift + Click to select multiple entries, if there are any present), and then right-click on the entries and select Copy from the popup context menu.
    The information is now copied into your system clipboard, which you can paste into your reply by pressing Ctrl+V. This information will allow ESET's engineers to determine what sort of threat was found and give specific removal instructions.

    If you do not wish to wait, you can reset the network stack per the instructions in Microsoft Knowledgebase Article #299357, "How to reset Internet Protocol (TCP/IP) in Windows XP" (these instructions apply to newer versions as well, such as Windows Vista) to restore network connectivity.

    This may cause ESET Smart Security to lose the ability to scan the network connection, so it would be a good idea to perform a reboot afterward to let it reintegrate its components with the operating system. Alternately, you can try doing this manually through the following steps:
    1. Open ESET Smart Security following the instructions in step #1, above.
    2. Press the F5 key to open the Advanced Setup window.
    3. In the left navigation pane, select Antivirus and antispyware → Protocol Filtering and in the right pane toggle "Enable application protocol content filtering" off and then on again. Click on OK when finished.
    4. In the left navigation pane, select Personal firewall → System integration and in the right pane select "Personal firewall is completely disabled" followed by "All features active". Click on OK when finished.
    ESET Smart Security should now be reintegrated with the system.



    Regards,

    Aryeh Goretsky
     
  9. VarzilTheGood

    VarzilTheGood Registered Member

    Joined:
    Mar 12, 2009
    Posts:
    5
    I went straight to the Microsoft article and used the
    Code:
    netsh int ip reset resetlog.txt
    command, then rebooted. That didn't do it. But I followed a link from that article to determine and recover from winsock errors.
    Code:
    netsh winsock reset
    followed by reboot restored connectivity. Yay!

    Afterward I ran into a problem with the firewall. I tried the re-integration instructions you supplied but even after rebooting (and another reboot requested by ESET) I still got "Personal firewall rules could not be converted for an unknown reason".

    Fortunately I know how to handle this one as it happened on a different system. I will fix with a full uninstall and reinstall.
     
Thread Status:
Not open for further replies.