odd to me the program does not update itself, only dat files. still poking fp
At 06:44 AM 3/14/2008, DHSinclair Poked the stick with: >You may wish to snoop around in the Wilders forums. It is the official support >forum for all things nod32. JMHO, but eset has their hands full with both the >new V3.0 A/V and their new V3.0 Security Suite (V3 A/V+Firewall). And, their >new V3 Business Edition (Enterprise) is having its' own set of growing pains. >A speed-bump for sure............ :) >http://www.wilderssecurity.com/index.php >The nod32 forums (5) are the first block below the general/announcement/test >topics. >You will also find support forums for many other things; many used here on the >list! > >It could be that the background nod32 services do not have free access to the >internet to phone home to the eset servers for updates. I think nod32 trys to >connect every 60 minutes by default. > >Not sure your version of nod32 v3.0 A/V is completely up to date; the latest >version at eset is 3.0.642. > >In any case, V3.0 now uses an internal proxy server to do it's business. It >does not tie itself into the tcp/ip stack like V2.7 does. This may be part of >the glitch. Are your sure you completely removed all parts and pieces of a >previous A/V. Nod32 is now sensitive to old A/V remnants (particularly >Kaspershy and Symantec). Perhaps the initial install did not complete >properly. I am not fluent with the new V3.0 A/V program, but answers should >be found here: >http://www.wilderssecurity.com/forumdisplay.php?f=88 >or here: >http://www.wilderssecurity.com/showthread.php?t=197509 > >There seems to still be some concern about how to get the older V2.7 nod32 A/V >in the trial wrapper. I think I still have it, and can upload it to your ftp >to try if necessary. But, WinXP sometimes choked on V2.7 also. Something >about how MS "improved" the tcp/ip stack processing in XP. I have not noticed >any trouble with my XP machine at all w/V2.7, however. > >I'll keep digging around and see if I can find some more clues. Nod32 on Vista >is a horse of another color yet again. >Hope some of this helps, >Duncan > > >At 21:15 03/13/2008 -0700, you wrote: >>Aw yes, more info. >>nod32 3.0.620.0 >> >>only turned it off in it's control panel. Suppose I could log in in safemode >>with networking and see WTF >> >>nod32 running on xp pro, server is vista ultimate. Been fussing with this >>today. only using windows fw. nod is AV only but does have some net >>filtering. As of yet unable to make it go. Final answer would be to just >>uninstall it and see what's up I guess. >> >>FWIW vista shows office but will not connect. Also seems to come and go in my >>netgear router. at the moment that MAY be suspect also but doubt it. Do have >>another router I can try tomorrow. I can ping vista from xp but not xp from >>vista. Network was fine b4 installing nod32 afaik. >> >>fp >> >>thanks >> >>At 08:13 PM 3/13/2008, DHSinclair Poked the stick with: >>>A bit hard to tell w/o some more detail. Which machine did you put nod32 >>>on? Which version of nod32? Does the machine w/nod32 also have a firewall >>>also? >>>How did you "turn nod32 off"? Its' background services are probably still >>>running....... :) >>>More input...... :) >>>Best, >>>Duncan >>> >>>At 15:40 03/13/2008 -0700, you wrote: >>>>Recently installed nod32 AV to play with. Have lost LAN connection from >>>>server to office yet I can still access server no problem from the office. >>>> >>>>Can nod32 do this ? turning it off has no affect >>>> >>>>thanks >>>>fishing >>>>fp >>>> >>>>-- >>>>Tallyho ! ]:8) >>>>Taglines below ! >>>>-- >>>>Those without heads do not need hats. >> >>-- >>Tallyho ! ]:8) >>Taglines below ! >>-- >>People say I'm indecisive, but I'm not so sure. -- Tallyho ! ]:8) Taglines below ! -- People say I'm indecisive, but I'm not so sure.
