Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Dameware Remote Support & Mini Remote Control > DameWare - Knowledgebase Articles > Troubleshooting the Connection Refused Message in Dameware Mini Remote Control - TCP/IP Error 10061

Troubleshooting the Connection Refused Message in Dameware Mini Remote Control - TCP/IP Error 10061

Table of contents

Updated: September 21, 2017


10061 is a TCP/IP error that implies there is a TCP/IP connectivity issue between the local and remote machines. Here is a possible method of troubleshooting the 10061 error in regard to the Mini Remote Control Service.


  • Dameware Mini Remote Control


Please make sure that you have administrative rights to the remote workstation. 


Reset the default TCP port usage(6129) on both local and remote workstations.

Within DWMRC, select the desired host entry and click on the Settings button. On the Remote Options Tab, verify that the Port number is set to 6129 (must match the Remote Client Agent Service port exactly).


To ensure the default port usage(6129) on the remote workstation:

  1. Back up your registry.
  2. Stop the DameWare Remote Client Agent Service.
  3. Delete DWRCS.INI from the system32 directory.
  4. Delete the registry entry for the client agent HKEY_LOCAL_MACHINE\SOFTWARE\DameWare Development\DWRCS. 
  5. Restart the service.

Other things to consider:

  1. There may be some other application using the same port. Stop the service on the remote machine and run "netstat -a". There should be nothing listening on port 6129. If there is, then something else is using the port. If not, then restart the service on the remote machine and you should have something (DMRC) listening on port 6129.
  2. If we have verified Step 1 and you get to this point with no resolution, then there must be a Microsoft name resolution/routing problem, because we can query and install a service using the installed protocol via Windows API but we can't communicate with the computer using plain TCP/IP via sockets. This means there is a problem with your network setup. You should be able to duplicate this problem outside of the DNTU/Mini Remote Control software. 
    1. Verify the IP address and hostname on the remote computer are correct.
    2. Attempt to map to a shared resource on the remote computer. If it fails, then resolve any network connectivity problems, and try the Mini Remote Control again.




Last modified