Endpoint Protection

 View Only
  • 1.  OK to set SNAC service to Disabled?

    Posted Mar 16, 2009 02:29 PM

    I'm running SEP MR4 MP1, I've installed only the antivirus/antispyware component on my clients and servers.  By default, the Symantec Network Access Control (SNAC) service is set to "Manual", and is not running at bootup.  I've been having an issue when I access Windows 2003 servers via Remote Desktop and I install an application - sometimes during an install, I'm suddenly disconnected from the server, and I can't get reconnected.

     

    I finally spent some time troubleshooting this, and what I've determined is that during the install, the SNAC service is being started.  When it starts, I can't PING or connect to the server via RDP.  When I stop the SNAC service, everything goes back to normal.

    I'm not sure what is happening that's making SNAC suddenly start running when I am doing an application install, but the simplest solution I think is to set SNAC to "Disabled".  Anyone know of any reason why I shouldn't do this?

     

    Being disconnected from a remote server during an install is a very bad thing to have happen, especially when there's no way to reconnect.

     



  • 2.  RE: OK to set SNAC service to Disabled?

    Posted Mar 16, 2009 06:57 PM

    That should be fine, unless you are licensed for SNAC, there is no reason for it to run anyway. 



  • 3.  RE: OK to set SNAC service to Disabled?

    Posted Mar 17, 2009 09:22 AM

    Thanks for the reply Paul.  I am concerned about why the SNAC service would suddenly start while a third party app install is being run.  I think it's something that Symantec should know about, I suspect it's a bug.  Since it has the effect of locking out access to the box, it's a pretty serious bug when dealing with production systems, especially those that are remotely located.



  • 4.  RE: OK to set SNAC service to Disabled?

    Posted Mar 17, 2009 01:03 PM

    At times, I have seen the service start when other windows services start - in particular the Wireless Zero Configuration Service, so it could be related to that.

    What software seems to trigger it?