Hi, i am currently running the latest up to date version of spybot, CPF & CAV, windows XP sp1 and i got a 4 Mbit ADSL connection.
Since i installed CPF i’ve been noticing an impressive slowing down in Windows Live Messenger file transfer with other contacts. Something like 1-1.5 kB/sec insted of 20-25 Kb/sec. What should i do? Do i have to open some ports in CPF?
I’m sorry if there’s already a post for this problem in the forum, i searched for it but i found nothing.
Thanks…
Does anyone know how to solve it? Please someone answer!
Thanks.
Hi, while I see other problems with CAV and CPF together, can you try to disable the CAV and see how it reacts? Thanks.
Paul
Can you please show us your CPF logs?
I had noticed the same problem. When I turned off the CPF, Messenger file transfer worked well.
This can only be a case in sending files to someone else. If it happens while receiving, it is because the problem in the sender’s side.
While behind a firewall, MSN Messenger uses MSN Servers to send files which are otherwise impossible to send because of the packet filtering.
Microsoft has decided to limit the transfer rate for the one which occurs over MSN servers, intentionally.
This new MSN version may need some ports to be opened. The easiest way to se this is checking your CPF logs for blocked entries.
Egemen
Hi, while I see other problems with CAV and CPF together, can you try to disable the CAV and see how it reacts? Thanks.Paul
This is the log of CPF activity while sending the file, i copied many voices because i dunno which one is Messenger related :-X
Date/Time :2006-09-05 08:56:58 Severity :Medium Reporter :Network Monitor Description: Inbound Policy Violation (Access Denied, IP = 87.5.91.88, Port = ms-rpc(135)) Protocol: TCP Incoming Source: 87.5.77.189:1190 Destination: 87.5.91.88:ms-rpc(135) TCP Flags: SYN Reason: Network Control Rule ID = 14Date/Time :2006-09-05 08:56:53
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, Protocol = IGMP)
Protocol:IGMP Incoming
Source: 192.168.100.1
Destination: 224.0.0.1
Reason: Network Control Rule ID = 14Date/Time :2006-09-05 08:56:43
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 87.5.91.88, Port = MS-ds(445))
Protocol: TCP Incoming
Source: 87.5.192.49:2560
Destination: 87.5.91.88:MS-ds(445)
TCP Flags: SYN
Reason: Network Control Rule ID = 14Date/Time :2006-09-05 08:55:53
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, Protocol = IGMP)
Protocol:IGMP Incoming
Source: 192.168.100.1
Destination: 224.0.0.1
Reason: Network Control Rule ID = 14Date/Time :2006-09-05 08:54:53
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, Protocol = IGMP)
Protocol:IGMP Incoming
Source: 192.168.100.1
Destination: 224.0.0.1
Reason: Network Control Rule ID = 14Date/Time :2006-09-05 08:54:43
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 87.5.91.88, Port = MS-ds(445))
Protocol: TCP Incoming
Source: 87.5.107.203:32108
Destination: 87.5.91.88:MS-ds(445)
TCP Flags: SYN
Reason: Network Control Rule ID = 14Date/Time :2006-09-05 08:54:38
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 87.5.91.88, Port = MS-ds(445))
Protocol: TCP Incoming
Source: 87.5.107.203:32108
Destination: 87.5.91.88:MS-ds(445)
TCP Flags: SYN
Reason: Network Control Rule ID = 14Date/Time :2006-09-05 08:53:53
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, Protocol = IGMP)
Protocol:IGMP Incoming
Source: 192.168.100.1
Destination: 224.0.0.1
Reason: Network Control Rule ID = 14Date/Time :2006-09-05 08:52:48
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, Protocol = IGMP)
Protocol:IGMP Incoming
Source: 192.168.100.1
Destination: 224.0.0.1
Reason: Network Control Rule ID = 14
Waiting for news… 
However, Comodo is wonderful! (V)
Ehm… anyone?
Nope. These logs do not reveal anything. Perhabs when MS starts to support MSN Live, they will tell us which ports should be opened or they will try to use “passive” mode transfers.
Egemen
Hmm… ok…
So you can the problem be solved? I think i’m not the only person using Live messenger, and i also don’t think that i’m the only one experiencing this problem…
I can confirm the problem…
I’ve got the same problem… It’s driving me crazy.
Ok but this is not a Live version problem, i also noticed it using old version 7.5. So i am a bit surprised no one ever noticed and posted it…
With the old version I wasn’t able to estabilish a videocall… With Live, now I can, but I’ve this new problem :-/
I “resolved” the problem disabling some options in the “Application Behavior Analysis”: in particular the third, the fourth and the fifth ones… Disabling them, it seems that transfers are faster…
I did as you suggested, but it seems still not working… I’ll try again…
Anyonme has further ideas?
Same problem here, transfer goes like 20-80kb bursts and then pause. Any suggestions yet.
Had same kind of problems with zone alarm too.
Yeah, ZA has the same problem… However the only way so solve the problem, until now, was changing firewall. I’m sorry to say that, because i really like comodo, but i use Live Messenger a lot and i need fast file transfers…
Good work to everyone, and i hope u’ll solve this annoying point
There was a workaround for ZA, but it broke ZA so… (:CLP)
However ZA was a bullshit-similar application… at the beginning it was better, now it’s becoming always more like Norton applications… I left it for Comodo and then i had to leave comodo too 