[SOLVED] [eMule] Still get lowid

Comodo Internet Security - CIS Firewall Help - CIS
1

Hello

Before installing Comodo Internet Security Premium (4.1.150349.920), I was using eMule just fine, but since then, I get the usual error message:


Warning eDonkeyServer No2 (212.63.206.35:4242) - You have a lowid. Please review your network config and/or your settings.

I’ve added a rule in “Application Rules” and moved it to the first line:

Network Control Rule: left all defaults


Action = Allow
Protocol = TCP or UDP
Direction = In/Out
Source Address = Any
Destination Address = Any
Source Port = Any
Destination Port = Any

Saved, closed dialog, tried to connect again in eMule: Same error.

Do I need to do something else?

Thank you for any hint.

PS: BTW, why does the forum use HTTPS?

2

Whilst I’m not familiar with eMule specifically and assuming there is nothing in CIS’s event logs regarding eMule or 212.63.206.35 (is there?), this might be something to do with your Global Rules. Apps, like eMule, often use PINGs, ECHO REQUEST’s and other such things to test connection speeds, etc. Post a screen shot of your Global Rules. But, it might be easier just to temporarily check the Log option on all the Global Rules & see what turns up in the Firewall event log regarding 212.63.206.35.

Because you requested it, that’s the way you first accessed the forums (on your bookmark shortcut maybe?). Anyway it’s completely optional. There’s a toggle switch on the top menu bar (the little white pad lock

)

3

I didn’t find where the log files are: How can I check this?

this might be something to do with your Global Rules. Apps, like eMule, often use PINGs, ECHO REQUEST's and other such things to test connection speeds, etc. Post a screen shot of your Global Rules.

Those are the default settings:

http://img26.imageshack.us/img26/7632/comodofirewallglobalrul.jpg

Don’t application-specific rules take precedence?

Thank you.

4

Open CIS - Firewall - View Firewall Events. If you need help with the events, resize the window & columns to expose more info and post a screen shot.

I’m not sure they are… it looks like (to me) that the Stealth Ports Wizard process has been run & possibly more than once.

It depends on the traffic direction. It goes something like this…

For Outgoing connections, the Application Rules are first and then the Global Rules.

For Incoming connections, the Global Rules are first and then the Application Rules.

But, with the current final Block rule in the Global Rules, anything that is not TCP or UDP will be silently blocked for eMule. However, with the eMule issue it is possible that the eMule servers are attempting to contact your OS rather than the eMule application anyway.

edit: typos

5

Closing, restarting eMule: No line about eMule.

For Incoming connections, the Global Rules are first and then the Application Rules.

Thanks for the tip. I don’t find this logical, but anyway, for those having the same issue, here’s how the problem was solved:

http://img707.imageshack.us/img707/5043/comodemuleallowinoutcon.jpg

Thanks for the help.

6

The Stealth Ports Wizard process can help (or not). If you had chosen the second option…

Alert me to incoming connections and make my ports stealth on a per-case basis

… then there would be no final Global Block rule and things would have worked as you logically expected them to. Your Global Rules would have looked more like the attached image (my current Global Rules… which would be the option above, with the LAN trusted Zone added).

However, if either of the following were selected…

[b]Define a new trusted network and make my ports stealth for everyone else[/b]

… or …

[b]Block all incoming connections and make my ports stealth for everyone[/b]

… then that would create the Global allow rules (for various items, depending on option used) with the final Block rule (blocking everything else).

I hope that helps.

[attachment deleted by admin]