mberger wrote: > Since then I have added ffmpeg and socketwrapper to the list of > applications excluded from NOD32 content filtering and rebooted the > server computer. I still have the same result, and I have attached this > morning's debug log.
Years ago NOD32 had a bad reputation with regard to Socketwrapper especially as it did bad things to the MS protocol stack to provide its security. It is necessary to test whether NOD32 is the source of the problem or not and that can only be done by removing NOD32 and retesting - disabling does not work. NOD32 must be removed and system rebooted as when it is just disabled it used to leave code attached MS Protocol stack which messed up comms.. If you want - try disabling first and then repeat test. ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=103158 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
