Before you start
The service must be delivered and active. Find its access information in the client area and delivery email without posting credentials publicly. Record the installed image and keep a backup before major changes. Reinstallation follows a data-erasing confirmation flow; it is not a harmless substitute for troubleshooting.
Find the correct service details
Open the relevant VPS and its remote-access section. Copy the displayed address and port with the supplied username instead of guessing a name from the operating-system language. Do not substitute a game server’s SFTP details or a Linux SSH port for the RDP port. Confirm that the copied address belongs to the Windows VPS you intend to administer.
Use a supported RDP client
On Windows, the built-in Remote Desktop Connection client accepts the destination and credentials. On another platform, use a client supported by its publisher for your environment. At first connection, inspect identity and certificate information rather than approving an unexpected destination automatically. The panel’s KVM console is a separate interface that can help when networking or the operating system is not responding normally.
Separate connection from permission
Network authentication and account rights determine who can open a session. Retain NLA and compatible access protections. Use strong passwords and appropriate permissions. Administrator access for server management does not automatically provide licensed remote desktops for unlimited users. Multiuser scenarios may require additional rights or licences, including applicable RDS CALs. Confirm the intended use rather than inferring entitlement from a successful login.
Allow for the operating system and licensing
CubixServ presents Windows Server Evaluation without a permanent licence included. Check Microsoft’s terms before planning ongoing use, together with the application’s own rights. Windows Server is not Windows 11; software compatibility, interfaces and roles differ. Compare image and application requirements with the selected memory and storage. Additional applications can quickly exhaust the headroom of a small VPS even when an initial login succeeds.
Diagnose failures before reinstalling
Record the exact error and check the service state, destination and time. If KVM works, inspect the operating system, logs, RDP service and access rules. Rejected credentials are not the same as a network outage; a timeout alone does not prove an attack. Avoid disabling the entire firewall or repeatedly restarting the server to hide an underlying configuration problem.
Prepare daily operation
After verifying access, plan updates, service accounts and independent backups before deploying compatible IIS, .NET or business applications. Check each software licence. Upstream DDoS filtering does not replace operating-system administration. For support, provide the relevant time, error and checks performed, removing passwords, tokens and personal data. Keep a recovery route available before changing remote-access settings.
For your situation
| Situation | Next check |
|---|---|
| Credentials rejected | Check the supplied account, correct service and keyboard layout before resetting anything. |
| Connection times out | Verify destination, port and console, then RDP state and access rules. |
| Several users | Check Microsoft and application rights; administration access is not a licence for unlimited desktops. |
Official sources
These documents describe the relevant protocols and software. Your service terms and configuration still need to be checked.
- Microsoft Learn/en-us/windows-server/remote/remote-desktop-services/remotepc/remote-desktop-allow-access
- Microsoft Learn/en-us/windows-server/get-started/hardware-requirements
- Microsoft/en-us/evalcenter/evaluate-windows-server-2025
- Microsoft Learn/en-us/windows-server/remote/remote-desktop-services/rds-client-access-license