Windows and RDP

How to connect to a Windows server via RDP: PC, Mac, phone

You open the desktop of a Windows server with Remote Desktop Connection, which is built into Windows, or with the free Windows App on a Mac or phone. The IP address, username and password are in the ticket about your server’s delivery.

  • Time: 10 minutes
  • Level: Easy

In short

  • On Windows: press Win + R, type mstsc, enter the server’s IP in the Computer field and the username from the ticket, usually Administrator.
  • On a Mac, iPhone, iPad or Android: use Microsoft’s Windows App (formerly Microsoft Remote Desktop). Tap “+”, then add a PC by its IP address.
  • On the first login, Windows warns that it cannot verify the server’s certificate. This always happens with a new server: click Yes.
  • Change the password you were given right after you log in: Ctrl + Alt + End, then Change a password.
Contents
  1. When to connect and where to find the login details
  2. From a Windows computer: Remote Desktop Connection
  3. From a Mac: Windows App
  4. From an iPhone, iPad or Android: the same Windows App
  5. Change the administrator password right away
  6. Closing the window or signing out: what happens to programs
  7. If you cannot connect: RDP errors and what to do
  8. FAQ

You will need

  • The IP address, username and administrator password from the delivery ticket in the ABCD client area.
  • On a Mac, iPhone, iPad or Android: the free Windows App from the App Store, Mac App Store or Google Play.
  • No server yet? See RDP servers with Windows Server.

When to connect and where to find the login details

We send the IP address, username and administrator password to the ticket once Windows is installed and the server is ready. Until that message arrives, you cannot connect: the system is still being installed.

The username is usually Administrator; a localized Windows Server uses a translated account name (for example, Администратор in the Russian edition). The default RDP port is 3389, and you do not need to enter it.

After a reboot, and especially after installing updates, a Windows server takes longer to come back than a Linux one. Wait about 15 minutes before deciding that it is not responding.

From a Windows computer: Remote Desktop Connection

The program is built into Windows 10 and 11 and is called mstsc; there is nothing to download.

  1. Open Remote Desktop Connection

    Press Win + R, type mstsc and press Enter. Or start typing “Remote Desktop Connection” in the Start menu.

  2. Enter the server’s IP and the username

    In the Computer field, enter the server’s IP, for example 203.0.113.10. Click Show Options and enter the username from the ticket in the User name field.

    If your computer is in a domain or you sign in to Windows with a Microsoft account, write the name with a dot and a backslash: .\Administrator. This tells Windows that the user belongs to the server, not to your computer.

  3. Turn on the clipboard and drives if you need to transfer files

    On the Local Resources tab, select Clipboard: you can then copy text and files between your computer and the server with Ctrl + C and Ctrl + V. The More button opens the choice of drives: a selected drive appears in File Explorer on the server. Connect only the drive you need, because the server gets full access to it for the duration of the session.

  4. Click Connect and enter the password

    In the Windows Security window, paste the password from the ticket. If the name of your own computer’s account is already filled in, click More choices under the password field, then Use a different account.

    Select Remember me only on your own personal computer.

  5. Confirm the connection in the certificate warning

    On the first login, Windows shows: “The identity of the remote computer cannot be verified. Do you want to connect anyway?” Click Yes. To stop the question from appearing again, select Don’t ask me again for connections to this computer.

    Why the warning appears and how to check it

    Windows Server creates its own RDP certificate during installation, and your computer cannot match it against a known certificate authority. The traffic is encrypted anyway; the warning only says that no third party has confirmed the server’s identity.

    To check the server, click View certificate in the warning and compare the thumbprint with the one the server itself shows. This PowerShell command, run on the server (for example through the KVM console), prints the thumbprint:

    Get-ChildItem 'Cert:\LocalMachine\Remote Desktop' | Format-List Subject, Thumbprint

    After a Windows reinstall, the certificate is new, and the warning appears again.

The server’s desktop opens within a few seconds. To avoid entering the address every time, go back to the General tab and click Save As: you get an .rdp file that opens the connection with a double-click.

From a Mac: Windows App

In 2024, Microsoft renamed the Microsoft Remote Desktop app for Mac to Windows App. If you already have the old app, it becomes Windows App by itself after an update.

  1. Install Windows App

    Find Windows App by Microsoft Corporation in the Mac App Store and install it.

  2. Add the server

    Click + and choose Add PC. In the PC name field, enter the server’s IP. You do not have to save the username and password: the app asks for them when you connect. Click Add.

  3. Connect and accept the certificate

    Double-click the server’s tile and enter the username and password from the ticket. When warned that the certificate could not be verified, click Continue.

