Endpoint Encryption

 View Only

  • 1.  Symantec Endpoint Encryption Active Directory Sync Service: Stopped

    Posted Sep 20, 2010 09:01 PM

    Hi, I am using SEE v7.02. My SEE ADSync services unable to start if I enable Active Directory Synchronization mode. I did try to use the domain admin but still unable to start the services. I appreciate if someone can help me on this?

     

    Richard



  • 2.  RE: Symantec Endpoint Encryption Active Directory Sync Service: Stopped

    Posted Sep 21, 2010 01:57 AM

    HI,

    Try check your Sql server logs. The logs should full. Do schedule to purge the logs file. After backup the logs, the services will start.

    Regards,



  • 3.  RE: Symantec Endpoint Encryption Active Directory Sync Service: Stopped

    Posted Sep 21, 2010 03:35 AM
    Has it just started happening or since install? Any errors in the windows event log about it?


  • 4.  RE: Symantec Endpoint Encryption Active Directory Sync Service: Stopped

    Posted Sep 21, 2010 09:44 PM

    Hi,

    I encounter this problem since the beginning so it has been never successfully sync with AD.

    I did try to increase the SQL server log but no luck...



  • 5.  RE: Symantec Endpoint Encryption Active Directory Sync Service: Stopped

    Posted Sep 22, 2010 03:31 AM
    Anything in the event logs when you try to start it? I noticed in 7.0.3 the AD settings are more comprehsive - you're asked to specificy the global catalog server for example.


  • 6.  RE: Symantec Endpoint Encryption Active Directory Sync Service: Stopped

    Posted Sep 22, 2010 05:14 AM
      |   view attached

    Hi ukDavidC,

    Thanks for your respond. The screen does prompt "Unable to connect to the Active Directory Global Catalog Server". if  I set e.g. Active Directory Forest Name: rootdomain.com and User Domain: child.rootdomain.com.

     



  • 7.  RE: Symantec Endpoint Encryption Active Directory Sync Service: Stopped

    Posted Sep 22, 2010 06:50 AM

    Looks like they changed the way global catalog works betwen 7.0.2 and 7.0.3. You might need to contact support for the information if you can't upgrade. The docs say that your SEE server needs to be in the same network as a GC. Otherwise, any firewalls or anything on the server that might be blocking communications? The documentation says port 3268.