Submit a ticketCall us

Cloud Workloads: Meet Your New Hybrid IT Reality
Have you found yourself in that evolving, hybrid IT grey area and wondering if cloud workloads are now part of your purview? And if so, will monitoring cloud workloads require a new set of dedicated cloud monitoring tools? Your answers: yes, they should be, and no, they don’t.

Find out how SolarWinds® Server & Application Monitor (SAM) can help you monitor your cloud workloads side by side with your on-premises workloads. Register Now.

Home > Success Center > DameWare Remote Support & Mini Remote Control > DameWare Documentation > Dameware Remote Support and Mini Remote Control Documentation - Previous Versions > DameWare Mini Remote Control User Guide > Additional information and instructions > IPv6, PNRP, and Clouds

IPv6, PNRP, and Clouds

Created by Anthony.Rinaldi_ret, last modified by Anthony.Rinaldi_ret on Jul 11, 2016

Views: 59 Votes: 0 Revisions: 3

DameWare Mini Remote Control supports the latest Internet Protocol, IPv6, and features that utilize it. In short, this means that a Mini Remote Controluser can use an IPv6 address to establish a Mini Remote Control connection to a remote system. The following components also utilize/support IPv6 technology:

  • Mini Remote Control Connection Invitations

  • MRC Peers list (Remote Connect browser pane)

  • PNRP Peers (Remote Connect browser pane)

Additional Information

Microsoft designed the Peer Name Resolution Protocol (PNRP) as a peer-to-peer protocol that enables dynamic name publication, registration, and resolution. This functionality requires IPv6. Mini Remote Control takes full advantage of the PNRP technology within the Windows operating systems, which allows a system to register its peer name and IP Address in a PNRP Cloud.

A PNRP Cloud is a group of systems that are able to resolve each other???s registered PNRP names within a network. There are three main Clouds, or scopes:

  • Global: The global IPv6 scope and represents all systems on the entire IPv6 Internet. There is only one global cloud.

  • Link-Local: Typically the same as the locally attached subnet. A system with PNRP enabled joins a Link-Local cloud for every Link-Local address present on it, so there are usually multiple Link-Local clouds.

  • Site-Local: Deprecated. It is not likely that you will encounter this cloud.

Utilizing IPv6

In theory, if a Windows system has a Global IPv6 address, peer-to-peer (p2p) applications can communicate with any other Windows system because PNRP can resolve the IP address.

To determine which clouds are available and their state, run the following command from a Command Prompt:

NETSH P2P PNRP CL SH ST

The Mini Remote Controlclient agent service also detects the availability and state of the clouds and lists them in the About information dialog of the Service (right-click the Mini Remote Control SysTray icon, and then select About.). Also, you can configure the Mini Remote Control client agent service to register a Local or Global PNRP name (see "Teredo - PNRP" in MRC Client Agent Service settings). If you do not select any options on the Teredo - PNRP tab in the Mini Remote Control client agent service settings, the agent does not register any PNRP names, and the system will not be displayed in the PNRP Peers list in the Remote Connect browser pane.

Note: The PNRP Peers list in the Remote Connect browser pane only applies to registered Link-Local PNRP Peers.

The status of the Clouds available to your system are typically denoted as one of the following:

  • Active: The cloud is healthy and accessible. You can register and publish PNRP names as well as resolve them.

  • Alone: The cloud is accessible by you (or your machine), but not connected to any other nodes and therefore you will not be able to resolve peers in this cloud. It can be normal at times for the Link-Local clouds to be in the Alone state.

  • Virtual: A Virtual cloud state indicates that a PNRP cloud was created but not used and therefore was suspended after 15 minutes of inactivity. If no PNRP names have been registered and nothing is resolving any other names, the virtual cloud state is expected.

IPv6 and Older Operating Systems

When native IPv6 connectivity is not available, such as when using older operating systems, Mini Remote Control can still use the new technology thanks to the transition technology called Teredo. Teredo is a technology that tunnels IPv6 over IPv4 and is included in Windows Operating Systems.

To check the Teredo state of the operating system and subsequently to determine if the system can use an IPv6 address, run the following command from a Command Prompt:

Windows Vista and above: NETSH int teredo sh st

Teredo addresses are IPv6 addresses. Therefore, the Mini Remote Control client agent service can use Teredo addresses to create Mini Remote Control invitations and connect to remote systems. For additional information about how to create Mini Remote Control invitations, see Create Invitation dialog.

Last modified

Tags

Classifications

Public