Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.


Home > Success Center > DameWare Remote Support & Mini Remote Control > DameWare Mini Remote Control User Guide > About DameWare Mini Remote Control > Troubleshoot your Central Server connection

Troubleshoot your Central Server connection

Table of contents
No headers
Created by Anthony.Rinaldi, last modified by Anthony.Rinaldi on Jul 11, 2016

Views: 28 Votes: 0 Revisions: 2

Before you can log on to the DameWare Central Server and use Remote Support or Mini Remote Control in centralized mode, the DameWare Central Server administrator must create an account for you to use and provide you with the Central Server information.

To log on you need the following information:

  • DameWare Central Server user name and password, if logging in with DameWare Authorization

  • IP address or host name of the DameWare Central Server

  • Port number used to communicate with the DameWare Central Server (by default, this is 6133)

Note: Use an IPv4 address or a hostname. If you must use an IPv6 address, you must add the address and host name to your host file. See KB 400151 for more information.

If you cannot logon to the Central Server and your user name and Central Server information are correct, you may have exceeded the number of licensed users or your account may be disabled. Contact your DameWare Central Server administrator to resolve this issue.

Each time you logon to DameWare Central Server from Remote Support or Mini Remote Control in centralized mode, you create a Central Server session. You can create multiple sessions from a single computer, but you cannot create sessions from different computers. If you open a second session from another Remote Support or Mini Remote Control console located on a different computer, your previous Central Server sessions are closed. Other reasons for your session to close include a Central Server administrator closing it or because you were idle for too long.

Last modified
13:57, 11 Jul 2016