Emule connections problem [Resolved]

I only see three log entries that would probably relate to emule:

Data/Hora: 2007-03-13 19:07:19 Severidade: Média Relatado: Monitor de Rede Descrição: Violação da Politica de Entrada (Acesso Negado, IP = 89.122.151.143, Porta = 36283) Protocolo: TCP Entrada Fonte: 89.122.151.143:2214 Destino: 192.168.1.100:36283 TCP Flags: SYN Razão: ID da Regra de Controlo da Rede =9

Data/Hora: 2007-03-13 19:07:14
Severidade: Média
Relatado: Monitor de Rede
Descrição: Violação da Politica de Entrada (Acesso Negado, IP = 89.122.151.143, Porta = 36283)
Protocolo: TCP Entrada
Fonte: 89.122.151.143:2214
Destino: 192.168.1.100:36283
TCP Flags: SYN
Razão: ID da Regra de Controlo da Rede =9

Data/Hora: 2007-03-13 19:07:09
Severidade: Média
Relatado: Monitor de Rede
Descrição: Violação da Politica de Entrada (Acesso Negado, IP = 89.122.151.143, Porta = 36283)
Protocolo: TCP Entrada
Fonte: 89.122.151.143:2214
Destino: 192.168.1.100:36283
TCP Flags: SYN
Razão: ID da Regra de Controlo da Rede =9

You will notice that the Port shown is not the same as the port in your Network Monitor rule for TCP.

My guess is that you have emule still set to automatically assign the Port#; please verify that you have the auto-assignment turned off, and it’s set manually to the Port indicated in your Network Monitor rule.

Also be aware that you will need to have rule for emule in your Application Monitor, to match. Thus, you want to make sure you have two rules in the Application Monitor; one for TCP, one for UDP. OR, you could do it with one rule, as such:

Application: Emule (browse to your executable file)
Parent: (set it to “Learn”)
Action: Allow
Protocol: TCP/UDP
Direction: In
Destination IP: Any (or your local IP as per your Network Monitor; 192.168.1.100)
Destination Port: A set of Ports: 54662,54672
Miscellaneous: - (leave blank)

Okay.

Reboot computer to make sure the firewall’s memory is cleared out, and the new rules are set.

LM

Emule works fine since i´ve made that rulles in network monitor. And CFP works fine with emule on.
And when i take those logs, emule is switch of, only PeerGuardian and Utorrent are on.
That IP 192.168.1.1 is From my Router, i forgot to tell you(so stupid!!!).
When i have UTORRENT of, everything works fine, except the Perguardian updates.
The problem is when i launch Utorrent.

Okay, then I think I’ve missed something…

What exactly is the problem when you launch Utorrent?

LM

Sorry, I should say, I understand that you’re saying it freezes after 2 hours or so… my brain is buggy now. :wink:

But isn’t utorrent another p2p client application, similar to emule? You should have a similar application rule as for emule, and network rule as well, on the assigned port. Need to assign a port, don’t let it do it automatically, and turn off the UPNP feature as well.

Just like emule, that should be all you need to get a green light.

The only other thing I can come up with, if you have the utorrent rules set like that, is to turn off Protocol Analysis. You can find this under Security/Advanced/Advanced Attack Detection/Miscellaneous. Some users apparently find that this helps with a similar issue.

Let me look into the cpf.exe 99% thing, to see what I can see…

Hope this is of some help,

LM

Okay, master kenobi…

I’m back, armed with more info!

If turning off Protocol Analysis doesn’t reduce the cpf.exe usage, we’re probably looking at a logging issue; this unfortunately seems to occur with some p2p users; wherein CFP consumes a lot of resources in order to log firewall events.

There are a couple things you can try, to reduce this (until a fix is released):

Go to Activity/Logs, right click an entry, select “Log Events From” and uncheck Network Monitor. Wait a few minutes, or just reboot the computer, to clear the memory and set the logging change. Some users report that they keep having to turn this off; for others it works fine.

The actual log file is located in: c:\documents & settings\all users\application data\comodo\personal firewall\logs; the file is logs.log. Right-click, select Properties, and change the Attributes to Read-Only. This will allow you to keep logging turned on, but will clear it out each time you exit the firewall (such as with a reboot).

