I am using looknstop version 2.05. I use findnot.com's vpn service, and when i try to connect, looknstop doesnt give me the option to allow or block the connection, it just doesn't allow the connection. Also, even though I have disabled the audio alarm, It continually sounds as i am trying to connect. the only way I could get it to go through is by turning off the internet filtering rule "all other packets" at the bottom of the list. What is the best and most secure way to configure looknstop? thanks A.
I am also trying to find out how to connect to findnot using VPN through Zone Alarm free V5. It just never gets through ? Anybody know why this is as i dont have any problems with ZA otherwise.
Hi admash ... and welcome to Wilders Do your logs indicate what is being blocked by the "all other packets" rule that you may need to permit? Regards, CrazyM
Hi admash, Yes, having the blocked packets from the log would help to know what needs to be allowed. Very often VPN are using IP Protocol 47. A specific rule for that is available here: http://www.looknstop.com/En/rules/rules.htm#VPN Another set of rules for specific VPN are also available here: http://looknstop.soft4ever.com/Rules/NortelVPN.rie Regards, Frederic
Thanks to all for your help. Here is a sample from the log: 02-07-05,03:39:53 U-2 'All other packets ' 193.151.75.22 IP Protocol:47 02-07-05,03:39:53 D-3 'All other packets ' 193.151.75.22 IP Protocol:47 02-07-05,03:39:55 U-4 'All other packets ' 193.151.75.22 IP Protocol:47 02-07-05,03:39:56 D-5 'All other packets ' 193.151.75.22 IP Protocol:47 I have downloaded the Protocol 47 rule, and I am now able to connect, however, I am now getting another message in the log: 02-07-05,03:49:09 U-18 'All other packets ' 224.0.0.22 IGMP Data:148 4 0 0 02-07-05,03:49:09 U-19 'All other packets ' 224.0.0.22 IGMP Data:148 4 0 0 02-07-05,03:49:09 U-20 'All other packets ' 224.0.0.22 IGMP Data:148 4 0 0 02-07-05,03:49:09 U-21 'All other packets ' 224.0.0.22 IGMP Data:148 4 0 0 02-07-05,03:49:09 U-22 'UDP : Any other UDP pack' 239.255.255.250 UDP Ports Dest:1900 What do I need to do next?
Try reading post "Configuring LnS for routers" (a sticky one, at the beginning of the posts list). X.
admash, Right now I am also fighting with some proper rules for my new Cisco-VPN client. And I do see these UDP port 1900 blocks also. Hopefully tomorrow I try posting my rules here.... Be patient Thomas
Usually blocking these packets has no consequence. If you have a lot of these packets in the log, you can try to create a rule that will silently drop them. Otherwise you can simply let this happening. Frederic
admash, Since there is so much "official" work to do at the moment, I don't get a minute to play with the VPN client config in LnS. Sorry! Maybe you solved the problem already by yourself ?? Thomas
I am still 'playing' with it myself. I am a bit of a novice, but am eager to learn. All of your help is appreciated.
To set Zone Alarm to allow you access to findnot, go to the Log Viewer in the Alerts and Logs section. Switch it to Firewall mode using the dropdown. You should see attempts to reach an IP address starting 193.xxx.xxx.xxx. Right button click, then select Add to add it to your trusted zone. You will probably need to add more than one address, I added two and all was then well. If you move between findnot servers, you will need to add all the IP addresses you use.