Data Loss Prevention

 View Only
  • 1.  DLP v11.6 SharePoint 2010 scanning error

    Posted Jan 23, 2014 02:05 PM

    I am unable to scan our sharepoint dev after deploying the .WSP and checking scan user credentials with the below error:

     

    1/22/14 5:43:00 AM

    INFO

    Scan started

    1/22/14 5:43:00 AM

    INFO

    Started scanning Site: https://10.X.X.X:443/teams/test

    1/22/14 5:43:01 AM

    WARNING

    Failed to read https://10.X.X.X:443/teams/test; error: Host name on the server certificate does not match with host name of server. See the online Help for SSL certificate setup.

    1/22/14 5:43:01 AM

    WARNING

    Failed to complete Site: https://10.X.X.X:443/teams/test; error: Host name on the server certificate does not match with host name of server. See the online Help for SSL certificate setup.

    1/22/14 5:43:01 AM

    INFO

    Scan finished

     

    Imported SSL and enabled Discover.ValidateSSLCertificates:

    1/22/14 5:47:37 AM

    INFO

    Scan started

    1/22/14 5:47:37 AM

    INFO

    Started scanning Site: https://10.X.X.X:443/teams/test

    1/22/14 5:47:38 AM

    WARNING

    Failed to read https://10.X.X.X:443/teams/test; error: The Symantec DLP solution for SharePoint is not found on https://10.X.X.X:443. Verify the installation of the required solution on the Web Front End.

    1/22/14 5:47:38 AM

    WARNING

    Failed to complete Site: https://10.X.X.X:443/teams/test; error: The Symantec DLP solution for SharePoint is not found on https://10.X.X.X:443. Verify the installation of the required solution on the Web Front End.

    1/22/14 5:47:38 AM

    INFO

    Scan finished

     

    Again error persists

    1/22/14 5:58:19 AM

    INFO

    Scan started

    1/22/14 5:58:20 AM

    INFO

    Started scanning Site: https://10.X.X.X/teams/test

    1/22/14 5:58:21 AM

    WARNING

    Failed to read https://10.X.X.X.228/teams/test; error: The Symantec DLP solution for SharePoint is not found on https://10.X.X.X. Verify the installation of the required solution on the Web Front End.

    1/22/14 5:58:21 AM

    WARNING

    Failed to complete Site: https://10.X.X.X/teams/test; error: The Symantec DLP solution for SharePoint is not found on https://10.X.X.X.228. Verify the installation of the required solution on the Web Front End.

    1/22/14 5:58:21 AM

    INFO

    Scan finished

     



  • 2.  RE: DLP v11.6 SharePoint 2010 scanning error

    Broadcom Employee
    Posted Jan 24, 2014 04:46 AM

    So, it's said that the WSP solution is not installed at the Web Front End (WFE) server on the farm.

    Make sure you have finished the installation of the WSP.



  • 3.  RE: DLP v11.6 SharePoint 2010 scanning error

    Posted Jan 24, 2014 05:10 AM

    Hello,

    the error shown above is due to the fact that you are accessing the Sharepoint server through it's IP address instead of the hostname.

    You need to use the same hostname to be entered in the Scan Target for Sharepoint as was used to issue the Sharepoint SSL certificate.

    To get this right do the following:

    1. Use your browser to naviagte to Sharepoint using the IP address: https://10.X.X.X/teams/test
    2. The browser will most likely issue a warning, similar to the one seen in the logfile too
    3. Ignore this warning, continue to the web site
    4. Now click on the lock icon in the browsers address bar (firefox) or on the "certificate error" message in the address bar (IE)
    5. Select show certificate
    6. You will see a window showing you the details of the ssl certificate that sharepoint is using
    7. In the details, look at the hostname shown in "Issued to:" and use this address in the scan target configuration instead of the IP address


  • 4.  RE: DLP v11.6 SharePoint 2010 scanning error

    Posted Jan 24, 2014 08:58 AM

    Errors continue:

    ------------------------------------------------------------

    1/24/14 7:06:25 AM INFO Scan started
    1/24/14 7:06:25 AM INFO Started scanning Site: https://sX.Xa.com:443/teams/test
    1/24/14 7:06:25 AM WARNING Failed to read https://sX.Xa.com:443/teams/test; error: Unable to resolve https://sX.Xa.com:443. Verify if the host name is valid.
    1/24/14 7:06:25 AM WARNING Failed to complete Site: https://sX.Xa.com:443/teams/test; error: Unable to resolve https://sX.Xa.com::443. Verify if the host name is valid.
    1/24/14 7:06:25 AM INFO Scan finished

    ------------------------------------------------------------

    1/24/14 7:05:20 AM INFO Scan started
    1/24/14 7:05:20 AM INFO Scan started
    1/24/14 7:05:20 AM INFO Started scanning Site: https://sX:443/teams/test
    1/24/14 7:05:20 AM WARNING Failed to read https://sX:443/teams/test; error: Unable to resolve https://sX:443. Verify if the host name is valid.
    1/24/14 7:05:20 AM WARNING Failed to complete Site: https://sX:443/teams/test; error: Unable to resolve https://sX:443. Verify if the host name is valid.
    1/24/14 7:05:20 AM INFO Scan finished

    ------------------------------------------------------------

    It appears that we have wild card in the cert:

    SharePointCert.png



  • 5.  RE: DLP v11.6 SharePoint 2010 scanning error

    Posted Jan 31, 2014 05:36 AM

    error: Unable to resolve https://sX:443. Verify if the host name is valid.

    means that the DLP scanner server cannot resolve the hostname to an IP address. Please try to open the URL https://sX.Xa.com:443/teams/test with Internet Explorer on your scanner host.

    It seems as if the DNS server configured at the scanner host cannot resolve this hostname so you might need to add it to the local "hosts" file on the scanner server in c:\windows\system32\drivers\etc.

    Open the hosts file with a text editor and enter a new line in the format

    xxx.xxx.xxx.xxx  sX.Xa.com

    where xxx.xxx.xxx.xxx is the IPv4 address of the server with the name sX.Xa.com



  • 6.  RE: DLP v11.6 SharePoint 2010 scanning error
    Best Answer

    Posted Feb 18, 2014 11:54 AM

    Issue was resolved.

     

    Client was presenting certificate which was pointing to the root domain, but their sharepoint is about 4 children domains down.

     

    When we testing we another sharepoint server which had the root domain, it worked with no issues.