Imon.dll files missing?

Discussion in 'NOD32 Early v2 Beta' started by hayc59, Jun 1, 2003.

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

    hayc59 Guest

    i ran 'start up list' and came up with this at the end of
    the report--------->

    anyone have any ideas?? thanks
     
  2. Pieter_Arntz

    Pieter_Arntz Spyware Veteran

    Joined:
    Apr 27, 2002
    Posts:
    13,330
    Location:
    Netherlands
    Hi hayc59,

    Have a look here: http://www.wilderssecurity.com/showthread.php?t=8137;start=msg54374#msg54374

    And you know how to check if this information from HijackThis is correct using either LSPFix and/or AdAware 6. :)

    Regards,

    Pieter
     
  3. hayc59

    hayc59 Guest

    just did an Eicar test to my Outlook and here are the results...so it must be working ok!? right? :D
     

    Attached Files:

  4. Pieter_Arntz

    Pieter_Arntz Spyware Veteran

    Joined:
    Apr 27, 2002
    Posts:
    13,330
    Location:
    Netherlands
    Right!! :)

    Could you download the latest version of HijackThis log
    and check if it still shows this glitch.
    If it does I will point Merijn (Author of HijackThis and StartupList) to this thread.

    Regards,

    Pieter
     
  5. Longthing

    Longthing Registered Member

    Joined:
    Jul 27, 2002
    Posts:
    40
    The HijackThis log shows here the following:

    O10 - Broken Internet access because of LSP provider 'imon.dll' missing
     
  6. hayc59

    hayc59 Guest

    here is the results of HiJackThis--->
     

    Attached Files:

    • jack.jpg
      jack.jpg
      File size:
      97.2 KB
      Views:
      1,611
  7. Andreas1

    Andreas1 Security Expert

    Joined:
    Jan 29, 2003
    Posts:
    367
    Location:
    Mainz (Ger)
    Hi all,
    i have got these alerts, too. But i have been going along fairly well just ignoring them. NOD v2 features some LSP checking of its own and i suspect that this has to do with it. (All of the LSP checking tools indicate that there's a problem, but in fact i haven't experienced one.)
    Any other experiences?
    CU,
    Andreas
     
  8. Longthing

    Longthing Registered Member

    Joined:
    Jul 27, 2002
    Posts:
    40
    All works fine here as well.
     
  9. Pieter_Arntz

    Pieter_Arntz Spyware Veteran

    Joined:
    Apr 27, 2002
    Posts:
    13,330
    Location:
    Netherlands
    I alerted Merijn to this thread.

    hayc59, could you check if these are correctly interpreted by the LSP Explorer in AdAware 6?
    As a kind of a third opinion.

    Regards,

    Pieter
     
  10. Merijn

    Merijn Guest

    The problem stems probably from the file path not being included in the LSP stack. Thus, HijackThis and StartupList look in their own directory for imon.dll and won't find it. Normal LSP providers have a complete path to the file in the Registry.

    I won't be here this week (7 days off starting tuesday) but a way to confirm this is the problem would be running HT or SL from the same folder imon.dll is in. But I see people on Wilders have already added the item to the ignorelist, so no real harm done :)
     
  11. hayc59

    hayc59 Guest

    here is the results of my check..
     

    Attached Files:

    • Lsp2.jpg
      Lsp2.jpg
      File size:
      63.7 KB
      Views:
      1,610
  12. hayc59

    hayc59 Guest

    and number 2
     

    Attached Files:

    • LSP.jpg
      LSP.jpg
      File size:
      61.6 KB
      Views:
      1,610
  13. Pieter_Arntz

    Pieter_Arntz Spyware Veteran

    Joined:
    Apr 27, 2002
    Posts:
    13,330
    Location:
    Netherlands
    That would confirm what Merijn is saying.
    If you compare your first screenshot with mine, you´ll see that for the Port Explorer dll the entire path is displayed, where for imon.dll only the filename is displayed. That would put HijackThis on the wrong track as Merijn explained.

    Regards,

    Pieter
     

    Attached Files:

  14. hayc59

    hayc59 Guest

    so i have no worries at all! thanks Merijn and Pieter
    for all your wisdom.... :D :D
     
Thread Status:
Not open for further replies.