<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic AirWatch Connector DC Issue in Workspace ONE Discussions</title>
    <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/AirWatch-Connector-DC-Issue/m-p/2981781#M19131</link>
    <description>&lt;LI-SPOILER&gt;&lt;LI-SPOILER&gt;&amp;nbsp;&lt;/LI-SPOILER&gt; &lt;/LI-SPOILER&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We have receiving the following issue , when we trying to connect the AirWatch connector to one of our domain controller, which are in trust.&lt;BR /&gt;We are receiving the following error:&lt;/P&gt;&lt;P&gt;2023/08/10 11:13:08.166 ****** 51e1a72f-b14c-451d-9d96-be1cd2e1ed26 [0000000-0000000] (9) Error System.Type.TestConnection Directory call failed. System.DirectoryServices.Protocols.LdapException: Error code:81 User Name:***** Error Details:Server is not reachable*** EXCEPTION ***&lt;BR /&gt;System.DirectoryServices.Protocols.LdapException: The LDAP server is unavailable. at System.DirectoryServices.Protocols.LdapConnection.Connect()&lt;BR /&gt;at System.DirectoryServices.Protocols.LdapConnection.BindHelper(NetworkCredential newCredential, Boolean needSetCredential)&lt;BR /&gt;at AirWatch.CloudConnector.DirectoryService.DirectoryService.ConnectLdap(LdapDirectoryIdentifier ldapDirectoryIdentifier)&lt;BR /&gt;at AirWatch.CloudConnector.DirectoryService.DirectoryService.CreateLdapConnection()&lt;BR /&gt;at AirWatch.CloudConnector.DirectoryService.DirectoryService.TestConnection(TestDirectoryConnectionRequest testConnectionRequest)AW_Logging_Exception_Logged:True;AW_Logging_Exception_Data_Count:1;AW_Logging_Exception_Log_Message:Directory call failed. System.DirectoryServices.Protocols.LdapException: Error code:81 User Name:**** Error Details:Server is not reachable;Diagnostics Context&lt;/P&gt;&lt;P&gt;We have checked our firewalls and the connector have access to the specified DC.&lt;BR /&gt;Could you please suggest some steps to remediate the issue?&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;</description>
    <pubDate>Thu, 10 Aug 2023 13:33:52 GMT</pubDate>
    <dc:creator>mnanev</dc:creator>
    <dc:date>2023-08-10T13:33:52Z</dc:date>
    <item>
      <title>AirWatch Connector DC Issue</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/AirWatch-Connector-DC-Issue/m-p/2981781#M19131</link>
      <description>&lt;LI-SPOILER&gt;&lt;LI-SPOILER&gt;&amp;nbsp;&lt;/LI-SPOILER&gt; &lt;/LI-SPOILER&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We have receiving the following issue , when we trying to connect the AirWatch connector to one of our domain controller, which are in trust.&lt;BR /&gt;We are receiving the following error:&lt;/P&gt;&lt;P&gt;2023/08/10 11:13:08.166 ****** 51e1a72f-b14c-451d-9d96-be1cd2e1ed26 [0000000-0000000] (9) Error System.Type.TestConnection Directory call failed. System.DirectoryServices.Protocols.LdapException: Error code:81 User Name:***** Error Details:Server is not reachable*** EXCEPTION ***&lt;BR /&gt;System.DirectoryServices.Protocols.LdapException: The LDAP server is unavailable. at System.DirectoryServices.Protocols.LdapConnection.Connect()&lt;BR /&gt;at System.DirectoryServices.Protocols.LdapConnection.BindHelper(NetworkCredential newCredential, Boolean needSetCredential)&lt;BR /&gt;at AirWatch.CloudConnector.DirectoryService.DirectoryService.ConnectLdap(LdapDirectoryIdentifier ldapDirectoryIdentifier)&lt;BR /&gt;at AirWatch.CloudConnector.DirectoryService.DirectoryService.CreateLdapConnection()&lt;BR /&gt;at AirWatch.CloudConnector.DirectoryService.DirectoryService.TestConnection(TestDirectoryConnectionRequest testConnectionRequest)AW_Logging_Exception_Logged:True;AW_Logging_Exception_Data_Count:1;AW_Logging_Exception_Log_Message:Directory call failed. System.DirectoryServices.Protocols.LdapException: Error code:81 User Name:**** Error Details:Server is not reachable;Diagnostics Context&lt;/P&gt;&lt;P&gt;We have checked our firewalls and the connector have access to the specified DC.&lt;BR /&gt;Could you please suggest some steps to remediate the issue?&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;</description>
      <pubDate>Thu, 10 Aug 2023 13:33:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/AirWatch-Connector-DC-Issue/m-p/2981781#M19131</guid>
      <dc:creator>mnanev</dc:creator>
      <dc:date>2023-08-10T13:33:52Z</dc:date>
    </item>
    <item>
      <title>Re: AirWatch Connector DC Issue</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/AirWatch-Connector-DC-Issue/m-p/2986054#M19149</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5637067"&gt;@mnanev&lt;/a&gt;&amp;nbsp;you have pinged or RDP from ACC to DC to confirm network connectivity? Have you nslookup the DC by name to confirm resolution back to IP? You can also enable debug logging as per info found in&amp;nbsp;&lt;A href="https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/WS1_Logging.pdf" target="_blank"&gt;https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/WS1_Logging.pdf&lt;/A&gt;&amp;nbsp;in the&amp;nbsp;VMware AirWatch Cloud Connector (ACC) section.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Sep 2023 22:39:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/AirWatch-Connector-DC-Issue/m-p/2986054#M19149</guid>
      <dc:creator>Phil_Helmling</dc:creator>
      <dc:date>2023-09-10T22:39:10Z</dc:date>
    </item>
  </channel>
</rss>

