p2pRemote

Troubleshooting

p2pRemote Connection Troubleshooting Checklist

First determine whether the failure occurs during device sign-in, tunnel creation, or application access. Change one variable at a time and record the result.

Identify the failure stage

  • Offline: the target is gray and a tunnel cannot be started.
  • Traversal failure: the target is online but tunnel creation fails.
  • Application failure: the tunnel connects but RDP, SMB, or SFTP fails.
  • Interruption: a working connection enters reconnecting or disconnects.

Note: Classifying the stage prevents an RDP configuration issue from being mistaken for NAT traversal failure.

The device is offline

  1. Verify sign-in with the same account.
  2. Keep the target awake and confirm the background service is running.
  3. Synchronize system time and time zone.
  4. Try another network to isolate DNS, proxy, or enterprise restrictions.
  5. Refresh the list and remove only genuinely stale device records.

The tunnel cannot connect

  1. Update both endpoints to compatible versions.
  2. Cancel and retry once.
  3. Check firewalls, security software, VPNs, and virtual adapters.
  4. Inspect both paths for double NAT or CGNAT.
  5. Move one endpoint to a hotspot for comparison.
  6. Collect matching logs from both endpoints.

The application cannot connect

  1. Use the peer virtual IP.
  2. Ping for a basic check, but still test the service port if ping fails.
  3. Run Test-NetConnection against the service port.
  4. Verify that the target service is listening beyond 127.0.0.1.
  5. Check inbound firewall and account permissions.
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

Interpret port tests

  • True: the path and port are reachable; inspect protocol, certificate, and credentials.
  • False: inspect the target listener, port number, and firewall.
  • Ping works but the port fails: the tunnel likely works and the application service is the problem.
  • Everything fails: recheck the copied address, tunnel state, and virtual-adapter route.

Frequent interruptions

  • Disable sleep and adapter power saving on the target.
  • Avoid changing Wi-Fi, VPN, or mobile networks mid-session.
  • Check router reconnects, short UDP timeouts, and packet loss.
  • Prefer Ethernet over weak Wi-Fi.
  • If only heavy transfers fail, reduce concurrency and inspect link quality.

Include in a support report

  • Client and OS versions on both endpoints.
  • Failure stage, time, and reproduction steps.
  • Target service, port, and test result.
  • Network type, NAT layers, and hotspot comparison.
  • Matching logs with sensitive data redacted.