The server stays in the app’s list, and next time a double-click on its tile is enough.

From an iPhone, iPad or Android: the same Windows App

Phones and tablets use the same app: Windows App by Microsoft Corporation in the App Store or Google Play. It replaced the former Microsoft Remote Desktop app on iOS and Android.

  1. Install Windows App and add the server

    Open the app, tap “+” and choose to add a PC. Enter the server’s IP in the PC name field and save.

  2. Connect

    Tap the server’s tile, enter the username and password, and accept the certificate warning.

A phone is handy for checking the server on the go: making sure a trading terminal is running, restarting a program. For longer work, a phone screen is too small, and a computer is the better choice.

Change the administrator password right away

The password from the ticket is stored in the ticket history and your e-mail. Change it in the first minutes of work, then set up protection as described in the article on protecting RDP from password guessing.

  1. Press Ctrl + Alt + End

    Inside an RDP session, this shortcut replaces Ctrl + Alt + Del. A menu appears with options to lock, sign out and change the password.

  2. Choose “Change a password” and enter a new one

    Enter the old password, then the new one twice. Make the new password at least 16 characters long, ideally generated by a password manager and not used anywhere else.

If the shortcut does not work, for example on a Mac or a phone, open PowerShell on the server as administrator and run net user Administrator *: Windows asks for the new password twice. On a localized Windows Server, use the translated account name (on Russian Windows, net user Администратор *).

Closing the window or signing out: what happens to programs

If you close the connection window with the cross, the session on the server keeps running. Open programs, such as a MetaTrader terminal or 1C, stay running, and you return to them the next time you connect. To end the session and close the programs, choose StartSign out on the server.

Right after installation, Windows Server accepts two RDP connections at the same time. If you need more, read how a server for a team works.

If you cannot connect: RDP errors and what to do

MessageWhat it meansWhat to do
“Remote Desktop can’t connect to the remote computer for one of these reasons…”
In Windows App on a Mac or phone: Error code: 0x204
The server does not accept the connection: it is rebooting or installing updates, the IP is wrong, the RDP port has been changed, or access is open only to specific IPs.Wait 15 minutes and try again. Compare the IP with the ticket. If the port was changed, add it after a colon: 203.0.113.10:42390. If that does not help, see what to check if the server is not responding.
“Your credentials did not work”The server did not accept the username or password.Check the keyboard layout and Caps Lock in the password window. Enter the name as .\Administrator. Paste the password with no trailing space. If the password is lost: resetting a Windows password on Hetzner; for an OVH server, write to us in a ticket, and we will tell you how to reset it.
As a security precaution, the user account has been locked because there were too many logon attempts or password change attempts.The lockout kicked in after wrong passwords. These may have been your own attempts or bots guessing the password.Wait for the lockout to clear (if you set it up following our article, that is 15 minutes), and enter the password carefully. If lockouts keep happening, restrict access to RDP: how to protect RDP.
“An internal error has occurred”The server could not start a session. The causes vary, from a temporary failure of the Remote Desktop Services to overload from mass password guessing.Try again in a few minutes. If it still fails, reboot the server: on Hetzner, on OVH. If the error comes back, close RDP to other people’s addresses as described in the article on protecting RDP.
“This could be due to CredSSP encryption oracle remediation”The server lacks security updates, and your computer refuses to log in without them.Update Windows on the server: open its screen through the Hetzner KVM console or IPMI on OVH and install the updates.

If the error is different or the advice did not help, send a screenshot of the error window and the time of the attempt, but not the password, in a ticket. They help support see faster on whose side the failure is.

FAQ

Which port does RDP use, and do I need to enter it?
The default is 3389, and you do not need to enter it. If the port was changed, add it to the IP after a colon: 203.0.113.10:42390.
How many people can work on the server at the same time?
Right after installation, Windows Server allows two. For more, you need the Remote Desktop Services role and licenses for it: more on a server for a team.
Will my programs close if I close the RDP window?
Not if you close the window with the cross: the session keeps running. Programs close if you choose Sign out on the server.
Can I connect from Linux?
Yes, for example with Remmina, which is in the repositories of most distributions. Choose the RDP protocol and enter the server’s IP.

Did this guide help?

Questions?