Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Windows to Windows

How to install NoPorts when connecting from Windows to Windows

NoPorts version <5.13.0 should follow old instructions located here: Windows to Windows Legacy

Prerequisite

Before starting the NoPorts installation, ensure you have at least two atSigns available. If you don’t yet have any atSigns, you can sign up for a NoPorts subscription or free trial at my.noports.com/no-ports-plans.

Step 1 to Step 4

These initial steps set up the machine initiating the connection.

On the machine you are connecting from

In this installation guide, @example01_np will represent the client Atsign, while @example02_np will represent the device Atsign.

Step 1: Download and run the Installer

Download the msi installer from GitHub. You can run the msi right from the windows-bundle.zip.

Step 2: Client Atsign activation (@example01_np)

If you've already activated your client Atsign on another device, this step will not work. Instead, follow this guide: Reuse your client Atsign on another machine

Open a terminal (Command Prompt or PowerShell) and run the following commands. This command activates your Atsign and prompts you to enter an OTP. This is only done during the setup of a brand new Atsign.

Replace @<REPLACE>_np with your client Atsign.

at_activate.exe -a "@<REPLACE>_np"

Enter the one-time password (OTP) & Check your SPAM/PROMOTIONS folders

at_activate will pause and wait for the input of a one-time pin (OTP) sent to your email or phone number. Once activated, the master keys will save at C:\Users\<user>\.atsign\keys.

Step 3: Device Atsign activation (@example02_np)

Run the same command, but for your device Atsign.

Replace @<REPLACE>_np with your device Atsign.

at_activate.exe -a "@<REPLACE>_np"

Enter the one-time password (OTP) & Check your SPAM/PROMOTIONS folders

at_activate will pause and wait for the input of a one-time pin (OTP) sent to your email or phone number. Once activated, the master keys will save at C:\Users\<user>\.atsign\keys.

Step 4: Generate an Atsign authorization passcode for your device Atsign

Run the following command to generate a 6-character one-time passcode. You will use this passcode in Step 6.

Replace @<REPLACE>_np with your device Atsign.

at_activate.exe otp -a "@<REPLACE>_np"

Step 5 to Step 7

After setting up the machine you're connecting from, you'll configure the machine you're connecting to.

On the machine you are connecting to

Step 5: Download and run the Installer

Download the msi installer from GitHub. You can run the msi right from the windows-bundle.zip.

Ensure both Core Tools & Daemon Service are being installed.

Step 6: Initiate device Atsign authorization request

Open a terminal (Command Prompt or PowerShell) and run the following command to make an authorization request.

Be sure to replace the following values:

@<REPLACE>_np with your device Atsign,

<PASSCODE> with the passcode generated in Step 4,

<USER> with your Windows username,

@<REPLACE>_np_key with your device Atsign,

<DEVICE_NAME> with the name of the machine you are on

at_activate.exe enroll -a "@<REPLACE>_np" `
  -s <PASSCODE> `
  -p noports `
  -k C:\Users\<USER>\.atsign\keys\@<REPLACE>_np_key.atKeys `
  -d <DEVICE_NAME> `
  -n "sshnp:rw,sshrvd:rw"

Once you see this text, you're ready to continue to the next step.

Submitting enrollment request 
Enrollment ID: ---------------------
Waiting for approval; will check every 10 seconds

If you encounter a handshake exception, it usually means your root certificates are outdated. To refresh them, run the following command with administrator privileges:Install-Script -Name UpdateRootCertificates

Step 7: Setup Service Config on Device

The service config lives in C:\Program Data\NoPorts\sshnpd.yaml, you can open it in notepad by running the following command:

Make sure you run notepad/terminal as administrator or else you won't be able to save your changes!

notepad C:\ProgramData\NoPorts\sshnpd.yaml

Ensure you provide the following fields to your service config:

  • atsign

    • atsign: example02_np

    • atsign: '@example02_np'

  • keys (windows path)

    • keys: C:\Users\alice\.atsign\keys\@example02_np_key.atKeys

  • manager

    • manager: example01_np

    • manager: '@example01_np'

Examples on how to fill in the fields are inside the config file.

Step 8 and Step 9

With both machines now configured, the final steps bring us back to the machine initiating the connection.

On the machine you are connecting from

Step 8: Approve the device atSign authorization request

Run the following command:

Be sure to replace the following values:

@<REPLACE>_np with your device atSign,

@<REPLACE_NAME> with the device name from Step 6.

Step 9: Use NoPorts!

That's it. You can start using NoPorts or explore some of the documented use cases, including MCP, SSH, RDP, SFTP, Web Server, and SMB.

Last updated