A graphical session needs its own service
RDP and VNC provide graphical access rather than an ordinary SSH shell. The remote machine must run the appropriate service, permit your account and accept the selected route. Installing OmniTerm does not itself enable Remote Desktop or a VNC server on another machine.
Graphical support is platform- and release-dependent. Use a supported native profile where required; do not assume every browser or mobile release has the same capabilities.
Connect to a desktop
- Confirm the administrator's approved protocol, address, port and authentication method.
- Create or open the matching RDP or VNC profile in the supported client.
- Review the security settings and any identity or certificate prompt before connecting.
- Open the remote graphical desktop control for that profile.
- Check the displayed machine before entering sensitive information or changing settings.
Clipboard, keyboard, resizing and other redirected features can differ by protocol and platform. Verify the actual feature you need rather than inferring it from the desktop being visible.
Trust the complete route
A desktop can display passwords, documents and private notifications. Only share it with authorized viewers. Do not expose an unprotected graphical service to the public internet to make it reachable; use the administrator's approved network path.
An encrypted outer connection does not make every inner service secure against every participant. A Gateway that handles a remote protocol is part of the trusted environment. Read privacy and trust for the distinction.
For individual remote application windows rather than a full desktop, see X11 applications. For failures, report the protocol, platform and route—not a screenshot containing private desktop content.