Connecting to a Windows server with Remote Desktop (RDP)
In this guide you learn how to connect to your Windows VDS or VPS with Remote Desktop (Remote Desktop Protocol, RDP) from Windows, macOS, iPhone, iPad, Android and Linux, how to handle the certificate warning on your first connection, and how to fix the most common connection errors.
Find your sign-in details
Once your payment is confirmed, your server is set up automatically, and most orders are delivered within a few minutes. Everything you need to connect is on the Sign-in Details card on your service page in the client area:
- Username:
Administratoron Windows servers. - Password: Hidden by default; use Show / Hide to see it and Copy to put it on the clipboard.
- IP Address and, if any, Additional IP rows: your server's dedicated IPv4 addresses.
- Remote Desktop (RDP) row: the address to connect to, in the form
IP:3389. - Download the RDP connection file: a ready-made .rdp file with the address (
IP:3389) and theAdministratorusername already filled in; it opens full screen, adapts to the window size with smart sizing and dynamic resolution, and asks for your credentials when you connect.
If you installed Windows with the Reinstall OS tool, the process can take up to 10 minutes, and first-boot settings such as networking, the password and the disk are completed in the background. Attempts made before then may time out or have the password rejected; wait a few minutes and try again. For details, see the reinstall guide.
Manage the password from the client area
To change the Administrator password, use the Reset Root Password tool in the client area; on Windows servers it changes the Administrator password. The panel logs in to the server with the stored password. If you change the password inside Windows (for example with net user), the panel can no longer log in, and the next reset fails with an error saying it could not log in to the server with the stored password. The new password must be at least 8 characters long and contain at least three of the following: uppercase letters, lowercase letters, digits and symbols. We recommend choosing a longer password and keeping it in a password manager. For the other steps after delivery, see the first 30 minutes checklist.
Connecting from a Windows computer
With the ready-made .rdp file
Double-click the file you downloaded. Windows may warn that the publisher cannot be verified; if you downloaded the file from your own client area, continue with Connect. In the credentials window, check that the username is Administrator and paste the password you copied from the client area.
If the credentials window suggests your own computer's account, choose the option to use a different account in that window and enter the username as .\Administrator. The leading .\ tells Windows you want the local account on the server.
Open only .rdp files you downloaded from your own client area. An .rdp file that arrives by email or from any other source can expose your local drives and clipboard to an unknown server the moment you connect.
mstsc and Local Resources
To connect without a file, press the Windows key + R to open the Run dialog, type mstsc and enter the IP address in the Computer field. You can also start the same client from the command line; all parameters are listed in the mstsc documentation:
# Connect by IP address
mstsc /v:203.0.113.10
# Full screen, or a specific window size
mstsc /v:203.0.113.10 /f
mstsc /v:203.0.113.10 /w:1600 /h:900
# Edit the settings of the .rdp file you downloaded (use your own file name)
mstsc /edit "$env:USERPROFILE\Downloads\server.rdp"The Show Options button opens the settings tabs. On the Local Resources tab, the Clipboard box controls copy and paste, and the Remote audio setting decides where sound plays. Drives, which you select under the More... button, shows your local disks on the server under This PC and is handy for small file transfers. Share only the resources you need, because software running on the server can also access a shared drive. To change the settings of the ready-made file permanently, right-click it, choose Edit and save it with Save As on the General tab.
Connecting from macOS, iPhone, iPad, Android and Linux
Microsoft's client, formerly called Microsoft Remote Desktop, is now named Windows App and can be installed for free on the following platforms:
| Platform | Client | Adding the connection |
|---|---|---|
| macOS | Windows App (App Store) | Open the downloaded .rdp file with the app, or add a new PC with its IP address using the plus (+) icon |
| iPhone and iPad | Windows App (App Store) | Add the IP address and the Administrator user manually |
| Android | Windows App (Google Play) | Add the IP address and the username manually |
| Linux | Remmina or FreeRDP | Create a new RDP profile in Remmina, or run FreeRDP from the command line |
On mobile devices, copying the password from the client area and pasting it is the most reliable way to avoid keyboard layout mix-ups. On Linux, Remmina is a graphical client whose RDP support comes in a separate plugin, while FreeRDP runs from the command line. The package name and the command depend on your distribution:
# Ubuntu/Debian: Remmina and its RDP plugin
sudo apt install remmina remmina-plugin-rdp
# FreeRDP 3: package freerdp3-x11, command xfreerdp3
sudo apt install freerdp3-x11
xfreerdp3 /v:203.0.113.10 /u:Administrator /dynamic-resolution
# Older releases with FreeRDP 2: package freerdp2-x11, command xfreerdp
xfreerdp /v:203.0.113.10 /u:Administrator /dynamic-resolution/dynamic-resolution adjusts the remote desktop's resolution as you resize the window. FreeRDP asks for the password, and on the first connection for certificate approval, on the command line.
The certificate warning on your first connection
Windows encrypts Remote Desktop traffic with a self-signed certificate. Because this certificate does not come from a recognized certificate authority, you see the warning "The identity of the remote computer cannot be verified" on your first connection. This is expected, but instead of clicking straight through, verifying once that the certificate really belongs to your server is how you would notice an attacker trying to intercept the connection (a man-in-the-middle attack):
- In the warning window, click View certificate and note the Thumbprint value on the Details tab.
- Open the VNC Console from the client area, sign in as Administrator and run the command below in PowerShell.
- If the two values match, check Don't ask me again for connections to this computer and connect. If they differ, do not connect, and check the network you are using.
Get-ChildItem 'Cert:\LocalMachine\Remote Desktop' | Select-Object Subject, Thumbprint, NotAfterThe self-signed certificate is renewed at intervals, and it can also change when the operating system is reinstalled or the server name changes. It is normal for the warning to reappear in those cases; if it changes for no obvious reason, verify the thumbprint again.
Troubleshooting connection problems
| Symptom | Likely cause | What to do |
|---|---|---|
| The connection times out, or you see "Remote Desktop can't connect to the remote computer" | The server is off, Windows is restarting after updates, or the network you are on blocks port 3389 | Check the server status in the client area; if the VNC Console shows an update screen, wait for it to finish; run Test-NetConnection 203.0.113.10 -Port 3389 on your computer, or try from another network (e.g. your phone's mobile data) |
| "Your credentials did not work" | The password was mistyped, the keyboard layout differs, or the client sends a different account name | Copy and paste the password from the client area and enter the username as .\Administrator; if that fails, set a new password with Reset Root Password |
| "An authentication error has occurred" with CredSSP encryption oracle remediation, or a Network Level Authentication (NLA) message | The client or the server is not up to date, or the client does not support NLA | Install Windows updates on both sides and update old clients; do not relax the security policy or turn off NLA |
| "An internal error has occurred" | Remote Desktop Services is not ready yet or is stuck; sometimes a VPN or network issue on the client side | If the server has just started, wait a few minutes; run Restart-Service TermService -Force from the VNC Console; if it persists, use Restart Server in the client area |
| The connection opens but the screen stays black | The user profile is loading, updates are running, or Windows Explorer is not responding | Wait a minute; press Ctrl+Alt+End to open Task Manager and start explorer.exe as a new task; turn off persistent bitmap caching on the Experience tab |
You can check whether an action you started in the client area was applied on the server in the C:\Windows\Temp\wisecp-task.log file. If the problem persists, open a support ticket; the support ticket guide explains what to include. Do not share your password in a support message.
If Remote Desktop is turned off: recovery with the VNC Console
If Remote Desktop has been turned off or a firewall rule is broken, your network-independent way in is the VNC Console in the client area; it opens while the server is running (see the VNC Console guide). Sign in as Administrator, then in Server Manager click the Remote Desktop entry on the Local Server page and select Allow remote connections to this computer, or use the Remote Desktop option in the sconfig menu. To do the same with PowerShell:
# Allow Remote Desktop connections
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server' -Name 'fDenyTSConnections' -Value 0
# Enable the Remote Desktop firewall rules (group ID that works in any UI language)
Enable-NetFirewallRule -Group '@FirewallAPI.dll,-28752'
# Check the service and that port 3389 is listening
Get-Service TermService
Get-NetTCPConnection -LocalPort 3389 -State ListenWhile troubleshooting, do not stop or remove VMware Tools (the VMTools service on Windows); panel actions such as a safe shutdown or a password reset depend on it.
Signing out versus disconnecting
When you close the Remote Desktop window from the connection bar at the top, you only disconnect: your session and open programs keep running on the server, and when you reconnect you pick up where you left off. This is useful for a long copy job or installation. Signing out is done from your user icon in the Start menu with Sign out, or with the logoff command, and it closes your programs. Signing out when you are done keeps idle sessions from using memory and CPU and keeps unsaved documents from staying open. To list the sessions on the server and end one if needed:
# List the sessions on the server
quser
# Sign out the session with ID 2 (take the ID from the quser output)
logoff 2Frequently asked questions
Is it safe to save my credentials?
The Remember me option stores the password in Windows Credential Manager, for your user account only. Do this only on a computer you alone use, with a locked screen and an encrypted disk; never save it on shared computers. You can list saved entries with cmdkey /list and delete one with cmdkey /delete:TERMSRV/203.0.113.10.
Does anything change after I rename the server?
The Change Hostname tool changes the computer name in Windows and restarts the server. You cannot connect until the restart is complete; because you connect by IP address, the name change does not affect the connection address, but the certificate warning may reappear.
Should I change the RDP port?
Changing the port cuts down some automated scanning, but it does not provide security on its own; IP restrictions, account lockout and NLA are far more effective. The Sign-in Details card and the file you download use the default port 3389, so if you change the port you have to connect with the mstsc /v:IP:port format. See the RDP security guide for details.
Related articles
Thanks for your feedback!