Remote access to the office in Algeria (2027): working from home or abroad on the company software, for when remote desktop does not work or is left open to the whole internet

“My accountant wants to work from home two days a week, my salesperson is on the road, and I spend the summer in France. We tried remote desktop: one day it works, the next day it does not. An IT person ‘opened a port’ on our router, and we also use a free remote-control tool that keeps disconnecting. How do we reach the office software from outside, reliably, without getting hacked?” There are three routes: an open port, which has to be closed; an encrypted tunnel to the office, which suits almost every case; and the software itself on the web, which removes the problem. The rest is a matter of accounts, PCs that stay on, and upload rate.

Symloop13 min read
Remote access to the office with no open portWorking from home or abroad on the company software: encrypted tunnel, named accounts, a measured lineREMOTE ACCESS · ALGERIA · 2027Remote access to the officewith no open portWorking from home or abroad on the company software: encryptedtunnel, named accounts, a measured lineAN OPEN PORTvisible to the whole internetAN ENCRYPTED TUNNELan account, a second codesymloop.com

Short answer. You do not open remote desktop to the internet: you first enter the office network through an encrypted tunnel, with one account per person and a second code, then open your session as if on site. Microsoft says so itself: forwarding a port opens the PC to the internet, which is not recommended, and a virtual private network is preferable. When remote desktop “does not work”, the cause is almost always one of six: PC switched off, address that changed, address shared by the operator, Windows Home edition, account, saturated line. And the lasting way out, when the software allows it, is to turn it into a web application.

This guide is for the manager of a company with five to two hundred workstations where part of the team works away from the office, an accountant at home, salespeople, travelling management, and for the founder based in France who wants to open the software of their Algerian company. The facts quoted come from public sources: Microsoft's documentation on remote desktop, and the definitions of the protocol, of address translation at the operator and of wake-on-LAN. The people, rates and delays in the example are constructed. This guide gives no hardware prices and does not cover the rules that apply to network equipment and encryption: check those with your operator and your legal adviser.

Three ways into the office: only one leaves the door open

The figure follows the same person along three routes: a port opened on the router, an encrypted tunnel, then the software turned into a web application.

Figure 1 · The same person reaches the office software by three routes. With a port opened on the router, they reach the PC, and so do the strangers who scan the internet: 3389 is the default port of remote desktop. With an encrypted tunnel, they enter the network with their account and a second code, and strangers stop at the router. With a web application, there is no PC left to reach. Schematic of a constructed example.

The open port. The remote desktop protocol listens by default on port 3389. To reach it from outside, that port is forwarded on the router: forwarding simply maps a port on the public address to a PC in the office. It works, and that is the problem: the PC then answers anyone. Microsoft's documentation says it plainly: you are opening your PC up to the internet, which is not recommended. In May 2019, a flaw named BlueKeep, in Microsoft's remote desktop implementation, allowed remote code execution; against an exposed and unpatched service, the attacker no longer even needs to guess a password. What can follow is described in the guide to ransomware.

The tunnel. With a virtual private network, nothing is opened towards the PCs: the accountant's computer sets up an encrypted tunnel to the office router, with her account and a second code, and finds itself in the network as if she were there. She then opens her remote desktop session on her own PC, or on a server. It is the principle of the tunnel between two sites in the guide to linking sites, applied to one person. The web application. If the management software exists as a web version, or can be rebuilt that way, there is no PC left to reach: everyone opens a browser. That is the route described in the guide to migrating old software. Remote-control tools. They are fine for fixing things, but a free account shared by five people is not working access: no named accounts, no log, and a dependence on an outside service.

«The question is not how to open remote desktop, but through where you enter the office network.»
01

Remote desktop does not work: six causes, in the order they are checked

The figure gives, for each cause, the sign that reveals it and what is done.

Figure 2 · Six causes, in the order they are checked, from the most ordinary to the most technical. The first four have nothing to do with security: a PC switched off, an address that changes, an operator that shares its address, a Windows edition that accepts no connection. None is solved by opening one more port.

