I've been using ZAISS (7.0.462.000) and eMule .48 successfully for several months now on my PC running Windows XP Pro SP2, after initially battling to get it set up properly in ZAISS. A few days ago ZAISS seemed to 'reset' itself - when I booted my PC it told me that a 'new network' had been found. Everything else seems to work OK, but now eMule is complaining that UDP packets are not coming through. The expert rules I had previously setup to allow eMule to do its thing are still there. I certainly haven't changed them. Why can eMule now no longer connect properly?
Perhaps a more-important question at this point in time is, I have given eMule the highest trust level; I have given it complete internet access; I have given it server rights. Why do I have to mess around opening ports for it as well??? By giving eMule the highest level of trust, internet access and server rights, basically I'm telling ZAISS, "I trust eMule, let it do *whatever* it wants!" - why then can it not just get out of the way and let eMule function?? What is the point of giving a program server rights if it will not be allowed to act as a server? Alternatively, how can the allocation of server rights *not* include the opening of necessary ports??
If I am missing something here, please let know what it is. By the same token, if I have posed valid questions please can someone supply answers? In either case, I will be most grateful!
Thankyou for your time
Operating System:Windows XP Pro
Product Name:ZoneAlarm Internet Security Suite