our Windows VPS comparison table<\/a> lays out the RDP-ready templates and the resource tiers that suit different workloads.<\/p>\n\n\n\nConfirm the server is reachable<\/h2>\n\n\n\n
Before touching the RDP client, prove that the host is up and that port 3389 is open. From a command prompt on your workstation:<\/p>\n\n\n\n
Test-NetConnection 203.0.113.10 -Port 3389<\/code><\/pre>\n\n\n\nA TcpTestSucceeded : True<\/code> result means the network path and the listener are both fine, so any failure after that point is authentication, certificate, or session configuration. If the test fails, check that the provider firewall allows your source IP and that the guest firewall has an inbound rule for Remote Desktop. A silent timeout usually means a network-level block; an immediate refusal usually means nothing is listening on the port at all.<\/p>\n\n\n\nOne nuance worth knowing: some providers expose RDP on a non-standard port to reduce noise from automated scanners. If your control panel issued a port other than 3389, use that value in the address field as host:port<\/code> and in the test above.<\/p>\n\n\n\nOpen the client and set the essentials<\/h2>\n\n\n\n
Launch mstsc.exe<\/code>, enter the public address or hostname of your server in the Computer field, then open Show Options<\/em> to fill in the details that matter:<\/p>\n\n\n\n- User name<\/strong> \u2014 use
SERVERNAME\\Administrator<\/code> or .\\Administrator<\/code> if the account is local. A bare username can be resolved against the wrong domain.<\/li>\n- Allow me to save credentials<\/strong> \u2014 convenient on a trusted personal machine, but skip it on shared hardware.<\/li>\n
- Experience tab<\/strong> \u2014 pick LAN (10 Mbps or higher)<\/em> for a data-centre link, or Modem<\/em> when you are tethered.<\/li>\n
- Display tab<\/strong> \u2014 choose a resolution and colour depth your link can carry; 32-bit colour over a congested link causes noticeable lag.<\/li><\/ul>\n\n\n\n
Save the connection as a .rdp file when you are finished. It keeps every setting, including gateway and certificate preferences, so you can launch the same configuration from a shortcut or hand it to a colleague without retyping credentials.<\/p>\n\n\n\n
Why the first login sometimes fails<\/h2>\n\n\n\nThe identity of the remote computer cannot be verified<\/h3>\n\n\n\n
This warning appears because the server presents a self-signed certificate that the client cannot trace to a trusted authority. Inside a data centre the host is one you provisioned, so choosing Don’t ask me again for connections to this computer<\/em> and continuing is normal. A certificate warning on a host you do not recognise is a genuine reason to stop, because it can indicate a man-in-the-middle proxy.<\/p>\n\n\n\nAn authentication error has occurred (Code: 0x80004005 or 0x80090302)<\/h3>\n\n\n\n
These codes point at a CredSSP or Network Level Authentication mismatch, often after patching changed the CredSSP encryption oracle setting on one side of the link. Server and client must agree on the required encryption level, and a mismatch surfaces as an authentication failure before the login screen ever renders. The same symptom appears if the server requires NLA but the connecting account is blocked by a lockout policy.<\/p>\n\n\n\n
# Check the auth level and RDP listener state\nGet-ItemProperty 'HKLM:\\SYSTEM\\CurrentControlSet\\Control\\Terminal Server\\WinStations\\RDP-Tcp' | Select-Object UserAuthentication, SecurityLayer\nGet-Service TermService\n(Get-NetTCPConnection -LocalPort 3389 -State Listen).OwningProcess<\/code><\/pre>\n\n\n\nThe number of connections is limited<\/h3>\n\n\n\n
An administrative session limit or an expired RDS CAL produces a message about the connection limit being reached. Sign out stale sessions from the server console or with qwinsta<\/code> and rwinsta<\/code>, and check licensing if the limit returns every day.<\/p>\n\n\n\nDial in the settings that change how it feels<\/h2>\n\n\n\n
Two things dominate perceived performance once the connection works. First, disable desktop composition, menu animations, and font smoothing on the client’s Experience tab \u2014 they add round trips for little benefit on a remote session. Second, keep your session resolution close to your local monitor; upscaling a large desktop over a thin link forces the client to re-render more pixels than it needs.<\/p>\n\n\n\n
For users on high-latency links, the Persistent bitmap caching<\/em> option meaningfully reduces redraw traffic, at the cost of disk space in the local cache folder. Enable it for regular connections and disable it on shared machines.<\/p>\n\n\n\nReconnect, gateway, and multi-monitor notes<\/h2>\n\n\n\n
If you reach the server through a Remote Desktop Gateway, the gateway address belongs on the Advanced tab, not in the Computer field. When a session drops, the default behaviour is to reconnect automatically; the Reconnect if the connection is lost<\/em> checkbox controls that, and it works best when the server keeps disconnected sessions alive rather than logging them off immediately.<\/p>\n\n\n\nMulti-monitor setups need the display setting matched to the monitors actually available. A saved .rdp file that requests four monitors will open a single maximised window on a laptop unless Use all my monitors for the remote session<\/em> is set, which is a common source of “it looks wrong” reports.<\/p>\n\n\n\n