Technical Anshu
Tutorials Blog
🖱️ Remote Control

Endpoint Central Remote Control Not Connecting Fix

You click Connect, the viewer spins, and nothing happens. Remote control has its own ports and its own service on the client — when either is missing, the session never starts.

✍️ Technical Anshu🪟 Windows Clients⏱️ 10 minute fix
🎥 Watch the installation that sets up remote control correctly in the video

A remote control session in Endpoint Central is an on-demand task plus a live screen stream. The request travels on the task channel, and the session itself uses the remote control ports on the server — 8443 for the secured session and 8444. On the client, a dedicated service, ManageEngine UEMS - Remote Control, has to be alive to accept the session. A spinning viewer almost always means one of those three things is missing. Here is the full check.

Endpoint Central — Remote Control Viewer
TargetSALES-LAPTOP-05
StatusConnecting to remote machine...
ElapsedSession never established
The viewer that spins forever — the request went out, the session never came back
1

First Question — Is the Agent Even Online

  1. Check the machine in Agent → Computers. If it shows offline, remote control has no path at all — fix the agent connection first (ports 8020 and 8383, agent service running)
  2. Confirm someone is not mid-reboot or on a VPN that just dropped. A session to a sleeping laptop fails politely and silently
  3. Try remote control on a wired desktop next to the server. If that works, your problem is the path to that one machine, not the feature
2

Open the Remote Control Ports on the Server

  1. Add inbound exceptions on the Endpoint Central server for 8443 (remote control, secured) and 8444 (remote control)
  2. Do not forget 8027 — the on-demand task port that carries the connect request itself, along with scans and remote shutdown
  3. If your browser reaches the console over a network firewall or the machine sits in another segment, the same ports must be allowed on that path too
  4. Test from your own PC with Test-NetConnection -ComputerName SERVERNAME -Port 8443
3

Start the Remote Control Service on the Client

  1. On the target PC, open services.msc
  2. Find ManageEngine UEMS - Remote Control and make sure it is Running with startup type Automatic. ManageEngine's own troubleshooting repeatedly points at this service for failed on-demand features
  3. If the service is missing entirely, the agent install on that PC is incomplete — reinstall the agent from Scope of Management
4

Check the Human Settings Before Blaming the Network ⭐

  1. If your remote control settings ask the user for confirmation before connecting, the session waits at the user's screen. A user who is away or who clicks Deny looks exactly like a technical failure from your side
  2. For unattended servers and kiosks, review the remote control settings in the console and set the confirmation and logging behaviour your company policy actually wants
  3. Keep session recording and audit options in mind — in many organisations the honest limit on remote control is policy, not technology, and the audit log is what keeps the feature allowed
⚠️ Remote office machines still failing? Cross-branch sessions depend on the WAN path allowing the task and session ports. That is the exact scenario ManageEngine's distribution server and Secure Gateway designs exist for — do not punch the main server open to the whole internet as a shortcut.

🎥 Watch the Setup Behind Remote Control

The installation video covers the agent and console basics every remote session stands on.

▶️ Watch Full Video
❓ Frequently Asked Questions

Remote control works inside the office but not for a branch user. Why?

The session ports are open on your LAN but not across the branch path. Branch and roaming machines need the ports reachable over VPN, or the Secure Gateway and distribution server design for WAN management. Test port 8443 from the branch side to confirm.

The viewer connects but shows a black screen. Is that the same problem?

Not quite — the session established, so ports and service are fine. A black screen usually means the machine is at a locked or secure desktop state, a display driver quirk, or the user session is not the one you expected. Reconnect after the user unlocks, and check you are viewing the active session.

Can the user see when I connect remotely?

Endpoint Central can be configured to prompt the user for approval and to notify them during the session, and sessions are logged. What your users experience depends on the remote control settings your admin chose — which is a policy decision worth making deliberately.

This guide is based on the Technical Anshu video on Endpoint Central installation • Stuck on a step? Ask in the video comments and you will get a reply 🙏