The PC is off or asleep. It is the most ordinary cause: someone switched the PC off when leaving, or it went to sleep. Sleep is turned off on the PCs concerned, and wake-on-LAN is turned on, a standard that allows a computer to be switched on or woken from sleep by a network message. The address changed. The public address of an ordinary line changes; a hard-coded connection then looks for an address that is no longer yours. The tunnel relies on a name that is updated automatically, which is what dynamic DNS does. The operator shares the address. Some connections, mobile ones in particular, go through address translation at the operator, which usually prevents its customers from using port forwarding: nothing gets in, whatever the router's configuration. You ask for a public address, or use a tunnel set up from the office outwards.

The Windows edition. The PC you connect to must run the Pro edition; the computer you connect from can run any edition. A PC on the Home edition will not accept an incoming connection. The account. A password changed at the office, an account not allowed to connect remotely, or a shared account that two people use at once: in practice, on an ordinary Windows PC, the remote connection takes the place of the session open on site. The line. A frozen picture and lagging typing come from the office line, dealt with below. If the software itself is slow, even on site, the cause lies elsewhere: see the guide to the slow server.

02

Clean remote access, in six steps

The second step is accented: before installing anything, you close what is open.

Figure 3 · The accented step is the second: before installing anything, every port forwarding on the router is listed and closed, including the one “set up one day to fix something”. The last step is done with each person, from the place where they will really work.

List: who needs what, and from where. The accountant needs the accounting software, not the whole network; the manager, their dashboards and their mail. Close: every port forwarding on the router is listed and removed, including the one “set up one day to fix something”. Install the tunnel: on the office router, with current encryption, and a client on each authorised computer.

Create the accounts: one per person, with a second code, and access limited to the PCs or the server each one needs; what to do when an account is compromised is in the guide to hacking. Prepare the PCs: Pro edition, sleep turned off, wake-on-LAN, updates. Try it: from outside, on 4G, with each person, before announcing that “it works”. For files alone, a shared space is often enough, with no remote session: see the guide to file sharing.

03

What the office line must send: upload rate and delay

The figure calculates the bandwidth the office sends for six remote people, then places three delays on a scale.

Figure 4 · Remote desktop sends the picture of the screen: what counts is the office’s upload rate. With the figures published by Microsoft, six people on management software need 1.2 Mbit/s; if one of them browses the web inside the session, 7.5; if they play a video, 10.5, more than the line. At the bottom, the round-trip delay: no discomfort up to 150 ms, fine for text up to 200 ms. People, line and delays are a constructed example.

Bandwidth. Remote desktop sends the picture of the screen; so it is the office's upload rate that counts. Microsoft publishes figures for a 1920 × 1080 screen: 100 to 150 kbit/s for a word processor, 150 to 200 for a spreadsheet, but 6 to 6.5 Mbit/s for web browsing inside the session and 8.5 to 9.5 for video. In the example, six people on the management software need 1.2 Mbit/s; if just one opens a news site inside the session, the total goes to 7.5; if they play a video, it exceeds the line's 10 Mbit/s, and the other five slow down. The rule is simple: in the session, you work; web and video are watched on your own computer.

Delay. The round-trip delay between the remote computer and the office is not fixed by more bandwidth. For its virtual desktops, Microsoft indicates that a delay of up to 150 ms does not hinder work without video, that between 150 and 200 ms text work remains fine, and that beyond 200 ms the experience may suffer. It is measured from the place where you work, at the time you work. One server for several. When several people must use the same software at the same time, they connect to a session server rather than to individual PCs; each user or device that connects to it then needs a client access licence, to be planned with your reseller.

«In the session, you work; web and video are watched on your own computer.»
04

Serious remote access, in five layers

The accented layer is the route: it decides what a stranger can try.

Figure 5 · The accented layer is the route: it decides what a stranger can try. Accounts, above, say who comes in; the target and the computer, below, say to what and with what; follow-up keeps the record of everything.

Who: named accounts and a second code; when someone leaves, their account is closed the same day. Through where: a tunnel or a gateway, never a remote desktop port on the router. To what: your own PC, a session server, or the web application.

With what: a company computer, up to date and encrypted, rather than the family computer; if the personal computer is the only option, the remote session at least keeps the data at the office. Follow-up: a connection log, alerts on repeated failures, an account review every quarter; this is the routine work described in the guide to managed IT.

