Connecting to Windows Server with Remote Desktop (RDP)

Remote Desktop (RDP) is how you manage a Windows Server with a desktop interface. When your server is delivered, the client panel shows the IP address, username and password, and that is all you need to connect.

Connecting from Windows

1. Type mstsc in the Start menu to open Remote Desktop Connection.
2. Enter your server IP in the Computer field. The default port is 3389; if you changed it, use IP:PORT.
3. The username is usually Administrator, followed by your password.
4. A certificate warning is normal; the server uses a self-signed certificate.

To speed the session up, disable visual effects on the Experience tab. On the Local Resources tab you can share your own drive with the server to copy files.

Connecting from macOS, Linux and phones

On macOS and mobile devices use Microsoft's Windows App (formerly Microsoft Remote Desktop). On Linux, Remmina or FreeRDP are common. All of them take the same details: IP, username, password.

If the connection fails

• Freshly installed server: wait for the operating system installation to finish; RDP does not answer while it runs.
• Firewall: make sure the "Remote Desktop" rule is enabled in Windows Defender Firewall.
• Changed port: if you moved RDP to another port, open that port in the firewall too.
• Password errors: reset the password from the panel and check that copy-paste did not add a trailing space.
• Your own network: some corporate and school networks block port 3389. Try from a different network, such as your phone.

Transferring files to the server

• Drag and drop: tick your local drive under Local Resources > More on the connection screen and it appears under This PC on the server, ready for copying.
• Clipboard: copy and paste works for small files and text.
• Direct download: for large files the fastest route is downloading them in the server's own browser, so you are not limited by your home upload speed.

Can several people connect at once?

Windows Server allows a limited number of simultaneous sessions for administration by default. If several people from your team need to work at the same time, that limit matters. Creating a separate account per person is both safer and more traceable than sharing one. Closing the window instead of signing out leaves the session open and consuming resources.

When the server will not boot: the KVM console

Remote Desktop only works while the operating system and network are running. A wrong firewall rule or an update stuck at boot can leave RDP unresponsive. That is when the ILO/KVM interface in the client panel matters: it shows the server's own screen, lets you interact with the boot process and reinstall the operating system if needed. Losing RDP does not mean losing access to the server.

What happens if the connection drops?

When an RDP session drops, the server keeps running and open programs stay open. Reconnecting returns you to the same session, so starting a long job (a backup, an update) and disconnecting is safe.

Transferring files to the server

• Drag and drop: tick your local drive under Local Resources > More on the connection screen and it appears under This PC on the server, ready for copying.
• Clipboard: copy and paste works for small files and text.
• Direct download: for large files the fastest route is downloading them in the server's own browser, so you are not limited by your home upload speed.

Can several people connect at once?

Windows Server allows a limited number of simultaneous sessions for administration by default. If several people from your team need to work at the same time, that limit matters. Creating a separate account per person is both safer and more traceable than sharing one. Closing the window instead of signing out leaves the session open and consuming resources.

When the server will not boot: the KVM console

Remote Desktop only works while the operating system and network are running. A wrong firewall rule or an update stuck at boot can leave RDP unresponsive. That is when the ILO/KVM interface in the client panel matters: it shows the server's own screen, lets you interact with the boot process and reinstall the operating system if needed. Losing RDP does not mean losing access to the server.

What happens if the connection drops?

When an RDP session drops, the server keeps running and open programs stay open. Reconnecting returns you to the same session, so starting a long job (a backup, an update) and disconnecting is safe.

Keep RDP secure

Remote Desktop is exposed to the internet and constantly receives password attempts. Do at least these three things:

• Use a long, unique password and change the default one for Administrator.
• If possible, change the RDP port and add a firewall rule that only allows your own IP.
• Define an account lockout policy for failed sign-in attempts.

Our servers run behind Layer 4 and Layer 7 DDoS protection, but password security inside the server is your responsibility.