no connection at boot up

[whoisit]

I'm having a problem with LnS after installing it on a new pc. The network connection doesn't work\is being blocked after starting the computer. I have to close and restart LnS in order to get the connection to work. It seems to be blocking before that.

Why is this?

[whoisit]

The connection also stops after a while. Again, LnS has to be closed and restarted in order to get back to normal.

[whoisit]

This is very awkward. The connection dies after a while and LnS has to be restarted.

Any suggestions anyone?

[whoisit]

There is a non-stop sytream of a connection that's being blocked. this is an example:
7-25-05,18:09:50 D-2755 'ICMP : All ICMP types (n' 194.134.180.37 ICMP Type:11 Code:0
07-25-05,18:09:50 D-2756 'ICMP : All ICMP types (n' 194.134.180.37 ICMP Type:11 Code:0
07-25-05,18:09:51 D-2757 'ICMP : All ICMP types (n' 194.134.180.37 ICMP Type:11 Code:0
07-25-05,18:09:51 D-2758 'ICMP : All ICMP types (n' 194.134.180.37 ICMP Type:11 Code:0


It really goes on and on, continuously. What could that be (modem?) and should I allow it?

[Frederic]

Are these alerts the only ones you get in the log (ICMP Type 11) ?

It could be a problem of IP Fragmentation.
You can try to import the following rules:
http://www.looknstop.com/Fr/rules/downloader.php?file=club_internet_adsl.rie

(sorry the name of the rule doesn't say Fragmentation, and it is in French, but it is just to see if this solves your issue).

Frederic

[whoisit]

Thanks, but that didn't help.
I didn't notice this before, but these alerts only occur when Bitcomet is running. These messages are new, after upgrading Motherboard\processor.

I don't know why this should make a difference, but it does.
Is there an explanation for the "dying" internet connection, forcing a restart of LnS in order to make it work again?

[Frederic]

Could you answer the first question:
Are these alerts the only ones you get in the log (ICMP Type 11) ?

If the answer is Yes, then you should try to add a specific rule allowing these packets. To do so, use a right click on this kind of alert in the logs.

Thanks,

Frederic

[Phant0m]

It is recommended that you to reproduce this anomaly, but have very little running in the background that clients that uses your connection. After the problem happens, poster the log file.

[whoisit]

After booting (and not being able to connect) the log is completely empty. Could there be a conflict with the new mb\processor?

[whoisit]

When the connection dies, there are messages in the log like the ones I posted before. Should I just allow these? And for any specific application?

[Frederic]

Yes, you should try to allow these packets.
There is no specific application associated to these packets, because they are used by the system directly.

For the problem of the connection at startup, you should try to only deactivate the Application Filtering and reboot, just to see if the problem is not coming from an application being blocked although it should not. This also could solve the disconnection issue, if finally the problem was you blocked by mistake (system ?) application to connect.

Frederic

[whoisit]

Thank you for the quick reply.

"only deactivate the Application Filtering and reboot"
I did that and the problem disappeared. It turned out that I had blocked a Windows process that has to be able to connect. Unblocked it: it's working now.
Even the reported messages in the log seem to have gone.
Thanks again for your support.