Tools

No DameWare MRC Access to remote computer when using VPN

This article provides brief information and steps to resolve issues when accessing a machine via MRC.

First published date

10/10/2018 2:19 PM

Last published date

10/10/2018 2:33 PM

Overview

This article provides brief information and steps to resolve issues when accessing a machine via MRC.

Product section

Dameware Remote Support & Mini Remote Control

Cause

The issues are caused by Windows permissions, firewall ports or Client configurations.

Is the MRC Client Agent Service already installed and running on this remote machine?

Although only a single TCP port is required to establish a MRC connection (provided the Service is already installed and running on the remote machine), other ports are required by the O/S to remotely install, remove, start, or stop the MRC Client Agent Service (or any Service), such as File & Printer Sharing.

Microsoft defines File & Printer Sharing as:

UDP 137 (Name),
UDP 138 (Datagram),
TCP 139 (Session),
TCP 445 (DirectHosting of SMB over TCP).

Resolution

See if you can access the Admin$ share of the remote machine

Open Computer or Run and then type: \\IP-Address\Admin$.

If you cannot access this remote machine via your O/S, then you will have to pre-install the MRC Client Agent Service on the remote machine before you will be able to connect.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.