Hope that is of more help to you. I apologize for drifting off into “lala land” earlier… :-[

LM

The eD2k network exposes a memory leak in ZoneAlarm: logging large amounts of UDP traffic makes vsmon.exe grow and grow and grow.

Looks like Comodo has exactly the same problem. I wonder if and how it will be fixed.

In first place, THANK YOU VERY MUCH for your patiente!!! :wink: :wink: :wink:
Ok, Little Mac, i will try all that things, and i will wait a couple of hours to see at happen.
Today, or maybe only tomorrow, i let you know if everything is ok(I hope so!!).

Have a good night.

Hello little Mac,

Now i think it´s ok!!! :BNC :BNC :BNC
I just turn off Protocol Analysis and erase some Torrent files, that are already completed, from the UTORRENT list(i´ve had ± 85 files!!!). Now i have only 12 files downloading and uploading. Probably it was because the large amount of traffic, like you said!
I let the PC on all night and everything is ok, except the PeerGuardian updates.
I´ve the rulles in application monitor just as you told me, but PeerGuardian still give me the message
" ERROR CONTACTING URL´S" !
And it´s the only problem i have now!
Below there are the logs when i try update the PeerGuardian Lists

Data de Criação: 08:14:00 14-03-2007

Espaço de Log:: Hoje

Data/Hora: 2007-03-14 08:13:52
Severidade: Média
Relatado: Monitor de Rede
Descrição: Violação da Politica de Entrada (Acesso Negado, IP = 192.168.1.1, Porta = upnp-mcast(1900))
Protocolo: UDP Entrada
Fonte: 192.168.1.1:upnp-mcast(1900)
Destino: 239.255.255.250:upnp-mcast(1900)
Razão: ID da Regra de Controlo da Rede =9

Data/Hora: 2007-03-14 08:13:47
Severidade: Média
Relatado: Monitor de Rede
Descrição: Violação da Politica de Entrada (Acesso Negado, Protocolo = IGMP)
Protocolo: IGMP Entrada
Fonte: 192.168.1.1
Destino: 224.0.0.1
Razão: ID da Regra de Controlo da Rede =9

Data/Hora: 2007-03-14 08:13:31
Severidade: Média
Relatado: Monitor de Rede
Descrição: Violação da Politica de Entrada (Acesso Negado, IP = 192.168.1.1, Porta = nbname(137))
Protocolo: UDP Entrada
Fonte: 192.168.1.1:4826
Destino: 192.168.1.100:nbname(137)
Razão: ID da Regra de Controlo da Rede =9

Data/Hora: 2007-03-14 08:13:31
Severidade: Média
Relatado: Monitor de Rede
Descrição: Violação da Politica de Entrada (Acesso Negado, IP = 192.168.1.1, Porta = upnp-mcast(1900))
Protocolo: UDP Entrada
Fonte: 192.168.1.1:upnp-mcast(1900)
Destino: 239.255.255.250:upnp-mcast(1900)
Razão: ID da Regra de Controlo da Rede =9

Data/Hora: 2007-03-14 08:13:20
Severidade: Média
Relatado: Monitor de Rede
Descrição: Violação da Politica de Entrada (Acesso Negado, IP = 192.168.1.1, Porta = nbname(137))
Protocolo: UDP Entrada
Fonte: 192.168.1.1:4826
Destino: 192.168.1.100:nbname(137)
Razão: ID da Regra de Controlo da Rede =9

Data/Hora: 2007-03-14 08:13:15
Severidade: Média
Relatado: Monitor de Rede
Descrição: Violação da Politica de Entrada (Acesso Negado, IP = 192.168.1.1, Porta = nbname(137))
Protocolo: UDP Entrada
Fonte: 192.168.1.1:4825
Destino: 192.168.1.100:nbname(137)
Razão: ID da Regra de Controlo da Rede =9

Data/Hora: 2007-03-14 08:13:05
Severidade: Média
Relatado: Monitor de Rede
Descrição: Violação da Politica de Entrada (Acesso Negado, IP = 192.168.1.1, Porta = upnp-mcast(1900))
Protocolo: UDP Entrada
Fonte: 192.168.1.1:upnp-mcast(1900)
Destino: 239.255.255.250:upnp-mcast(1900)
Razão: ID da Regra de Controlo da Rede =9

Data/Hora: 2007-03-14 08:13:04
Severidade: Média
Relatado: Monitor de Rede
Descrição: Violação da Politica de Entrada (Acesso Negado, IP = 192.168.1.1, Porta = nbname(137))
Protocolo: UDP Entrada
Fonte: 192.168.1.1:4825
Destino: 192.168.1.100:nbname(137)
Razão: ID da Regra de Controlo da Rede =9

Data/Hora: 2007-03-14 08:12:59
Severidade: Média
Relatado: Monitor de Rede
Descrição: Violação da Politica de Entrada (Acesso Negado, Protocolo = IGMP)
Protocolo: IGMP Entrada
Fonte: 192.168.1.1
Destino: 224.0.0.1
Razão: ID da Regra de Controlo da Rede =9

Data/Hora: 2007-03-14 08:12:59
Severidade: Média
Relatado: Monitor de Rede
Descrição: Violação da Politica de Entrada (Acesso Negado, IP = 192.168.1.1, Porta = nbname(137))
Protocolo: UDP Entrada
Fonte: 192.168.1.1:4825
Destino: 192.168.1.100:nbname(137)
Razão: ID da Regra de Controlo da Rede =9

Any ideas Little Mac?

Thank you.

master kenobi,

I’m glad the utorrent is working better with protocol analysis turned off. I’ll go ahead and mark the topic resolved and close it. If you find you’re stilling having problems with it, just PM me or another Mod and we’ll reopen it.

For the peerguardian issue, why don’t you go ahead and start a new topic in the Help board? That way we can address that issue directly.

LM