Every tax season the same question comes up in CA offices: how do staff working from home get remote access to the Tally server without putting client data at risk? Usually someone forwards a port on the router, Remote Desktop works from home, and everyone moves on. That shortcut is the single most common way small-office servers get attacked. This post compares the realistic options honestly, including where our own product fits and where it does not.
First, what you are actually choosing between
Staff at home need two things: a network path to the office server, and a way to use Tally once they get there. For most small offices the second part is Remote Desktop (RDP), and that part rarely changes. The decision is about the path. You can let the internet reach RDP directly, put a gateway in front of it, or make staff join a private network first.
| Option | Needs a public or static IP at the office? | Second factor (MFA)? | Main risk |
|---|---|---|---|
| RDP port forwarded to the internet | Yes | No | Every password-guessing bot on the internet can reach your sign-in screen |
| RDP allowed only from known IP addresses | Yes | No | Home broadband addresses change, so the list breaks or gets widened |
| RD Gateway | Yes | Possible, with extra setup | The gateway itself faces the internet and must be patched |
| VPN on the office router or firewall | Usually | Depends on the device | VPN appliances are a favourite target; firmware must be kept current |
| Hosted or mesh VPN service | Usually not | Often, through the provider’s sign-in | A monthly subscription and one more vendor with access to your network |
| Prixl Guard Secure Access | No (in the default “Prixl Magic” mode) | Not yet | Staff app is Windows 64-bit only today |
Option 1: RDP open to the internet
Forwarding port 3389 (or any other port) from the router to the server makes the Windows sign-in screen reachable from anywhere. Automated tools try usernames and passwords against such servers around the clock. Remote Desktop has no built-in second factor, so one guessed or reused password is enough. Moving RDP to a different port only reduces log noise, because some scanners check every port. Our guide to RDP security risks covers this in detail. Treat this option as the thing you are moving away from.
Option 2: allow RDP only from known addresses
A firewall rule that accepts Remote Desktop only from specific public IP addresses closes the door to everyone else. It works well for a partner with a fixed office connection at another branch. It works badly for articles and staff on home broadband or a phone hotspot, because those addresses change. In practice someone widens the rule during the September rush “just for now”, and it stays wide. Our post on restricting RDP access safely shows how to set the rule up properly if this suits you.
Option 3: RD Gateway
Remote Desktop Gateway is a Windows Server role that wraps RDP inside HTTPS, so only port 443 faces the internet instead of RDP itself. You can add multi-factor sign-in with Microsoft’s NPS extension for Microsoft Entra MFA, but read the prerequisites first: it needs a Network Policy Server, Active Directory synchronised to Microsoft Entra ID, and a paid Entra ID P1 or P2 licence for each user. It is a solid design for a firm with a domain and a capable IT vendor. For a ten-person office on a workgroup it is a lot of moving parts, and the gateway still needs a reachable public address and regular patching.
Option 4: a VPN on the office router or firewall
Many business routers and firewalls can act as a VPN server. Staff connect to the VPN, then open Remote Desktop to the server’s office address, and RDP itself is never visible from the internet. This is a big improvement on Option 1, with three caveats.
- The router needs a public IP address that people can reach. If your provider puts your connection behind carrier-grade NAT (CGNAT), a router VPN simply cannot accept connections.
- The VPN device becomes the thing attackers target. The NSA and CISA’s 2021 guidance on selecting and hardening remote-access VPNs warns that exploited VPN servers have led to stolen credentials and remote code execution. Keep the firmware updated and turn off features you do not use.
- Give each person their own VPN account, never one shared login, so you can remove someone the day they leave.
Our explainer on what a VPN is and when to use one covers the types in more depth.
Option 5: a hosted or mesh VPN service
Several companies sell VPN services where both the server and each laptop connect outwards to the provider, which then joins them up. Because nothing has to accept an inbound connection at the office, these usually work behind CGNAT and need no router changes. Many plug into a sign-in provider that can add a second factor. The trade-offs are a per-user subscription, another vendor that sits in the path to your server, and settings that someone has to own. Check where the provider stores its data and how quickly you can remove a user.
Option 6: Prixl Guard, a private tunnel run from your Warden dashboard
Prixl Guard Secure Access belongs to the same family as Option 5, built into Prixl Warden. Staff reach the office server through an encrypted WireGuard tunnel, and Remote Desktop can then be closed to the internet with the setting “Lock RDP to Secure Access only”. The admin invites each person from the “Secure Access” tab in the Warden dashboard; the person enters a one-time invite code (valid for 24 hours) in the Guard app, and access can be revoked from the same tab at any time.
The default connection method, “Prixl Magic”, needs no router setup and no static IP. It works behind most office routers and CGNAT, with an automatic relay as a fallback. A second method, “Classic Static IP”, is for offices that do have a real public IP and can forward UDP port 51820.
The limits, plainly. The staff app runs on Windows 64-bit only: there is no Mac, iPhone or Android app today. Guard does not add a second sign-in factor yet; Windows still asks for each person’s password. Guard comes with the Warden + Guard plan, which includes 5 seats; extra seats start at ₹600 per seat per year (see pricing). It is not part of the free trial.
Whichever you choose, do these too
- One Windows account per person. No shared “tally” or “office” login.
- Passwords of at least 15 characters, the minimum for single-factor sign-in in NIST SP 800-63B-4 (2025); passphrases are fine.
- Network Level Authentication on, and an account lockout policy set, remembering that the built-in Administrator is exempt from lockout on Server 2022 and older unless “Allow Administrator account lockout” is enabled.
- Remove remote access on the day someone leaves, including articled assistants at the end of their term.
- Check the home laptops before the season starts. A route that only works on Windows, or only on the office’s own laptops, needs to be known in July, not discovered in September.
A quick way to decide
If you have a domain, an IT vendor who already runs Microsoft 365 with Entra ID, and a static IP, RD Gateway with MFA is a strong choice. If you have a static IP and a decent business firewall, a router VPN is reasonable, provided someone owns its updates. If you have no static IP, are behind CGNAT, or simply want the fewest moving parts, look at a hosted VPN service or Guard. In every case, the goal is the same: nothing on the internet should be able to reach your server’s Remote Desktop sign-in screen directly.
Prixl Warden watches the server whichever route you pick: failed and successful sign-ins, password-guessing patterns, and sign-ins outside working hours. Start your 30-day free trial and see who is already knocking on your server’s door.
