Views:

The issue is caused by the improperly working DPI data channel despite its correct configuration.

To resolve the issue:

  1. Login to the DSM console.
  2. Go to Computers > Domain Controller.
  3. Click Intrusion Prevention Rules and click Assign/Unassign.
  4. Unassign the following IPS Rules:
    • 1005067 - Identified potentially harmful client traffic
    • 1005090 - Identified potentially harmful server traffic
  5. Save the changes.
  6. Login to Deep Security Virtual Appliance (DSVA) and run the following command to re-establish the IPS data channel:

    $>sudo stop ds_filter
    $>sudo rmmod vmxnet3
    $>sudo modprobe vmxnet3
    $>sudo /etc/init.d/ds_datachannel start
    $>sudo start ds_filter
    Then
    $>cd /dev
    $>ls

    You should see the vmxnet_eth2_shm character device.

  7. Restart the DSVA.