Direct Connect failure to connect

Last Modified

Wed Nov 30 21:43 GMT 2016

Description

Connection issues occur with Direct Connect.

Environment

  • N-able N-central 9.x and higher.

Solution

If you are experiencing connection issues with Direct Connect, it may be due to an invalid plugin as NTR has updated their signed certificate which now requires a new ActiveX or NPAPI plugin to be installed.

  1. Clear the cache.

On the Operator side (your computer):

  • Windows XP: C:\Documents and Settings\LocalService\Application Data\ntr
  • Windows 7 (32-bit): C:\Windows\System32\config\systemprofile\AppData\LocalLow
  • Windows 7 (64-bit): C:\Users\*user*\AppData\LocalLow\ntr
  • Windows 8: C:\Users\*user*\AppData\Local\Temp\Low\ntr

Other possible locations on Windows 8:

  • C:\Users\{USERNAME}\AppData(hidden folder)\LocalLow\ntr
  • C:\Users\{USERNAME}\AppData(hidden folder)\Local\Temp\Low\ntr\
  • C:\Users\{USERNAME}\AppData(hidden folder)\Local\Temp\ntr\
  • C:\Users\{USERNAME}\AppData(hidden folder)\Local\ntr\
  • C:\Users\{USERNAME}\AppData(hidden folder)\Roaming\ntr\

On the target side (the device you are trying to connect with):

  • C:\Program Files (x86)\N-able Technologies\Windows Agent\Temp\ntr\*.txt
  • C:\Program Files (x86)\N-able Technologies\Windows Agent\Temp\ntr\*.log
  1. If clearing the browser cache does not fix the issue, you will need to install the older NTR plugin before you can launch any remote control.
    To download the older NTR plugin, click here:https://app.ntrglobal.com/plugin/chrome.
  2. You may need to enable the NPAPI Plugins in Chrome:

How to enable NPAPI Plugins in Chrome v42+:

  1. In the Chrome browser, type "Chrome://flags".
  2. In the list, search to locate Enable NPAPI.
  3. Click Enable.
  4. Relaunch Chrome.