application filtering problem

Discussion in 'LnS English Forum' started by paolo_italy, Sep 16, 2008.

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

    paolo_italy Registered Member

    Joined:
    May 6, 2006
    Posts:
    13
    hi,
    my problem is with LnS 2.06 (17/05/2007) and the LnS window don't show and don't ask me anything.
    :oops:

    Help me please.

    Paolo
     
  2. Climenole

    Climenole Look 'n' Stop Expert

    Joined:
    Jun 3, 2005
    Posts:
    1,640
  3. paolo_italy

    paolo_italy Registered Member

    Joined:
    May 6, 2006
    Posts:
    13
    many thanks,
    but after upgrade i received error msg and application filtering don't work again.

    Bye
     

    Attached Files:

  4. Climenole

    Climenole Look 'n' Stop Expert

    Joined:
    Jun 3, 2005
    Posts:
    1,640
    Hi paolo_italy :)

    Check this article on the Official LnS FAQ:

    problems with driver remove

    Follow exactly the procedure.

    I suggest you to used this tools for Registry searching:
    RegSeeker

    - Check the backup option before
    - don't "clean" the registry but search with specific words
    such as LnS, lnsfw, S4E_LNS...

    I guess the best and easier solution for you is to make a clean install.

    Hope this help: let us know.

    :)
     
  5. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,354
    Location:
    France
    Hi paolo_italy

    This error indicates a problem in the registry which prevents the driver to run (and to be installed) properly.

    Actually it is the lnsfw1 driver, so what suggested Climenole will not help (because the mentioned procedure is for lnsfw driver).

    To identify the issue with the registry you should run the LoadOrder utility from Microsoft:
    http://technet.microsoft.com/en-us/sysinternals/bb897416.aspx

    Then highlight the PNP_TDI drivers like this:
    LoadOrder.JPG

    Thanks,

    Frederic
     
  6. Climenole

    Climenole Look 'n' Stop Expert

    Joined:
    Jun 3, 2005
    Posts:
    1,640
    Hi Frederic :)

    Oups !!! :oops:

    I hope paolo_italy will read your post before doing the "cleanup"...

    :blink:
     
  7. paolo_italy

    paolo_italy Registered Member

    Joined:
    May 6, 2006
    Posts:
    13
    Thank you to all,

    this is log:


    System PNP_TDI 31 lnsfw1
    System PNP_TDI 27* NetBT NetBios su Tcpip
    System PNP_TDI 26* Tcpip Driver protocollo TCP/IP

    Automatic PNP_TDI n/a* WS2IFSL Ambiente di supporto del provider del Servizio Non-IFS di Windows Socket 2.0


    Bye
     
  8. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,354
    Location:
    France
    The order must be:
    TcpIp
    Lnsfw1
    Netbt

    So probably the problem is coming from the bad order you have.

    This is configured through the registry with [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GroupOrderList] key and the PNP_TDI value.
    Could you export this key to a file, open it as a text file, and copy paste here, just the PNP_TDI value ?

    Did you install/remove another application related to the network ? It seems someone has broken this key.

    Regards,

    Frederic
     
  9. paolo_italy

    paolo_italy Registered Member

    Joined:
    May 6, 2006
    Posts:
    13
    "PNP_TDI"=hex:1e,00,00,00,02,00,00,00,1c,00,00,00,04,00,00,00,05,00,00,00,06,\
    00,00,00,07,00,00,00,08,00,00,00,09,00,00,00,0a,00,00,00,01,00,00,00,0b,00,\
    00,00,0c,00,00,00,0d,00,00,00,0e,00,00,00,0f,00,00,00,10,00,00,00,11,00,00,\
    00,12,00,00,00,13,00,00,00,14,00,00,00,15,00,00,00,16,00,00,00,17,00,00,00,\
    18,00,00,00,19,00,00,00,1d,00,00,00,1e,00,00,00,1f,00,00,00,20,00,00,00,21,\
    00,00,00


    thank you very much for your interest

    Paolo
     
  10. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,354
    Location:
    France
    The problem is the tags for TcpIp (26/1A) and NetBt (27/1B) are not in that list.
    This is also why there is a * in LoadOrder for these drivers (and it is not normal).

    You can try to fix that with the following entry (3 modifications in bold):
    "PNP_TDI"=hex:20,00,00,00,02,00,00,00,1c,00,00,00,04,00,00,00,05,00,00,00,06,\
    00,00,00,07,00,00,00,08,00,00,00,09,00,00,00,0a,00,00,00,01,00,00,00,0b,00,\
    00,00,0c,00,00,00,0d,00,00,00,0e,00,00,00,0f,00,00,00,10,00,00,00,11,00,00,\
    00,12,00,00,00,13,00,00,00,14,00,00,00,15,00,00,00,16,00,00,00,17,00,00,00,\
    18,00,00,00,19,00,00,00,1d,00,00,00,1e,00,00,00,1a,00,00,00,1f,00,00,00,1b,00,00,00,20,00,00,00,21,\
    00,00,00

    Modify the .reg file, and execute it, to have it written to the registry.

    Run again LoadOrder and you should get:

    System PNP_TDI 26 Tcpip Driver protocollo TCP/IP
    System PNP_TDI 31 lnsfw1
    System PNP_TDI 27 NetBT NetBios su Tcpip

    Then reboot, and normally the application filtering should be working again.

    Regards,

    Frederic
     
  11. paolo_italy

    paolo_italy Registered Member

    Joined:
    May 6, 2006
    Posts:
    13
    You've been fantastic
    I resolved

    :D

    I would give you a kiss but unfortunately I have "classic" taste

    :D

    See you soon

    Paolo
     
  12. Climenole

    Climenole Look 'n' Stop Expert

    Joined:
    Jun 3, 2005
    Posts:
    1,640
    Hi Frederic :)

    Wow ! You're a Genius! :eek: Thank you for these posts. I learned a lot today.

    :thumb:

    :)
     
  13. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,354
    Location:
    France
    Thanks Paolo and Climenole :)

    What I would like to know is how the registry could be corrupted that way o_O
    I don't think it is caused by Look 'n' Stop.

    Paolo, how the problem appeared exactly:
    1- just after the very first installation of Look 'n' Stop
    2- Look 'n' Stop was working properly for a while, and you installed/uninstalled some other application (or you used an uninstall tool, or you did a restoration) and then the Application Filtering stopped to work
    3- Look 'n' Stop was working properly for a while, and the problem appeared suddenly, with no special event that could be the cause of the issue

    Thanks,

    Frederic
     
  14. nuser

    nuser Registered Member

    Joined:
    May 31, 2007
    Posts:
    105
    Location:
    Singapore
    Hi, Frederic,
    1, what's the difference between lnsfw1 and lnsfw? (lnsfw1=TDI filter, lnsfw=NDIS filter?)
    2, in your snapshot, tcpip6 is loaded after lnsfw1. Does it mean that lns can't filter ipv6?
     
  15. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,354
    Location:
    France
    Hi nuser,
    Lnsfw1 is for the Application filtering.
    Lnsfw is for the Internet Filtering.
    This screenshot comes from an XP machine, and it is true the application filtering doesn't support IPV6 for XP but only for Vista (this is in the 2.06 changelog).
    Now, I'm not sure the reason it doesn't work for XP is simply the load order.

    Frederic
     
  16. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,354
    Location:
    France
    I've just checked that and it seems modifying the load order to have Tcpip6 driver loaded before lnsfw1 is finally sufficient to have an IPV6 connection detected by the application filtering (at least a "telnet IPV6@" was detected).

    Frederic
     
  17. nuser

    nuser Registered Member

    Joined:
    May 31, 2007
    Posts:
    105
    Location:
    Singapore
    Hi, Frederic,
    To rearrange the load order of drivers, is the only way to manually reset the registry entries? Seems Loadorder can only display the loading order, not resetting.

    In Loadorder, I don't find lnsfw.sys, only lnssvc.exe. Is this normal?

    thanks:)
     
  18. Frederic

    Frederic LnS Developer

    Joined:
    Jan 9, 2003
    Posts:
    4,354
    Location:
    France
    Yes, this is the only way I know. Maybe some applications are doing that, but I don't know them.
    Yes, LoadOrder just reads the registry and shows the driver order in a friendly way.
    I don't know why the other driver (note that the registry key is "SFilter" instead of lnsfw) is not in that list.
    Since all entries from [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services] are not there, probably LoadOrder is using another information.

    Frederic
     
  19. paolo_italy

    paolo_italy Registered Member

    Joined:
    May 6, 2006
    Posts:
    13

    The problem has been since the first installation but had given no weight
     
  20. paolo_italy

    paolo_italy Registered Member

    Joined:
    May 6, 2006
    Posts:
    13
    Bye, Paolo
     
Thread Status:
Not open for further replies.