Sign in
Microsoft.com
 
Resources for IT Professionals
 
 
 
Resources for IT Professionals > Forums Home > Windows Home Server Forums > Windows Home Server Software > NOD32 AV and Shared Folders permissions...
Ask a questionAsk a question
Search Forums:
 

QuestionNOD32 AV and Shared Folders permissions...

  • Tuesday, July 10, 2007 5:51 AMLang Murphy Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    I read in some guy's blog that he thought NOD32 (client, not server) was the best AV solution available for WHS right now. Since I was going to activate remote access, I figured it would be irresponsible not to have an AV program installed, so I d/l'ed NOD32 (trial version) last week and installed it. Activated remote access, hit the road, and remote access worked great this past week.

     

    Just got home tonight... was having all kinds of problems accessing shared folders. Couldn't hit them from the client seats... was getting permission error. Even got permission error logged on locally to WHS when trying to access shared folders. WTF?

     

    Uninstalled NOD32... and... problem went away. Hmm...

     

    The Welcome Mat is out for comments / suggestions!

     

    Lang

     

All Replies

  • Tuesday, July 10, 2007 6:00 AMLang Murphy Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    So... that said... what AV are y'all using on WHS? Don't care much for Symantec or McAfee...

     

    Lang

     
  • Tuesday, July 10, 2007 6:01 AMS_M_E Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I've had good luck with Symantec Corp AV. NOD32 is a good AV solution, I'm actually surprised that it conflicted somehow.

    *shrug*

     
  • Tuesday, July 10, 2007 6:26 AMLang Murphy Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Yes, I, too, was surprised. I must admit that I didn't dig very deep into the issue... just uninstalled NOD32. Since that appeared to fix the problem, I must assume NOD32 was the source of the problem. Sigh... now I have to go off and investigate other AV solutions. I'm not a big fan of SAV... it's generally acknowledged to be a resource hog. But then, that's on the client side, not the server side... don't know how much SAV for servers costs... I would guess "a pretty penny."

     

    Thanks for the reply!

     

    Lang

     
  • Tuesday, July 10, 2007 2:12 PMplayadru182 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I had the same problem. Uninstalled and things are working great now.  I hope they can get this fixed.
     
  • Tuesday, July 10, 2007 4:40 PMLang Murphy Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Well, glad to hear I'm not the only one experiencing this problem. Also sorry to hear I'm not the only one experiencing this problem. Guess I have to go find the blog that recommended NOD32 and report on our experiences with it on WHS.

     

    Thanks!

     

    Lang

     
  • Tuesday, July 10, 2007 8:51 PMPhilip ChurchillMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Thanks Lang Murphy,

    My orignal blog post you quoted was More Anti-Virus Software for WHS.

     

    I have spoken to ESET technical support who said that they have not tested NOD32 on WHS yet, so have no idea why this is happening. They will be testing it before WHS goes RTM but say that since home server is based on Windows Server 2003 it should work fine which naturally it isn't.

     

    Other AV products can be found at the link with pricing etc and in the meantime any ideas why this is happening anyone?

     

     

     

     
  • Saturday, September 01, 2007 6:36 AMFreight77 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    As the RTM version of WHS is upon us. Has anyone tried a newer version of NOD32 lately or heard any news from ESET? I would love to install NOD32 in WHS instead of any other antivirus program.
     
  • Thursday, September 06, 2007 4:46 AMTheDude42 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I got a similar problem (couldn't access shares from client pcs after a while). I think it was after installing NOD32. I have just untinstalled it, and will report back after I've used it for a few hours.

    EDIT:
    Confirmed. Uninstalled NOD32. Everything's fine now.
     
  • Tuesday, October 09, 2007 6:38 PMDDanster Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Just tried to run this issue up the flagpole at NOD32, since WHS is shipping and I'm a paying NOD32 customer...

     

    Here was their reply:

     

    Hello,

    There are no known issues in regards to running the current version of NOD32 on a Windows Home Server version of Windows. It is basically a very stripped down version of Server 2003.

    As it is not recommended to enable the IMON module when installing NOD32 onto a server (some system instability may occur), please disable IMON to see if this is what is causing the issue. Since AMON is still running, you will not be compromising any protection on your machine.

    If you have additional questions with regards to your case please let us know by replying to this email.

    Thank you for using NOD32,
    ESET Customer Care


    Anyone had similar experiences?

     

     

     

     
  • Wednesday, October 10, 2007 3:00 PMTommyD Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Had the same problem (see my previous post).
    Tried their suggestion of disabling IMON and that didnt help.
    I also disabled everything else (AMON, IMON etc) and still the same problem.
     
  • Wednesday, October 10, 2007 5:34 PMColinWH Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    They seem to have a very different idea about what constitutes WHS, than AVG have!

    When I was talking to them, they said that although it's based on W2k3 Server, there were numerous changes and they were having to re-write a large portion of their server product to work correctly on WHS.

    Microsoft did say early on, that anti-virus vendors were working on compatable versions, to be available at RTM. That implys that 'standard' versions may well not work correctly.

     

    Colin

     
  • Friday, October 19, 2007 8:59 PMregispabx Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

      Preciso atualizar meu anti v´rus nod32 gratuito....