New version 2.05b2

I'm going to go back to 2.05b1, check everything works there, and then un-install and install 2.05b2 again.

Watch this space!

 

Hello,

Thanks Phant0m`` for letting me know about this thread. I've the same problem. I read whole thread and followed all steps. Tried deleting and adding (of course I rebooted every time - delete - reboot - add/allow - reboot) and replacing the driver with the open Frederic uploaded and DNS resolution is still not working on my system.

I hope something can be done about this.

regards,

richter

 

Yea, you can be sure Frederic will have this fixed ASAP!

 

I certainly hope so. It's a small glitch, I'm glad it's being fixed right away. Other than this, things seem to be working fine.

 

I've run into a problem.

Unistalled b2, resinstalled b1 but it will not run, I get an error 'unable to load lnsfw driver (error 0)

 

You probably re-installed without rebooting after the uninstall.
Try the following:
- uninstall again
- reboot
- install again

Frederic

 

Hey aptisman

Please see http://www.wilderssecurity.info/0306.shtml

 

Did you delete lnsfw.sys and lnsfw1.sys from windows\system32\drivers directory after uninstalling and before installing beta 1? *In case they were left out after uninstall*

 

Could you try to verify the problem disappears if you start Look 'n' Stop after the PC is connected to Internet ?
To test that simply do the following:
- your PC is connected
- Enable the Protocol checking in Look 'n' Stop
- quit Look 'n' Stop
- restart Look 'n' Stop
- in the welcome Tab the "Connected To internet" checkbox should be checked
- does it work ?

If yes, I think I found where is the issue.

Frederic

 

Hello,

I did as you said and it says I'm connected to Internet and it shows my IP address, but I still cannot browse or do anything while Protocol filtering is enabled. Sorry.

 

Yes, I think I forgot to re-boot!

Now back to 2.05b1, Protocol Filtering is enabled and everything is working again.

Do you want me to uninstall and reinstall b2?

 

Not needed at this time.

I will investigate further and come back with new suggestions.

Thanks for your patience

Frederic

 

I have the same problem with protocol filtering when its enabled in the new beta 2. By the way, I am on WinXP pro.

 

I don't understand why i haven't it so, all works well, is it a bug

 

Does your connection use WANARP.SYS?

 

It is possible to reproduce the issue without having Wanarp, by using the MBTest leaktest.
By default Look 'n' Stop blocks NPF.SYS, this works, but if you try to allow it and restart MBTest, NPF.SYS is still blocked (like for Wanarp).

So normally I should be able to find a fix quickly.

Frederic

 

Hey Frederic

I didn't use MBTest but i did use something else that uses that Protocol Driver, and i have no problems on my end.

 

No.

@Frederic

Exactly Fredric, i have tried and even by allowing NPF.SYS, MBtest is still blocked.

 

NPF.SYS shouldn’t be in continuous use unless you using Application that uses that Protocol Driver like mbtest, gkweb have you tried closing out of mbtest and pausing for a minute and go into Protocol filtering configurations and manually removing that Protocol and click OK button, then back into Protocol filtering configurations and manually add “NPF.SYS” into the field and click “Add” & “OK” buttons and re-doing that mbtest…?

 

Hi again

You said "I found the cause to be when Adding/Removing a Protocol Driver to/from the list when the Protocol Driver has continues activity, it will not apply until Protocol Driver refreshes. So for those who internet depends on WANARP.SYS Protocol Driver, when you see “Protocol” alerts in Look ‘n’ Stop Log screen, go into Protocol Filtering configurations and select line containing “WANARP.SYS” and click “Allow” & "OK" buttons. Now disable the Internet, Go into your "Local Area Connection Status" and in General TAB click "Disable". Re-boot the Computer and after Look ‘n’ Stop fully Loads then “Enable” your Internet again."

I'm lost from "Go into your 'Local Area Connection Status' - I don't seem to have one that's active!

 

What Windows ver you using?

And you using Dial-up? if not what connection type you use?

 

Dial-up on XP Home

 

After Microsoft Windows boots up, and Look 'n' Stop fully loads and before dialing a Connection goto Look 'n' Stop Protocol Filtering configurations and manually add WANARP.SYS by inserting that into blank and clicking "Add" button and then click "Allow" & "OK" buttons.

If there is already WANARP.SYS entry, delete and do the above, after doing these steps then Dial a Connection.

 

still blocked doing like that.

And regarding what you said, *I* need to use NPF.SYS at least for leaktest purpose

 

You meaning to tell me that you have leaktest programs running in the background continuously holding up that Protocol Driver?

I believe not....