Skip to main content

Connect to a Windows Node

Use this guide to connect to a Windows node from your local machine by using Remote Desktop Protocol (RDP). This page is for Windows nodes only. For Linux nodes, use Connect to a Linux node.

Windows nodes use password-based RDP access. SSH-key access is for Linux nodes and is not shown for Windows nodes in the create-node flow.

Before You Begin​

Make sure you have:

RequirementWhere to check
Node statusThe node should be in Running state in Compute > Nodes.
Public IP or private network pathUse the Public IP column in the node list, or use a private IP only from a network that can reach the node.
UsernameUse the username shown in the password email, image notes, or your configured Windows user.
PasswordUse the secure password email sent after node creation, or the latest password if it was changed later.
Security group accessInbound TCP port 3389 must be allowed from your source IP or network.
RDP clientUse the built-in Remote Desktop client on Windows, Microsoft Remote Desktop on macOS, or an RDP client such as Remmina on Linux.
note

E1WC is part of the E1-series behavior. E1-series nodes do not include a default public IP. If the Public IP column shows Not Assigned, attach a primary public IP where supported or connect through a private network path that can reach the node.

Best Practice

Do not expose RDP to all internet sources unless you intentionally need that access. Restrict TCP port 3389 to your office, VPN, bastion host, or trusted source IP range.

Find the Node IP Address​

  1. Log in to MyAccount.
  2. Go to Compute > Nodes.
  3. Find the Windows node you want to access.
  4. Use one of these addresses:
AddressWhen to use it
Public IPUse this when connecting from the internet.
Private IPUse this only when your machine, VPN, bastion host, or another node can reach the node's private network.

If the node has no public IP:

  • Attach a primary public IP if the node must be reachable from the internet.
  • Use a private network path if the node is intentionally private.
  • Use Access Console from the node list or node details page if you need emergency console access while fixing network settings.

Connect from Windows​

  1. Open Remote Desktop Connection.
  2. Enter the node Public IP or reachable Private IP in the Computer field.
  3. Click Connect.
  4. Enter the username and password from the node password email.
  5. If the RDP client shows a certificate warning, confirm only after checking that the IP address is the Windows node you intended to access.

You can also open Remote Desktop Connection from Run:

mstsc

Connect from macOS​

  1. Install Microsoft Remote Desktop from the Mac App Store if it is not already installed.
  2. Add a new PC.
  3. Enter the node Public IP or reachable Private IP as the PC name.
  4. Enter the username and password from the node password email, or choose to enter credentials when connecting.
  5. Start the saved connection.
  6. If the client shows a certificate warning, continue only after checking that the IP address is correct.

Connect from Linux​

Use an RDP client such as Remmina or another client supported by your Linux distribution.

General flow:

  1. Open your RDP client.
  2. Create a new RDP connection.
  3. Enter the node Public IP or reachable Private IP.
  4. Enter the username and password from the node password email.
  5. Connect.

If you use a command-line RDP client, follow that client's documentation for the exact command format. Keep the password out of shell history when possible.

Password Email and Password Changes​

After node creation, a secure password link is sent to the registered email address. The link expires after 168 hours. Save the password securely when you retrieve it.

You can change the Windows node password from MyAccount:

  1. Go to Compute > Nodes.
  2. Open the Windows node details page.
  3. Go to the Security area.
  4. Use the password change action.
  5. Enter and confirm the new password.

The portal validates the new password before submitting it. The password must be 16 to 30 characters and include uppercase, lowercase, number, and special-character requirements.

note

If the node is locked or acting as a DR target, the portal can disable password changes. Resolve the node state first or contact support if the action remains unavailable.

Common Connection Problems​

SymptomLikely causeWhat to do
Public IP shows Not AssignedThe node does not have a public IP.Attach a primary public IP or connect through a private network path.
RDP cannot connect or times outTCP port 3389 is blocked, the node has no reachable IP, or the route is unavailable.Check the primary public IP, Add-on IPs, VPC path, and security group inbound rules.
Credentials are rejectedThe username or password is wrong, or the password was changed after the email was sent.Use the latest password, confirm the username, or change the password from MyAccount.
RDP opens but disconnects quicklyWindows may still be starting services, or the node is under heavy load.Wait a few minutes, refresh node status, then retry. Use Access Console if it continues.
Certificate warning appearsThe RDP certificate is not trusted by your local machine.Verify the node IP before continuing. Do not continue if the IP is not the node you intended to access.
Security group looks correct but RDP still failsWindows Firewall or an OS-level rule can conflict with network rules.Use Access Console to inspect Windows network and firewall settings.

Security Checklist​

Before using the Windows node for production:

  • Restrict inbound TCP 3389 to trusted source IPs.
  • Avoid sharing the Windows password over chat or tickets.
  • Change the password after sharing temporary access.
  • Use a VPN, bastion, or private network path for administrative access when possible.
  • Keep Access Console available for emergency recovery.
  • Review security group rules after attaching or changing public IPs.

Automate This​

For automation, use the approved MyAccount API documentation as the public source of supported node operations:

Do not depend on private or unpublished fields unless the field is present in the approved public API documentation.

ResourceUse it for
Create a nodeLaunch a Windows node and review password access behavior.
Choose a node familyCompare E1WC, Windows compute, SQL, and other node families.
Connect and use a SQL Server nodeConfigure access for Windows SQL Server nodes after RDP works.
Security GroupsAllow or restrict TCP port 3389.
Static Public IPsAttach a primary public IP when the node does not have one.
Manage NodesManage node actions after launch.
Connect to a Linux nodeAccess Linux nodes with SSH.

Next Step​

After you connect, apply Windows updates, configure your workload, and restrict the security group to only the ports your workload needs. If this is a SQL Server image, continue with Connect and use a SQL Server node.

Last updated on May 19, 2026.