Some problems with rules for uTorrent

Help for v2
#1

My IP: 10.3.xxx.xxx
incoming port is 5000, forwarded
uTorrent is setuped to communicate on 10.3.xxx.xxx IP

I have these rules for uTorrent:
NetMonitor

  • allow TCP/UDP in, destination port (5000), destination IP 10.3.xxx.xxx, source IP any, source port any
  • allow TCP/UDP out, destination port (any), destination IP (any), source IP 10.3.xxx.xxx, source port any

listening port (5000) is properly forwarded

AppMonitor

  • allow TCP/UDP in, destination port (5000), destination IP 10.3.xxx.xxx
  • allow TCP/UDP out, destination port (any), destination IP (any)

So as you see I have opened connection on incoming port 5000. But when I run uTorrent and start downloading I can see CPF alerts that uTorrent trys to receive incoming connections on port 5000 and destination IP adresses that are others as my IP.

So destination IPs of incoming connection on my port 5000 are not IPs of my PC. :o And I must add new incoming rule or modify the old one.

Is it correct? Why yes or why not?
And my second (third) question is.
How should I correctly setup rules for uTorrent? It must be so secure as possible.

Thank you. (B)

#2

I’m not a uTorrent user, but I’ve heard that you should turn off UPnP in uTorrent.
Your IN rule looks ok and should work.
Your Out rule is not needed if you have the default rules, where it is a rule for allowing all on TCP/UDP OUT

First, check your logs and see what rule that’s stopping uTorrent.
Try to restart CPF.
Then if it doesn’t work, restart the PC.

#3

Hi.
I’ve had turned off UPnP from the beginning. I’ve changed NetMon rules so I had to add outbound rule for uTorrent.

NetMon rules are OK, they are not blocking uTorrent.

AppMonitor has that strange (maybe only for me) alerts (uTorrent trys to receive incoming connections on port 5000 and destination IP adresses that are others as my IP). When I add new AppMonitor inbound rule with destination IP setuped to any, the problem is solved. But my question is, why? Why must be inbound destination rule ‘IP any - port 5000’ and not ‘my IP 10.3.xxx.xxx - port 5000’ where uTorren is waiting for incoming conections?

I do not have any other application with this problem.

Thank you.

#4

I checked my app rules, and I have the same… The only one that i have to have ANY on, is my torrent program… Azureus…