Knowledge Center

The Data Exchange Layer Client cannot connect to the DXL Broker
Technical Articles ID:   KB89060
Last Modified:  11/29/2018


McAfee Data Exchange Layer (DXL) 2.x, 3.x

Symantec Drive Encryption
Other third-party vendor applications


The DXL Client is successfully installed but cannot connect to the DXL Broker, even though there are no connectivity problems or any other issues in the DXL logs.


This is caused by a third-party vendor application injecting a DLL into McAfee services; for example, Symantec Drive Encryption.

You can use Process Explorer to see which DLLs are injected into any given process. For the DXL client it would be dxlservice.exe, and also any service starting with mfe.


If Endpoint Security 10.5 or higher is installed, these DLLs should be listed under the policy Endpoint Security Common in the Certificates section.

NOTE: This section is only visible if Show Advanced has been selected.

These DLLs must be selected to allow our internal kernel driver to whitelist them, so that the DXL client can successfully connect to the fabric (because the DXL client is also using our internal kernel driver).


If the DLLs are not listed under the Common policy, or unsigned DLLs are injected:
  1. Go to the DXL Client policy and de-select the Self Protection option.
  2. Enforce the new policy on the affected machines.
  3. Open Task Manager and terminate the dxlservice.exe process.

    It will restart after five seconds and will then be able to reconnect to the DXL Broker because it is no longer using the internal kernel driver.

Alternatively, a system restart achieves the same result as terminating the process.

Rate this document

Beta Translate with

Select a desired language below to translate this page.


This article is available in the following languages:

English United States
Spanish Spain

Glossary of Technical Terms

 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.