Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > DameWare Remote Support & Mini Remote Control > DameWare Documentation > Dameware Administrator Guide > Configure Dameware Mini Remote Control to connect through a firewall

Configure Dameware Mini Remote Control to connect through a firewall

Updated: September 19, 2017

This topic describes how to change the default port number that Mini Remote Control and the Dameware client agent use to connect.

When you connect to a remote site, SolarWinds recommends that you install the client agent on the remote computer before you connect to it. When you install the client agent before you connect to the remote computer, you only need one port open in your firewall or router.

If you install the client agent when you first attempt to connect to the remote computer, you must open multiple ports to install the client agent and open the TCP port used to connect the application with the client agent. The client agent is installed using the same ports used to access shared resources, and due to security risks, SolarWinds does not recommend opening these ports on a perimeter firewall. The default TCP port for communication is 6129.

Microsoft documents the TCP ports required for connecting through a firewall. The ports depend on the Operating System version, the Network protocol installed, and how the network is configured.

Firewall configuration example:

The Windows 2007/2008 redirector and server components support Direct Hosting over Server Message Block (SMB) for communicating with other computers running these Operating Systems. Direct Hosting over SMB does not use NetBIOS for name resolution. DNS is used for name resolution and the Microsoft networking communication is sent directly over TCP without a NetBIOS header. Direct Hosting of SMB over TCP/IP uses TCP & UDP port 445 instead of the NetBIOS session TCP port 139. DNS Direct Hosting also uses port 445 (TCP and UDP).

By default, both NetBIOS and Direct Hosting are enabled on Windows 2007/2008, and both are tried in parallel when a new connection is established. The first to succeed in connecting is used for any given attempt. NetBIOS over TCP/IP support can be disabled to force all traffic to use TCP/IP Direct Hosting.

Change the default port number

To communicate, the Mini Remote Control application and the client agent must both use the same port number.

To change the port settings on the application:

  1. Open the Mini Remote Control application.
  2. Click View > Default Host Properties.
  3. Click Remote Options, and enter a port number.
  4. Click OK.

To change the port settings on the client agent:

  1. In the system tray, right-click the client agent, and select Properties.
  2. Click General, and enter a port number.
  3. Click OK.
Last modified


This page has no custom tags.