New version 2.05b2

Hi

Got a problem with this here.

The log is full of 'Protocols' and I had to go to Advanced Options and disable Protocols otherwise I could not get out anywhere.

This is on Dial-Up and XP Home.

 

Hi,

Could you open the Console, clic on Driver Logs, and tell us what is the blocked protocol ?

Did you update from 2.05b1 (and you didn't have this problem before) or is it a fresh install ?

Thanks,

Frederic

 

Hey aptisman

By Default WANARP.SYS is detected and configured to block, you must Allow manually…

 

Yes, it's WANARP.SYS which is showing as blocked in the Console, although it's shown as allowed under 'Advanced Options/Protocols'.

Phantom, how do I allow it manually please?

 

Sorry, I should have said I did upgrade from 2.05b1 and I did not have this problem before.

 

Goto Protocol Filtering settings and select that Protocol Driver and click BLOCK, apply and go back and now "Allow".

 

Hey aptisman

Yea it seems to be minor problem we overlooked, upgrading over the existing somehow reset the Protocol Driver choices

 

Thanks Phantom, I have done that, I think correctly, but it has not helped. Nothing is resolving with Protocols enabled.

 

Hey aptisman

Try deleting that driver from the list, and try to surf, go back and authorize that driver which should be placed back into the Protocol filtering list.

 

Deleted it, tried to surf but it did not re-appear in the list.

I added it back manually but that did not help either!

 

Delete it from the list, re-boot the machine.

Normally when a newly Protocol Driver becomes detected it automatically adds with a Block, In Internet Filtering screen you should see indications with "Protocol" alerts.

 

Re-booted and it's back in the list. Allowed it but no joy, still nothing resolving with Protocols enabled.

 

Disabling Protocol Filtering Feature, does this fix the problem? In Look 'n' Stop Internet Filtering screen do you see "Protocol" alerts?

In Welcome screen, what you see for "IP Address:" ?

 

Yes, disabling Protocol Filtering fixes the problem.

Not sure what you mean 'do I see Protocol alerts in Internet Filtering screen, sorry.

IP address in Welcome screen is 213.104.224.62

 

Hey aptisman

Perhaps if you Enable Protocol Filtering and click Allow for that Protocol Driver and re-boot the machine, perhaps that’ll fix?

 

No, nothing works with Protocol Filtering enabled. It did under 2.05b1!

I'm using your Sept 9th Ruleset by the way.

 

How many things are listed in Protocol Filtering?   
And do they all show being allowed?

 

WANARP.SYS
NETBT.SYS
TCPIP.SYS

All allowed, all active, the latter two with a * against Yes.

 

Hey

OK I GIVE UP! LOL

Uninstall and Install v2.05b1 or use v2.05b2 and disable Protocol Filtering Feature and wait for a Fix!

 

Ok

Thanks for your help meanwhile!

 

LOL sorry, guess there really isn’t much else I can think of…

Me I would Install v2.05b1 and verify there isn’t a problem, and backup rule-set and Plug-Ins and whatever and Uninstall v2.05b1 and re-boot and try Installing v2.05b2 and re-boot. Afterwards manually “Allow” that Protocol Driver in Protocol Filtering.

 

With this configuration, do you confirm you still have "Protocol" alerts in the log ?
If yes, it is still wanarp that is indicated in the Console when asking for the driver logs ?

I've placed the old driver from the 2.05b1 here:
http://looknstop.soft4ever.com/Beta/En/2.05b1/LNSFW1.SYS
Normally you can use it with the 2.05b2.

If it works it will confirm the problem is in the new driver from the 2.05b2.
If it doesn't work, the problem comes from the looknstop.exe.

Thanks,

Frederic

 

I swopped the driver but it still didn't work. I've gone back to the newer one now.

 

Hey

This may seem like a stupid question, but when you swopped drivers did you also re-boot the Machine?

 

Ok, thanks, in this case the problem is in the looknstop.exe.
I will look at that.

Frederic