Connect to a server through the remote access portal

TL;DR — To connect to a server through the remote access portal, sign in to the portal, open the server from the resource list, and launch the browser-based session first. If the connection fails, the most common fix is using the correct portal account or role (your permission level) and selecting the right target server from the list. Reading time: ~5 min

Goal

When you finish, you will be able to open the remote access portal, select the correct server, and start a working remote session so you can see the server login screen or desktop/terminal in your browser.

Prerequisites

• Your remote access portal URL, for example https://portal.your-company.example.
• Your portal username and password, or your single sign-on (SSO, company login) account.
• Any second factor required for login, such as an authenticator app code or security key.
• Permission to access the target server in the portal. If you do not see the server listed after login, your account is missing access.
• The server name you need to reach, for example app-prod-01 or win-finance-02.
• A current web browser: Chrome, Edge, Firefox, or Safari released within the last 12 months.
• If your portal offers a desktop client as a fallback: permission to install software on your computer.
• If your organization requires a VPN (virtual private network, a secure connection into the company network) before portal access, have that VPN login ready.

Steps

Step 1: Open the remote access portal

Open your browser and go to your portal URL exactly as provided by your agency or IT contact.

https://portal.your-company.example

What you should see: a sign-in page with your organization name and fields for email/username and password, or a button such as "Sign in with SSO".

Step 2: Sign in with your assigned account

Use the login method your organization gave you.

If you use a direct portal account:

Username: your assigned portal username
Password: your assigned portal password

If you use SSO, click the SSO button on the portal sign-in page, then complete your company login.

If prompted for multi-factor authentication, enter the 6-digit code from your authenticator app or approve the sign-in request.

What you should see: the portal home page, usually with a list of resources such as servers, hosts, assets, or connections.

Step 3: Find the server you need

In the portal, use the search box or resource list to find the exact server name you were given.

Use the server name exactly, for example:

app-prod-01

Common menu paths vary by provider, but look for one of these patterns in your provider's dashboard:

Portal Home → Resources → Servers
Portal Home → Assets → Search
Portal Home → Connections → Available Targets

Click the server name once it appears in the list.

What you should see: a details page or side panel for that server with a button such as "Connect", "Launch", "Start session", or "Open in browser".

Step 4: Start a browser-based session

Choose the browser option first if the portal offers more than one connection method.

Typical button labels:

Connect
Start session
Launch
Open in browser
Web RDP
Web SSH
Web Console

If the portal asks you to pick a protocol (the connection type), choose the one that matches the server:

If the browser asks for permission to open pop-ups, click Allow for the portal site and click the connect button again.

What you should see: a new browser tab or embedded session window showing either a Windows login screen, a Linux terminal prompt, or a server console.

Step 5: Log in to the server when prompted

The portal gets you to the server; you may still need the server account itself.

For a Windows server, enter:

Username: the Windows username provided to you
Password: the Windows password provided to you

For a Linux server in a web terminal, enter your username when prompted, then your password. If the terminal asks whether to trust a new host key, accept it only if your organization told you to use that exact server name.

What you should see: the Windows desktop, or a Linux shell prompt similar to one of these:

C:\Users\yourname>

yourname@app-prod-01:~$

Step 6: If the browser session does not open, use the portal's client option

Some portals work better with a local client than with an in-browser session.

In the server details page, look for one of these options:

Download client
Open in desktop app
Native client
RDP file
SSH config

If the portal downloads an RDP file for Windows access, open the downloaded file and continue.

If the portal provides a hostname and port for SSH, use the exact command it shows. A common format is:

ssh yourname@server.example.com -p 2222

If the portal provides a one-time command, copy and paste that exact command instead of guessing.

What you should see: the desktop client opens and connects, or your terminal shows a login prompt for the target server.

Verify it works

Use the check that matches your server type.

For a Windows server:

• The remote desktop window opens.
• You can click the Start menu or open File Explorer.
• The session title or banner shows the expected server name.

For a Linux server, run:

hostname

Expected result: the output matches the server you intended to reach, for example:

app-prod-01

Then run:

whoami

Expected result: your assigned username, for example:

yourname

If the portal itself shows connection status, it should change to a success state such as:

Connected
Session active
Live

Common pitfalls

You signed in with the wrong account

Mistake: using a personal email, an old portal account, or the wrong SSO tenant (identity directory).

Symptom: you can log in, but the server list is empty or the target server is missing.

Fix: sign out completely, sign back in with the exact account named in your access email, and complete MFA for that account.

Pop-ups are blocked in the browser

Mistake: the browser blocks the session window when you click Connect.

Symptom: nothing opens, or you briefly see a blocked pop-up icon in the address bar.

Fix: allow pop-ups for the portal site, then click Connect or Start session again.

You picked the wrong protocol

Mistake: choosing SSH for a Windows server or RDP for a Linux server.

Symptom: the session fails immediately, or you see a blank screen or protocol error.

Fix: go back to the server page and select RDP for Windows or SSH for Linux.

The portal session opens, but the server login fails

Mistake: entering your portal password into the server login prompt.

Symptom: "invalid username or password" after the portal session has already started.

Fix: use the server credentials provided for that machine; portal credentials and server credentials are often different.

The server is there, but you do not have permission to start a session

Mistake: your account can view the asset but not connect to it.

Symptom: the Connect button is missing, disabled, or returns an access denied message.

Fix: request the specific role or access grant for that server from your administrator, then refresh the portal and try again.

A stale browser session is interfering

Mistake: an old login session or cached portal page is stuck.

Symptom: repeated redirects, blank session pages, or the portal shows outdated resource data.

Fix: sign out, close all portal tabs, open a private/incognito window, and sign in again at the portal URL.

This article was written by an AI system and published pending human review. Verify anything you intend to act on.