LNS setup

Hi,

When setting up LNS, Windows said that the software may be incompatible because it wasn't tested on Windows - it doesn't include the Windows compatiblity logo or something.

Then I have this question: When LNS was just set up, I'm getting all kinds of notifications in the log tab, about traffic being blocked. Do I need to add, the ports attempted, to the ruleset?

Best regards,
Mark Klomp

 

That depends on what you want to do. If you have traffic like that for any program you are using: create the rule. If you see things that you don't want: block it.

 

OK, so I'll add the ports, that are attempted to make connections through for specific apps.

OK and how about the incompatibility notice from windows when installing the app?

 

BTW I'm using Win XP Professional SP1

 

It is not an incompatibility notice, it is only a warning because one driver is not signed. This is a Microsoft protection to avoid malicious drivers to be installed.

Frederic

 

I have many notifications in the Log, how to add any notification as a rule to the ruleset?

 

The program crashes when adding a rule from the log tab

 

And how about the ''Standaardregels.rls'' which are the rules in Dutch language, which were tried to be set up by LnS at the Setup process, but where it comes with a notification window about that it couldn't open the file.
I searched on my HD, it said it couldn't find the file.
I think that the file is included with the package you download when you download the Dutch language for the software.
But how can I use that Dutch translated ruleset now?

 

Could you be more specific ?

- it crashes systematically when you use this feature, and never worked
or
- it worked several times and then crashed once
or
- it worked several times and now crahes everytime


What is the number of rules of your ruleset ?
What is the kind of packets you are trying to create a rule for ?

Thanks,

Frederic

 

Actually there is no Dutch ruleset.
This is simply a problem in the .lng translation file: the name of the ruleset should not be translated.

Frederic

 

Hi,
Everytime I use the feature it crashes, this is from the beginning. I have just installed LnS too on my 2nd computer and there it also crashes when trying to add the rule via the Log tab.

Is this bug fixed in the newest beta version; 2.05p3? I'm using 2.05p2.

 

BTW, I'm using the Enhancedruleset.rls

 

The problem is coming from the translation file (nederlands.lng) which is not correct.
I've updated it. Open the Plugin dialog box configuration, select the language plugin and clic the Configuration button. In the new dialog box that will open, in the update Group, clic the "Check Now" button and normally the new .lng file will be downloaded.
The new .lng will take effect the next time Look 'n' Stop will be started, either when Windows will be restarted or if you manually Stop+Restart Look 'n' Stop.

Frederic

 

In fact something has been done in the 2.05p3 to avoid the error dialog box display:

this way the .lng can actually still contain a translated ruleset name (maybe it will be useful in the future).

Frederic

 

Hi Frederic,

Can you please attach the updated .lng file with a reply from you?
The problem is, that when I run LnS I even won't be able to connect to the internet, so I won't be able to update the file through it. So I thought, if you can attach the file, then I'll download it, and then I will copy it to the C:\Program Files\Soft4Ever\looknstop directory to update the .lng file.

Thanks,
Ren

 

Hi,

I didn't understand you are not able to connect to internet when Look 'n' Stop is started. I thought you just have some alerts in the logs, but eveything else was working.
This problem has to be solved first and the .lng file or creating rules from log won't help anyway in that matter.

Could you confirm you are running the standard ruleset or the enhanced rulesest ?
- If yes, then just disable the Internet Filtering and verify if you can connect to internet or not. If you are still unable to connect to internet, then you have probably blocked an application, and the problem is not coming from rules or the internet filtering. Just remove all applications in the application filtering and re-authorize the legitime applications as soon as they will try to connect (in particular svchost and services you may have blocked)
- if not, please confirm you have the same problem with one of the two standard rulesets and then do the operation just above

Thanks,

Frederic

 

I have switched from the EnhancedRuleSet to the StandardRuleSet, now my internetconnection works. When I have Internet Filtering put off, I can also connect to the internet.
So the problem is lying in the EnhancedRuleSet.
I tested if I still get the crash when trying to add a rule via the Log tab, and yes it is.
BTW I have to say this, yesterday I upgraded from SP1 to SP2, when I had SP1 I could connect to the internet using EnhancedRuleSet.
Now I can't. On my 2nd computer there is still Win XP with SP1 and there it works with EnhancedRuleSet.

So I'll use the StandardRuleSet for now then. So thats fixed, now I want to ask if you wanna upload the English .lng file to solve the crash.

thx

 

Ok, in this case, is there specific alerts in the Log when you are using the EnhancedRuleset and it doesn't work ?
Perhaps you enabled the Fragmentation Flag rules ? (by default they are disabled)
Otherwise it could be the "Block Incoming Connection rule" which is the problem and the difference compared to the Standard ruleset.

Do you mean you finally retrieved the updated .lng file ?
The version inside the file should be 1.01 (the previous one was 1.00). Could you check ?
Also did you quit/restart Look 'n' Stop as I mentioned ? otherwise the new .lng was not taken into account yet (if you did the test just after retrieving the file without quitting Look 'n' Stop).
If the version is 1.01 and you still get the crash, I suppose the menu open before the crash and the crash occurs when you select an item in the menu. What is the text in the menu item (don't select it to avoid the crash, just read it) ?

Thanks,

Frederic

 

--I tested if I still get the crash when trying to add a rule via the Log tab, and yes it is.-- > it wasn't updated yet.

I did update the .lng now, because now i was able to because now I have got internet access when LnS is running, and yes its fixed, it won't crash anymore when adding a rule. My comptuer was trying to use UDP port 1900.
Now Im getting a request , TCP, from address gprsh65.isp.t-mobile.cz
should I trust this, and add the rule?

 

It depends on the port and the rule that has blocked the packet, and if you are using special applications (like a server or P2P) or not.

If the rule is the "Block Incoming connections" and if you are not using a special application, no you don't have to allow this packet. Look 'n' Stop is doing its job by blocking suspect packets.

Another example: if you have installed a public http server on your PC, and if the port is 80 and the rule still "Block Incoming connections", then it is normal to have some alerts from people trying to reach your server and yes you should create a rule.

Frederic

 

How do I make a rule to allow my AV to update. I'm using NOD32.

thx

 

How to configure LNS to allow connections in my p2p app?

 

initially, when you setup your look n stop you should had allowed in the area "application filtering" NOD32 KERNEL SERVICE, when you try to upate your nod32 definitions you have to see a warning of wether allow or block this service accesing to the internet, just give a click on "allow", now you will see it on the "application filtering" tab of look n stop, that means that this service/program is allowed to acces to the internet.

for p2p applications id recommend phantom´s ruleset

 

where to download phantom's ruleset? link pls.