Quote:
|
Originally Posted by Digital_Trucker
 It's nice to have a pro around! Yes, I do have it set up as a single instance (only because I didn't think it would be a good idea to be trying to change the same files with 2 different instances). The only thing I'm wondering about in that regard, though, is why it would trigger McAfee on panthercules machine and not trigger ZoneAlarm pro on mine? Of course, the answer to that may fall into the "Twilight Zone" category  |
It's simply down to McAfee and .NET not playing well together "out of the box".
The key connection was the P9 description and panthercules (fortunately) mentioning McAfee. I remember a user having a similar problem over a year ago (seems things haven't changed since then
)! Unfortunately, short of disabling the firewall, I can't remember what changes the client can make in their firewall to get the two playing again (I use ZA as well).
McAfee Firewall is just more sensitive I guess. Much like Avasti! virus scanner is more sensitive than pretty much any other too.