p2pRemote

File transfer

Use FTP, FTPS, or SFTP Through p2pRemote

p2pRemote provides the network path, while FTP, FTPS, or SFTP is still served by software on the target device. Prefer encrypted SFTP or FTPS where possible.

Choose a protocol

  • SFTP uses SSH and normally needs one port (22); it is the preferred option.
  • FTPS adds TLS to FTP but may still require a passive data-port range.
  • Plain FTP does not encrypt credentials or content.

Prepare the server

  1. Install and start the chosen server on the target.
  2. Create a dedicated user restricted to the required directory.
  3. Record protocol, port, username, and authentication.
  4. Add a narrow inbound firewall rule.
  5. For passive FTP/FTPS, configure and allow a fixed data-port range.

Connect

  1. Create the p2pRemote tunnel and copy the peer virtual IP.
  2. Create a site in FileZilla or another client.
  3. Use the virtual IP as host and retain the server's protocol, port, and credentials.
  4. Verify the SSH host-key fingerprint on first SFTP connection.
  5. Test permissions with a small file.
Host: <peer-virtual-ip>
Protocol: SFTP
Port: 22
Logon: password or key file

Troubleshoot

  • Test the control port with Test-NetConnection.
  • Make sure the service is not bound only to 127.0.0.1.
  • Check SSH logs or passive FTP data ports.
  • Verify both filesystem and server-level permissions.
  • Reduce concurrent transfers when large files fail.

Transfer safely

  • Prefer SFTP with key authentication.
  • Do not reuse an administrator password.
  • Grant only the required directory permissions.
  • Disconnect both the file client and tunnel after use.