L'N'S for windows 7 ?

[1hui]

the computer without L'N'S is not safe ;D
so when the new version for windows 7 will be released?;D

[Phant0m]

Perhaps after the Windows 7 gets shipped out... :P


You using the Windows 7 beta? Have you tried using Look 'n' Stop 2.06p3 on it?



Regards,
Phant0m``

[1hui]

-{ Quote: "Perhaps after the Windows 7 gets shipped out... :P
You using the Windows 7 beta? Have you tried using Look 'n' Stop 2.06p3 on it?
Regards,
Phant0m``" }-

hi Phant0m

sorry for replying so late.
yes,I am using win7 beta(ver 6801).
I was using LnS 2.06 when I post this thread.I installed it on win 7.
Reboot.
BLUE SCREEN.....

I have installed LnS 2.06p3 on win 7 now.
I haven't got a bule screen yet.
but
Looks like the language plugin doesn't work.

thanks for paying attention.

1hui.

[SOUSOUS]

Using 2.06p3 french version on Windows 7 7000, works fine for the moment except the DLL detection, always BSOD

[Frederic]

I've tested the 2.06p3 version on the build 7000 (Win32 only, at that time), and it is working fine (for the standard features).

Normally the TDI stack is no longer supported after Vista, so it was unexpected the application filtering still installs and works properly.
I don't know if finally TDI will be still supported, or if this is just for this beta and it will be removed later, in a future beta, or for the final release.

Yes, the DLL filtering requires an update, here is a patch version of lnsfw1.sys fixing that:
http://looknstop.soft4ever.com/Beta/lnsfw1/LNSFW1-p2.zip

Regards,

Frederic

[1hui]

hi Frederic

The new driver works well now.

It looks like that LnS 2.06p3 works perfect on windows 7 beta build 7000 now!;D


Regards,

1hui

[thylacine]

hi Frederic, i don't know what's wrong, but i can't even connect to internet with 2.06p3.

i'm connecting to broadband using PPPoE. On XP system, i set the preferred network interface as "WAN Miniport (IP) - Look 'n' St - xxxxx". All works.

However, in Win7, this network interface selection doesn't work. In the Welcome tab, the status shows IP address as 0.0.0.0. The Connected checkbox is not ticked, but the Statistics data is working.

Any ideas?

thanks!

[Frederic]

Hi thylacine,

After you are connected through PPPoE, could you try using the following tool:
http://looknstop.soft4ever.com/Tools/AdaptList.exe

I would like to know what you get for "WAN Miniport (PPPoE)" and "WAN Miniport (IP)" adapters.

I understand Look 'n' Stop in the options tab only shows "WAN Miniport (IP)" but not "WAN Miniport (PPPoE)".

Thanks,

Frederic

[thylacine]

well, i don't have "WAN Miniport (PPPoE)" listed.

i'm attaching the lists here.

note: i've masked the last 3 octets in the mac address listed. hope it's ok.


additional info: Since i noticed LnS doesn't function in Win7, I have set Windows Firewall enabled, although enabling/disabling it doesn't make any difference to LnS at all.

thanks!

[Phant0m]

Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
Adresse MAC: 00:11:2f:xx:xx:xx
Adresse IP: 192.168.1.2

Does this 'Marvell Yukon 88E8001/8003/8010' Network Adapter show in the Network interfaces list? Is this your primary adapter used when making Internet connection?

[thylacine]

Marvel Yukon is the main/only adapter for internet connection.

I have 4 entries in the Network Interfaces screen:

WAN Miniport (IPv6)
WAN Miniport (Network Monitor)
WAN Miniport (IP)
Marvell Yukon 88E8001/8003/8010

[Phant0m]

Try checking the adapter 'Marvell Yukon 88E8001/8003/8010' and 'Apply' it and then re-visit the Look 'n' Stop - Welcome screen and see if you have 192.168... shown for 'IP Address: field.


Do some surfing, you should see the Statistics information increasing.

[1hui]

If you select the adapter 'Marvell Yukon 88E8001/8003/8010"
you should add a rule to allow PPPoE frames( ethernet type 8864 or 8863?)

IF you add a rule to allow PPPoE frames.It looks like that you add a rule "allow all"..:doubt:

[thylacine]

@Phant0m,

If i select adapter "Marvell Yukon", the Welcome screen shows conencted IP as 192.168.1.2 ... statistics are increasing .... however, the Standard/EnhancedRulesSet blocked all incoming packets ...

Rule: All other packets
Type: ETH
Address: 00:90:1A:xx:xx:xx

[Phant0m]

There must be a problem with getting the IP on "WAN Miniport (IP) - Look 'n' St - xxxxx", but you say the Statistics is increasing.... And you don't have "WAN Miniport (PPPoE)" in that list, I guess you'll have to wait for the big man to arrive to solve your problem. ???

[Frederic]

-{ Quote: "well, i don't have "WAN Miniport (PPPoE)" listed.

i'm attaching the lists here.

note: i've masked the last 3 octets in the mac address listed. hope it's ok.
" }-
There was actually a "WAN Miniport (PPPOE)" in the file you attached, but no IP attached to it:
WAN Miniport (PPPOE)
Adresse MAC: 00:00:00:00:00:00
Adresse IP:

I guess your IP address was mentioned for that one:
ISP
Adresse MAC: 00:00:00:00:00:00
Adresse IP: xxx.xxx.xxx.xxx
Is it correct ?

And the problem is actually to associate the driver adapter name (Wan Miniport IP) to this interface ("ISP").

-{ Quote: "
additional info: Since i noticed LnS doesn't function in Win7, I have set Windows Firewall enabled, although enabling/disabling it doesn't make any difference to LnS at all.
" }-
Yes, the firewalls are not linked.

If you want to use Look 'n' Stop, what you can do is editing the rules using "Equal my @" criteria for IP Address settings, and replace this criteria with "All".
There are two important rules which use this criteria:
- UDP DNS
- TCP : Authorize most common Internet services
And select back the Wan Miniport IP network interface in the options.

This is the only reason why it is not working: the IP address associated to the adapter is not properly retrieved.

After you confirm "ISP" was the right adapter for the IP address I will propose a patch for looknstop.exe (so you could use again "Equal my @" criteria).

Regards,

Frederic

[thylacine]

the ISP is my dial-up to broadband. it's using dynamic IP.

let me try your suggestion.

i'll update here soon.

[thylacine]

well, i need a patch (or update) to associate my broadband dialer with WAN Miniport ...

thanks guys

[Frederic]

Hi thylacine,

I've updated AdaptList to display the type of interface:
http://looknstop.soft4ever.com/Tools/AdaptList.exe

I would like to know which interface type is detected for this "ISP" connection.

Note: the new AdaptList tool displays only network interfaces having an IP layer (to get all network interfaces, "-all" switch can be used, normally not required here).

Thanks,

Frederic

[thylacine]

hi frederic,

attached is the updated info.

thanks!

[Phant0m]

You're in luck thylacine! The AdaptList log reveals Frederic's enhancement is working like a charm. :)



Regards,
Phant0m``

[thylacine]

hi Frederic/Phant0m,

been some time now since my last update ...

good to hear the enhancement is coming along. But, where is it? :)

[Frederic]

Hi thylacine,

Did you receive my email with a special version to test (one month ago) ?

Frederic

[thylacine]

i'm afraid not ... been awaiting my email since i PMed you my email ...

strange ... i thought you were still figuring out a possible solution, that's why i dropped by asking for updates ;)

anyway, do you mind resend it again?

thanks frederic!

[thylacine]

oh wow! the fix works flawlessly!

now i don't feel 'naked on the Net' with Windows 7 anymore ;)

THANK YOU, Frederic and team! A good job well done!

[ktango]

Hi Frederic,

In Windows Vista win32 chinese (simplified) edition, The network interface selection doesn't work. In the Welcome tab, the status shows IP address as 0.0.0.0. The Connected checkbox is not ticked, but the Statistics data is working.

The AdaptList displays the type of interface as follows :

Software Loopback Interface 1
MAC Address: 00:00:00:00:00:00
IP Address: 127.0.0.1
Interface type: IF_TYPE_SOFTWARE_LOOPBACK (24)

Realtek RTL8168B/8111B Family PCI-E Gigabit Ethernet NIC (NDIS 6.0)
MAC Address: 00:0b:2f:25:a2:d9
IP Address: 192.168.1.3
Interface type: IF_TYPE_ETHERNET_CSMACD (6)

VMware Virtual Ethernet Adapter for VMnet1
MAC Address: 00:50:56:c0:00:01
IP Address: 192.168.146.1
Interface type: IF_TYPE_ETHERNET_CSMACD (6)

VMware Virtual Ethernet Adapter for VMnet8
MAC Address: 00:50:56:c0:00:08
IP Address: 192.168.129.1
Interface type: IF_TYPE_ETHERNET_CSMACD (6)

ADSL
MAC Address: 00:00:00:00:00:00
IP Address: 58.45.96.67
Interface type: IF_TYPE_PPP (23)

Please help to advise.

Regards,
ktango

[Frederic]

Hi ktango,

Which build of Win7 beta ar you using ?

Thanks,

Frederic

[ktango]

Hi Frederic,

It is Windows Vista win32 chinese (simplified) edition.

Regards

ktango

[Frederic]

Yes, but is it build 7000 or build 7057 ?
Someone else posted a similar issue in the french forum, for the build 7057:
http://www.wilderssecurity.com/showthread.php?t=236963

Frederic

[Phant0m]

Windows 7 Build .. ?

Information can be found in the registry location .. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion

[Triple Helix]

He says he has Vista guys?

TH

[Phant0m]

True... but did you notice the topic title? :P


-{ Quote: "He says he has Vista guys?

TH" }-

[Triple Helix]

-{ Quote: "True... but did you notice the topic title? :P" }-

Yes but it could be him that posted in the wrong Thread! :wacko:

[Phant0m]

Build information can be found in the registry location .. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion ... not specific to Windows 7 :P

[ktango]

Windows Vista win32 chinese (simplified) edition is build 6001.

Windows 7 is build 7057

Regards

ktango

[Triple Helix]

-{ Quote: "Build information can be found in the registry location .. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion ... not specific to Windows 7 :P" }-

There we go he is using Both! :P

[Frederic]

Sorry ktango, my mistake, since the thread was for Windows 7, I have completely missed you are saying you are using Vista :-[

So, back to your initial post, could you confirm the interface corresponding to your internet connection, and to be used in Look 'n' Stop (probably through "Wan Miniport (IP)" should be:

ADSL
MAC Address: 00:00:00:00:00:00
IP Address: 58.45.96.67
Interface type: IF_TYPE_PPP (23)

Thanks,

Frederic

[jacksontan]

Hi,Frederic,it is Vista.
http://mediafarm4.ucomo.com/photo_thumbnail_image/53/50/2dec6ad3-d39e-4a9b-b0bd-1ff3b7457baf.jpg

http://mediafarm4.ucomo.com/photo_thumbnail_image/25/73/88fedcb6-f5ab-4d27-a0ef-0a8d623a9654.jpg

http://mediafarm4.ucomo.com/photo_thumbnail_image/21/99/065a0efd-de8f-4564-9d41-8e301b90d50c.jpg

http://mediafarm4.ucomo.com/photo_thumbnail_image/10/5/428070a2-c99a-409f-a31d-e568322e8cc7.jpg

[ktango]

-{ Quote: "Sorry ktango, my mistake, since the thread was for Windows 7, I have completely missed you are saying you are using Vista :-[

So, back to your initial post, could you confirm the interface corresponding to your internet connection, and to be used in Look 'n' Stop (probably through "Wan Miniport (IP)" should be:

ADSL
MAC Address: 00:00:00:00:00:00
IP Address: 58.45.96.67
Interface type: IF_TYPE_PPP (23)

Thanks,

Frederic" }-

Hi Frederic,

For ADSL ,It is
MAC Address: 00:00:00:00:00:00
IP Address: 58.45.96.67
Interface type: IF_TYPE_PPP (23)

Regards

ktango

[1hui]

-{ Quote: "True... but did you notice the topic title? :P" }-

Vista is called 'The beta Vision of Win 7'.
Maybe They are similar somewhere. :p

[Defenestration]

Given that a lot of people will probably run Windows 7 RC as their main system, will a general release of LnS be made with support for it ?

[Frederic]

There will be first a minor update (2.06p4) to fix this PPP detection issue (actually not specific to Win7) and for the DLL detection for Win7 (Win32 only).

Frédéric

[Defenestration]

When will 2.06p4 be released (I'm after the x64 version) ?

[Frederic]

It should be before the end of the month if everything goes well (in particular with Win7 RC).

Frederic

[Defenestration]

I'm keen to start running Win7 x64 RC and want to use LnS with it. Can I get hold of an x64 build of the special version you sent to thylacine (PM me the link) ?

Thanks in advance!

[Frederic]

Do you have a problem with the detection of a PPP connection ?
If you do, send me an email at lnssupport@soft4ever.com.
If you don't, normally the current 2.06p3 version should be Ok.

Thanks,

Frederic

[thylacine]

an update ... i just installed Win7 RC (b7100) ... LnS is back with the same problem, and this happens with temporary fix in place...

will totally remove LnS and starts identifying the source ...

[thylacine]

hi frederic, something is screwed up here .. i can't install/remove LnS ...

the uninstaller removed the files, but my Device Manager (Network Adapters) all showing ! marks ...

is there a manual way to remove LnS?

thanks!

[Frederic]

Yes, you can try this procedure:
http://www.looknstop.com/En/faq_problems.htm#driver_remove

Did you perform a fresh install of Win7 RC, or did you perform a simple update ?

Frederic

[thylacine]

officially, b7100 RC doesn't support 'upgrade' over b7000 Beta ... but since i wanted to preserve the appplications, i performed a little 'bypass' upgrade ...

of course fresh install is preferable, but not practical if you've been using Beta b7000 as ur day-to-day OS (and much preferred over Vista!)

will try the removal procedures and update here ;)

thanks frederic!

[thylacine]

hi frederic,

i got stuck removing some keys at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\S4E_LNSDRIVERMP

i have 0000 to 0003, and these keys are related to the unremovable ! entries in Device Manager.

[1hui]

-{ Quote: "
i got stuck removing some keys at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\S4E_LNSDRIVERMP

" }-
hi thylacine
You need to change the permissions of the key and subkeys.
208816
I hope this could help .

[thylacine]

hi 1hui, can't set any permissions ...

[1hui]

-{ Quote: "hi 1hui, can't set any permissions ..." }-

hi thylacine
try to do this.
permissions---Advanced---owner,click one of the name ---ok
permissions---add--Advanced--find now,choose "everyone"--ok,choose "full control"(permissions for everyone)
change the permissions of the key and subkeys one by one
pardon for my poor english..

[1hui]

-{ Quote: "
permissions---Advanced---owner,click one of the name " }-
The name should not be 'Administrator'

[Frederic]

Maybe it would work in safe mode.

Did you remove all the other keys ?
Usually you can't remove these ones, some other LNS references still exist somewhere else.

If finally you can remove these keys, or if you try to reinstall anyway, I suggest you do also some cleanup in c:\windows\inf. Remove there all lnsdriver*.inf,lnsdriver*.pnf files, and search for the oemXX.inf files containing "soft4ever", then remove these oemXX.inf files and the corresponding oemXX.pnf files.
This additional procedure is only for the re-installation, it won't help to cleanup the registry.

Regards,

Frederic

[thylacine]

hi guys,

no luck removing the dreaded drivers :( it's annoying though ...

is there a manual uninstaller available?

[Frederic]

Hi thylacine,

The registry procedure is already manual. There could not be something more manual...

Did you really try in safe mode ?

Maybe the installation will go anyway, if you performed some cleanup yet.

Regards,

Frederic

[thylacine]

hi frederic ...

following ur advise on May 12, i finally managed to install LnS back. Fully operational.

However, the dreaded Yellow ! are still there.

As long as LnS is working, i'm happy :)

[Frederic]

Hi thylacine,

Ok, thanks for the follow-up.
I'm happy for you too ;)

Did you something else special, or did you just try to install again ?

Frederic

[thylacine]

hi frederic, i relooked your suggestion on this part:

-{ Quote: " I suggest you do also some cleanup in c:\windows\inf. Remove there all lnsdriver*.inf,lnsdriver*.pnf files, and search for the oemXX.inf files containing "soft4ever", then remove these oemXX.inf files and the corresponding oemXX.pnf files.

This additional procedure is only for the re-installation, it won't help to cleanup the registry." }-
i wondered, so i follow thru the steps. Reinstallation worked (previously wasn't, so i guess this part is the culprit).

however, the registry-thingy still bugs me (and creates the Yellow ! marks).

I'm glad that the *special* thing is i feel secured now with LnS running with Win7.

p/s: The reason why LnS is preferred because it's a 2-in-1 solution: application filtering (managing) & Firewall. Previously, I used Windows Firewall + Vista Application Control. I hate softwares calling 'home', hence the need for LnS or Vista Application Control to manage these softwares making outbound connections.

thanks Frederic!