Tutorial: Build a Windows Remote Office Workflow with MoonProxy

[chenxxpro]

Background

Many office computers sit behind a corporate firewall with no public IP. This tutorial shows how to expose a Windows workstation to the internet using MoonProxy -- no router changes, no public IP needed.

Who this is for

• Homelab enthusiasts
• Developers who cannot open ports at the office
• Users behind strict NAT / firewall policies

Step-by-step

1. Prerequisites

• A Windows 10 / 11 workstation (the remote side)
• A Linux VPS with a public IP, ports 7000 and 6000 open
• frps running on the VPS (MoonProxy bundles one as sidecar)

2. VPS-side frps config

[common]
bind_port = 7000
dashboard_port = 6000
dashboard_user = admin
dashboard_pwd = your_password

3. Workstation-side MoonProxy config

• Add config: name workstation / server vps.example.com:7000 / token same as above
• Add proxy: TCP / local_ip 127.0.0.1 / local_port 3389 / remote_port 13389

4. Connect from anywhere

• Any RDP client connects to vps.example.com:13389 - traffic is forwarded to workstation 3389
• Path: RDP -> VPS (relay, no decrypt) -> workstation

Advanced

• VSCode Server remote dev: same flow, remote_port 8001, local_port 8080
• Harden the VPS: run fail2ban to block scanners
• Multi-user isolation: each machine gets its own token + config file

FAQ

Q: How is this better than TeamViewer?
A: Fully self-hosted, zero monthly fee, full traffic control, no third-party dependency.

Q: Is a VPS mandatory? Can I use my home router instead?
A: MoonProxy works with any frps server, including home routers (OpenWrt + frp plugin). Symmetric NAT environments are best handled by a VPS though.

---

Share your remote office setup in the comments.