Nod Proxy Quit Working After CHKDSK

Discussion in 'ESET NOD32 Antivirus' started by Shelty, Feb 10, 2008.

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

    Shelty Registered Member

    Joined:
    Oct 28, 2007
    Posts:
    41
    Nod's proxy quit working after a reboot from CHKDSK. The only reason I noticed it is because Thunderbird has been working through the proxy and then all of a sudden Online Armor asked for access to port 110. Ekrn.exe was not listed in the firewall status as listening on port 30606.

    After another reboot, the proxy seemed to start working again. I checked to make sure all of Nod's settings were the same and did not notice anything that had changed.

    If I didn't have Online Armor popping up asking for access on port 110. I would have never noticed that the proxy was not working.

    Has anyone else noticed this? All is well for now.
     
Thread Status:
Not open for further replies.