Windows Guides
MobaXterm to Mac Screen Sharing over SSH
MobaXterm can connect to a Mac screen through SSH when the tunnel and the VNC target are kept separate.
At a glance
- MobaXterm can either use an external tunnel script or its own SSH gateway settings.
- The Mac host and SSH port belong to the tunnel configuration.
- The VNC target should remain localhost when the Mac screen port is locked behind SSH.
Why MobaXterm is useful here
MobaXterm is popular because it brings terminal, SSH, and remote-session tools into one Windows app. That makes it a natural fit for technical users who want Mac screen access without installing a cloud remote desktop agent.
The key is to avoid treating MobaXterm as a reason to expose VNC directly. It can be used as the viewer while SSH remains the only network entry point.
Method one: external tunnel first
The simplest mental model is to run an external SSH tunnel script first, then create a MobaXterm VNC session pointed at localhost:5901. The script handles SSH. MobaXterm handles the screen viewer.
This method is easy to troubleshoot because the tunnel and viewer are separate. If SSH is not connected, fix the script or key. If SSH is connected but the screen does not open, inspect the VNC address, port, and screen-sharing password.
Method two: MobaXterm SSH gateway
MobaXterm can also define an SSH gateway inside the session. In that case, enter the Mac reachable address, the Mac-side SSH port, the username, and the private key in the gateway settings. Then keep the VNC session target on the local tunnel destination.
The same rule applies: the SSH configuration reaches the Mac; the VNC configuration reaches the screen service after the tunnel exists. Mixing those two fields is the common mistake.
- SSH gateway host: Mac LAN IP, WAN/DDNS host, or mesh VPN address.
- SSH port: the configured Mac-side SSH port.
- VNC target: localhost and the local port used by the tunnel.
A cleaner workflow with HearthGate
HearthGate generates connection material for Windows, manages the Mac-side SSH posture, supports restricted keys, and can keep VNC reachable only through the tunnel. MobaXterm remains a familiar Windows client rather than the security boundary.
That makes the workflow easier to explain: use MobaXterm for the session, use HearthGate for the Mac-side gate.
Want the Mac-side gateway for this model?
HearthGate packages secure VNC over SSH, restricted keys, firewall VNC lockdown, connection bundles, and session visibility into one native Mac app.
Explore HearthGate