Hello. I have been out of the forum for some time but I would like to tell you what I have found about P2P apps and NOD32 (in the networking part). I like to point before starting that this is not only a problem with NOD32, but there are other applications that can be affected by this. The main problem here is the way P2P programs like E-Mule or Azureus (or any other bittorrent client like bittornado, shareaza...) work. The users of these programs have noticed that having IMON / AMON running while running these P2P apps can develop conflicts. You can get slowdowns of your system, totally or partially hang in network activity or simply the things can go to the crashing level (application, windows or both). What I have seen after investigating a lot on the net (different webforums specialized in these kind of apps) is that P2P programs put a lot of stress over a network connection and any program that is monitoring traffic. It is very easy and common for a program that uses the bittorrent protocol or E-mule to make hundreds of connections at the same time with a lots peers. It is common when downloading a popular torrent with a big swamp that your system is connected to around 1000 machines or more at the same time. Here is where the application that is monitoring the traffic starts to have problems. An example of this is if you start a Emule or Azureus and start the download of some popular files (a good movie), after some minutes you can check netstat and you will be surprised with the number of actual connections been made. After some time (it can be some minutes or hours, it depends entirely of the number of concurrent connections been established) it is not uncommon that the P2P program stops to work, or that you completely lose network activity(even if the windows icon shows that the connection is OK) and cannot even surf the web. One of the ways to solve this problem while the developers find a way to fix this compatibility issues is to make sure you configure your P2P client in a special way, limiting the number of global concurrent connections possible. Not all the programs let you do this, and there is not a magic number for solving every problem out there. A number between 256-512 can work with Azureus for example. Another factor that you have to have in mind is that if you run a software firewall too, there are going to be 2 programs (NOD32 and the firewall) monitoring your network traffic at the same time, so the risk of a conflict is higher. These are some programs and situations that I have learned that have difficulties with P2P apps, (I like to point that programs like Kazaa don't fall well in this category because the way they work, Kazaa doesn't establish a so high number of concurrent connections like bittorrent or Emule do): -NOD32 -Zone Alarm (specially version 5) -Hardware routers/firewalls: These have special problems with P2P so if you have one of these and are having problems (the router hangs) here is your possible answer. I like to finish saying this: I love NOD32 and I don't blame the developers, this phenomenon was maybe not contemplated by them and this kind of stress in the network connection is maybe not common for everybody, but I would like to see a solution (turning off AMON(IMON is not in my solution list). P2P programs like Emule and bittorrent driven ones are becoming more popular everyday, so it is smart to look into this issue. Zonelabs is having a nightmare due to the same problem and they have a lot of unhappy customers for this reason. There is just to go to their forums and type "bittorrent" in the search field to find that the ZL stuff has not given the amount of attention that the problem deserves.