Canonical page: https://koahost.com/rdp-connection-guide/ Language: English. Source snapshot: 2026-11-11. Generated: 2026-11-11T12:30:53.888Z. [Home](https://koahost.com/) / [Explore](https://koahost.com/resources/) / WINDOWS / RDP WINDOWS / RDP # Connect to your KoaHost Windows server Find your access details, open your first remote desktop and save a connection without putting a password in a file. [Find your VPS](https://koahost.com/vps/) ## IN THIS DOCUMENT [Before your first connection](https://koahost.com/rdp-connection-guide/#section-1)[Connect from Windows](https://koahost.com/rdp-connection-guide/#section-2)[Connect from macOS or Linux](https://koahost.com/rdp-connection-guide/#section-3)[Save several connections](https://koahost.com/rdp-connection-guide/#section-4)[Protect your access](https://koahost.com/rdp-connection-guide/#section-5)[If the connection fails](https://koahost.com/rdp-connection-guide/#section-6)[Users, sessions and plan size](https://koahost.com/rdp-connection-guide/#section-7)[Your privacy settings](https://koahost.com/rdp-connection-guide/#section-8)[Questions & answers](https://koahost.com/rdp-connection-guide/#page-faq)[Knowledge base](https://koahost.com/resources/) ## Before your first connection Wait until your service is marked active. In the private client area, find its actual IP address, RDP port and Windows account details. A hostname chosen in the configurator identifies your server. It becomes a connection address only when its DNS points to the server IP. ## Connect from Windows Press Win + R, type mstsc and open Remote Desktop Connection. Enter the delivered IP address, followed by :port if a custom port is specified. Select Connect, enter the delivered username and password, then verify any certificate warning against the server details before proceeding. ## Connect from macOS or Linux On macOS, use Microsoft Windows App and add a remote PC. On Linux, use Remmina with the RDP protocol. Enter the same server address and your own Windows account details. Keep certificate verification enabled. ## Save several connections In mstsc, open Show Options, then Save As to create a separate .rdp file for each server. Use clear names to avoid confusing machines. The file may contain the address and username. Leave password entry enabled. Credentials saved in the local operating system are a separate choice, suitable only on a trusted personal device. ``` full address:s:YOUR_SERVER_IP:3389 username:s:YOUR_WINDOWS_USERNAME prompt for credentials:i:1 redirectdrives:i:0 ``` ## Protect your access Use a unique strong password and keep Windows and your RDP client updated. Keep Network Level Authentication enabled. Restrict access to your IP addresses or use a suitable VPN or gateway. Each team member should use a personal account. Sharing the administrator password gives everyone the same privileges. Official documentation: [Microsoft · Remote Desktop](https://learn.microsoft.com/windows-server/remote/remote-desktop-services/remotepc/remote-desktop-allow-access) ## If the connection fails Check that the service is active and the delivered address and port are correct. Verify your permitted source IP if your network changed. A failed login may come from the username, keyboard layout or password. A certificate change needs verification. Contact support from your client area if access still fails. Never paste passwords into a ticket. ## Users, sessions and plan size The Windows Server allocations cover named people, not interchangeable seats shared by a larger team. The same maximum number may connect simultaneously. Their applications share the plan resources. Windows 10/11 provides one session. Close a session by signing out when finished. Disconnecting leaves applications running and does not create another licence. - Scout Remote · 1 named user - Warden Remote · 5 named users - Guardian Remote · 10 named users - Vanguard Remote · 20 named users - Apex Remote · 30 named users Official documentation: [Microsoft · RDS](https://learn.microsoft.com/windows-server/remote/remote-desktop-services/rds-plan-choose-how-you-pay) ## Your privacy settings NO KYC. NO ACTIVITY LOGS. · DMCA ignored KoaHost follows its no-KYC and no-activity-logging policy. Windows and applications may keep logs inside your own server. You control their configuration. Your RDP client may also remember connections locally. Saved .rdp entries are not additional users and do not change the access rights included in your plan. ## A little more clarity. How many users are included? On Windows Server, Scout includes 1 named user, Warden 5, Guardian 10, Vanguard 20 and Apex 30. Windows 10/11 provides one user session on every tier. Can I add more users? Choose a larger Windows Server tier or request a written offer for a custom allocation. The rights and any extra charge must be agreed before purchase. Where do I find my password? Use the access details delivered through your private client area after activation. Keep them in a password manager. Support does not need your Windows password to answer a connection question. KEEP EXPLORING ## Continue reading. [Products ### Anonymous offshore Windows RDP hosting Anonymous offshore Windows RDP hosting with a Windows licence and administrator access. No KYC, crypto payments and DMCA ignored.…](https://koahost.com/rdp/)[Guides ### Make RDP a deliberate entrance. A Windows server needs the same care as any public machine, with particular attention to remote login and software licensing.…](https://koahost.com/windows-security/) CONFIGURE YOUR INFRASTRUCTURE ## Take control. Deploy on your terms. No identity paperwork. Full administrator access. Crypto-native billing. [Select a configuration](https://koahost.com/vps/)