05

Remote access in place in 2027, in weeks

Three weeks in the example, the first with nothing changed.

  • What the manager sees: who has remote access, since when, each person's last connection, and no remote desktop port open on the router.
  • What the company no longer does: share a remote-control password, leave a port open “for now”, call the office to have a PC switched back on, discover a forgotten access after someone leaves.
  • What is measured: upload rate and round-trip delay from outside, successful and refused connections, accounts inactive for thirty days.
  • What Symloop does: the stock-take and the measurement, the tunnel and the accounts, preparing the PCs or the session server, then, when the software justifies it, rebuilding it as a web and mobile application.
Figure 6 · Three weeks in the example, the first with nothing changed. The accented week is the tunnel and the accounts, tried by two people before everyone; ports are closed only once the tunnel has proved itself, so that nobody is cut off.

Week 1, stock-take and measurement: who connects and to what, which forwardings are open on the router, which Windows edition on each PC, what upload rate and what delay measured from outside. Week 2, tunnel and accounts: the tunnel is installed, the accounts are created, and two people use it for a week.

Week 3, switch-over and closing: everyone goes through the tunnel, the ports are closed, the remote-control tools removed, the log in place. And after. If the software stays painful from a distance, because it is heavy or the line cannot keep up, the question is no longer access: it is the software, which has to be hosted differently or rebuilt as a web application.

How do I reach my office computer from home?
In two stages. First an encrypted tunnel to the office network, with your account and a second code; then remote desktop to your PC, which must be switched on and running the Pro edition of Windows. No port is forwarded on the router for this.
Why does remote desktop not work?
Six causes keep coming back: the PC is off or asleep, the office's public address has changed, the operator shares the address and nothing can get in, the PC runs the Home edition, the account is not allowed or its password has changed, or the line is saturated. They are checked in that order.
Is it dangerous to open the remote desktop port on the router?
Yes. The PC becomes reachable by anyone on the internet, and only the password, or the latest update, stands between a stranger and your network. Microsoft's documentation states that it is not recommended and that a virtual private network is preferable.
What is a company VPN, and do we need one?
It is an encrypted tunnel between an outside computer and the office network, installed on the office router. It has nothing to do with the consumer services used to change country. You need one as soon as a person has to reach a PC, a server or a folder at the office from outside.
Can I work from France on the office software in Algeria?
Yes, through the same tunnel. What decides the comfort is the round-trip delay between the two countries and the office's upload rate: measure them on an ordinary day. Management software gets through well; design software or a video inside the session gets through badly.
Do the office computers have to stay on?
The PC you connect to must be on and must not go to sleep. Wake-on-LAN allows it to be switched back on remotely. When several people work remotely every day, a session server that is always on is simpler than individual PCs.
Can several people connect to the same PC?
Not at the same time: in practice, an ordinary Windows PC holds only one session, and the remote connection takes the place of the one open on site. For several people on the same software, a session server is used, with a client access licence per user or per device.
How much bandwidth does remote desktop need?
Little for management software: Microsoft's figures are 150 to 200 kbit/s for a spreadsheet. A lot as soon as someone browses the web or watches a video inside the session: 6 to 9.5 Mbit/s. It is the office's upload rate that counts, not the rate at home.
Are free remote-control tools enough?
For helping a colleague, yes. For working every day, no: no named accounts, no connection log, an account that is often shared, and an outside service on which all access depends. Working access is installed on your premises, in your name.
Can I connect from my personal computer?
You can, but it is the weak point: a shared family computer that is not up to date opens the office session. At the very least, a separate account on that computer, updates, and no local copy of the files. The ideal remains a company computer.
Tell us how many people work away from the office, on which software, and what your line's upload rate is: we come back with the route that fits and what has to be closed

An accountant at home, salespeople on the road, travelling management, or a founder in France opening their company's software: we close the ports, install the tunnel, create the accounts and measure the line

A one-week stock-take, an encrypted tunnel, one account per person with a second code, and, when the software justifies it, its rebuild as a web application. We work from Algiers and Sétif, in French, Arabic and English.