p2pRemote

Documentation

p2pRemote Core Usage Guide

Follow the complete first-use flow from installation and sign-in through tunnel creation, virtual-IP use, and disconnection. Use one account for your own devices; use a connection code and one-time password to connect to someone else's device.

Prepare and install

The controller initiates access; the remote device is the target. Install the supported client from the official site on both endpoints.

  • Allow the background service and virtual networking components.
  • Use unique, recognizable device names.
  • Keep automatic time enabled and prevent unattended targets from sleeping.
  • Enable the target service, such as RDP or file sharing.

Sign in and identify devices

For your own devices, sign in to the same account on both. To connect to someone else's device, use their connection code and one-time password instead of sharing accounts.

  1. Open Devices and locate This device and the target.
  2. Teal means online, a green link means connected, and gray means offline.
  3. Verify the target name and system details.

Note: Android can initiate a tunnel but cannot currently accept one as the passive endpoint.

p2pRemote device list showing local, online, connected, and offline states
Identify the local device and each connection state.

Create the tunnel

  1. Select the online target.
  2. Verify its identity in device details.
  3. Choose Create Tunnel.
  4. Wait for network detection, peer coordination, traversal, and virtual-address setup.
  5. Continue only after the state reads Connected.
Create Tunnel action in p2pRemote device details
Select an online target and create the tunnel.

Copy the peer virtual IP

Use the peer virtual IP, not the local virtual IP or router public address, in the remote application.

  • RDP: mstsc /v:<peer-virtual-ip>
  • SMB: \\<peer-virtual-ip>\<share-name>
  • SFTP: peer virtual IP, normally port 22
  • Other services: peer virtual IP and actual service port
Connected p2pRemote device with peer virtual IP actions
Copy the peer virtual IP after the tunnel connects.

Verify the tunnel and service

The tunnel supplies reachability but does not start RDP, SMB, SSH, or FTP on the target.

ping <peer-virtual-ip>
Test-NetConnection <peer-virtual-ip> -Port 3389
Test-NetConnection <peer-virtual-ip> -Port 445
Test-NetConnection <peer-virtual-ip> -Port 22

Note: A failed ping may only mean ICMP is blocked. Test the actual service port.

Disconnect after use

  1. Save work in the remote application.
  2. Close application sessions.
  3. Choose Disconnect Tunnel in device details.
  4. Confirm that the device returns to online but disconnected.

Security checklist

  • Use strong passwords for remote accounts.
  • Enable only the services and firewall rules you need.
  • Do not leave the entire firewall disabled.
  • Share only required folders with least-privilege permissions.