Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > DameWare Remote Support & Mini Remote Control > Dameware Remote Support and Mini Remote Control Getting Started Guide > Dameware Mini Remote Control actions > Dameware Mini Remote Control connection and authentication methods

Dameware Mini Remote Control connection and authentication methods

Table of contents
No headers

Updated: June 30, 2017

This topic applies to:

  • Remote Support, centralized mode
  • Remote Support, stand-alone and evaluation modes
  • Mini Remote Control, centralized mode
  • Mini Remote Control, stand-alone and evaluation modes

The Mini Remote Control application connects to the client agent service using a direct TCP connection from the application to the client agents. Although this method may not be as convenient as establishing a VPN or SSL con-nection to a LAN, for many users it provides a necessary means of providing remote support for customers or administration for remote machines not on a LAN.

Dameware Mini Remote Control supports the following connection methods:

Connection Method DescriptionAuthentication Methods

Use MRC Viewer

Connects to the MRC agent installed on the remote Windows machine. If an agent is not installed on the remote machine, it is installed during the connection.

Proprietary Challenge / Response: This authentication method works by having a custom proprietary User Name and Password defined in the set-tings of the Mini Remote Control client agent service on the remote system. The User Name and Password are stored in encrypted format in the Registry of the remote system.

Windows NT Challenge / Response: This authentication method uses the integrated security of the Windows operating system to connect to a remote system.

Encrypted Windows Logon: The Encrypted Windows Logon is similar to the Windows NT Challenge / Response authentication method except that it sends the User Name and Password to the remote system in an encrypted format. This authentication method is designed primarily for situations where NT Challenge / Response authentication is not possible, or fails. Examples of these situations include when Domain Controllers have been configured to disallow anonymous connections, NT Challenge / Response has been disabled, or when using any of the Home versions of Windows Operating Systems.

Smart Card Logon: The Smart Card Logon provides a form of two-factor authentication that allows the Mini Remote Control user to authenticate to a remote system using a Smart Card and PIN at the local system without requiring a Smart Card reader at the remote system. This option works in conjunction with the Smart Card network implementation.

Use Remote Desktop (RDP)

Connects to the remote system using the Microsoft Remote Desktop Program. When you select this option, Mini Remote Control opens the RDP viewer within the Mini Remote Control application to connect to the remote system.


Use VNC Viewer (Linux or Mac)

Connects to a remote VNC server using the Remote Frame Buffer (RFB) protocol. Use this option to connect to Linux or Mac hosts.

For additional information about the operating systems Mini Remote Control supports for VNC connections, see VNC setup.


Use Intel AMT KVM

Connects to a remote Intel AMT KVM host using the Remote Frame Buffer (RFB) protocol. Use this option to connect to remote systems running on Intel vPro hardware.

This connection option requires the remote system to be set up to accept VNC connections. For additional information about setting up VNC servers, see VNC setup.


Last modified
10:17, 5 Jul 2017