Chapter 5Network, branches and Clarus Link
This chapter is for the support technician and the laboratory's network administrator. It explains:
- how the server is opened to the laboratory's network, and closed again;
- how a member computer joins its branch's server, and leaves it;
- how the branches of a chain are linked and exchange their data;
- what Clarus Link is, and how work goes on from outside the laboratory.
All of it is done in the program's Branches and linking screen, which has three pages: Branches, Branch devices and Samples sent.
5.1 How the computers and the branches are linked
| Link | Between | Over |
|---|---|---|
| A member computer and its server | The computers of one branch | The laboratory's network, once the server is opened to it |
| A branch and the other branches of a chain | The branches' servers, and the centre | A direct address, Clarus Link, or both |
| Outside the laboratory | A member computer, a manager's phone, and the server | Clarus Link, over the internet |
Each branch has its own server and its own database (see 2.3 Server or member). Linking branches does not make one database. Each branch keeps its own and exchanges with the others.
5.2 Opening the server to the laboratory's network
As installed, the program on the server answers that computer alone. Before any other device reaches it, the server must be opened to the laboratory's network.
Before opening it:
- The administrator has a password. The program does not open the server to the network's devices before that.
- The page is opened on the server computer itself. Elsewhere it shows the network's state and does not change it.
- The computer is connected to the laboratory's network, and Windows classes that network as private.
Steps:
- In Branches and linking, on the The laboratory's network card, press Open it and confirm.
- Windows shows its approval window on the server. Choose "Yes". The card waits until Windows applies the change.
- The program starts again on its new address. Press Start on the new address if the page does not move by itself.
Then the card shows The address the devices use: the address the laboratory's devices type to reach the program, or its number.
What opening does:
- It opens the program's port, and the member computers' port after it, in Windows' firewall, on private and domain networks only (see A.4 Firewall rules). Only the laboratory's network is opened, never the internet.
- It makes a certificate of the laboratory's own, so every connection is encrypted. On each device that opens the program in a browser, press Download the laboratory's certificate and install it once in "Trusted Root Certification Authorities".
To close it, press Close it. The program starts again and answers the server computer alone.
5.3 Joining a member computer
A member computer joins its server by its own licence number. The number tells it its branch.
On the server, before the new computer types its number:
- In Branch devices, on the Joining a new device to the branch's server card, type The new computer's licence number and press Allow it.
- The number may then activate itself within 24 hours.
On the member computer:
- Install it as "A computer in an existing branch" (see 2.3 Server or member).
- The first time the program starts, it asks for This computer's licence number. Type it as it came.
- The computer looks for its branch's server on the laboratory's network, and joins it.
- If it does not find the server, it asks for The branch server's name or address. The server's The laboratory's network card shows them.
The new computer then appears in Branch devices. If its state is Waiting for approval, choose it and press Approval.
The list of the branch's devices shows each computer's name, its licence, its route (Inside the branch or Through Clarus Link), and when the server last heard from it. Its filter shows the devices that are working, waiting for approval, without a licence, or working from outside.
To take a computer out:
- From the server: choose it and press Remove the device. Its sessions end at once, and it does not work until it joins again.
- From the computer itself: in its This device screen, press Leave the branch. It stops working until it joins again by its licence number.
5.4 When a member computer cannot reach its server
A member computer keeps the analysers' results that it could not send to the server. Its This device screen says how many messages wait, and since when. They go by themselves when the server answers again.
When the waiting place is full, the computer refuses new messages. The analyser then keeps its results and sends them again. Check that the computer reaches its server: the network, the cable, or the server itself.
5.5 Linking the branches of a chain
A chain is several branches, each with its server, and a centre. The centre sets the laboratory's identity, prices, reference ranges and public website, and they reach every branch from there.
The branches link by themselves from their licence numbers. When a branch server or a centre is activated, its numbers tell it which branches are its brothers, and it connects to them through Clarus Link (see 5.6 Clarus Link). There is no invitation to make and no key to type.
- A star around the centre. Each branch sends to the centre, and the centre passes it on to the others.
- A laboratory with no centre number: the server of branch B01 acts as the centre. Linking status names it, after The branch acting as the centre:
- A centre number issued later: the role moves from B01 to the centre once the centre holds everything. Linking status follows the move. B01 then works as an ordinary branch, and nothing of its data is deleted.
- The internet cut between branches: each branch goes on working with its own server. What it changes waits, and is sent when the connection returns.
At a new branch:
- Install a "Branch server" (see 2.3 Server or member), and activate it with its own server number (see 3.3 Activating the licence).
- In the first setup, choose Join an existing chain. Its catalogue and users come from the centre, so their steps are reviewed, not written (see 3.1 The first setup). Open branches and linking opens Branches and linking, where the link to the centre shows.
Each link shows its state, its route and its last exchange:
| State | Meaning |
|---|---|
| Linked | The two branches exchange |
| Waiting for the key | The link is there, but the two servers have not yet confirmed each other. It clears by itself once both are activated and reach each other; if it stays, check each one's licence and Clarus Link (see 5.8 When the network or the link stumbles) |
| Paused | The exchange is stopped for now |
| Link ended | The two branches no longer exchange |
The branches exchange by themselves. Exchange now sends what waits at once. Between branches that cannot reach each other at all, the exchange travels as a file: one branch exports it, and the other takes it by Import a file.
5.6 Clarus Link
Clarus Link joins, through the supplier's server, two computers that cannot see each other. It serves:
- the branches of a chain whose servers are not on one network;
- a member computer working from outside its branch;
- the managers' phones.
The connection is encrypted end to end. The supplier's server holds no key to it and reads nothing of it. It knows only which laboratory connected, when, and how many bytes passed.
Clarus Link is a service enabled for each laboratory. Its state shows in Branches and linking, and on the home page among the services. When it refuses a branch, the program says why:
| What the program says | What to do |
|---|---|
| Clarus Link is not enabled for this laboratory | Contact the supplier to enable it |
| The trial has ended, so Clarus Link stopped | It returns when the service is enabled |
| Clarus Link does not recognise this copy yet | The copy must reach the update server at least once, and an activated copy must verify its licence online |
| Clarus Link is paused on the supplier's side | Nothing is wrong in the laboratory. Wait |
| Clarus Link already serves another copy holding this laboratory's identity | Run the laboratory's program on one computer only |
In every case, access through the laboratory's own address still works where it is set up.
5.7 Working from outside the branch
A member computer may be allowed to work from outside its branch, for example a manager's laptop. In Branch devices, choose the device and set Working from outside the branch: Closed, Always, or Until a day.
The condition is set by the program: the device's Windows account has a PIN or a password, and its disk is encrypted with BitLocker.
A device can also be marked trusted. Then a user the manager chose signs in on it with the password alone, because the device's signature is the second factor. A personal device is never marked trusted. Its owner needs the app or an authenticator app (see 11.2 Password rules).
5.8 When the network or the link stumbles
| What shows | Likely cause | What to do |
|---|---|---|
| This computer is not connected to the laboratory's network. Connect it by cable or Wi-Fi, then check. | The server has no network | Connect it by cable or Wi-Fi, then press Check now |
| The card says the network is not private | Windows classes the network as public, so its firewall keeps the devices out | Press Make this network private on the server |
| Windows did not apply the change: the approval was declined | Its window was answered "No", or not answered | Open it again and choose "Yes" |
| The certificate names an address this computer no longer has | The server's address changed | Renew the certificate, then start again. Then fix the server's address in the router |
| No device joins before the server is opened to the laboratory's computers. | The server was not opened to the network | Open it (see 5.2 Opening the server to the laboratory's network) |
| The branch's computers cannot find the server, which was opened before its number was activated | The discovery rule is missing | Open the server to the computers again, and accept Windows' question |
| A member computer works through Clarus Link inside the laboratory | The server's network is public | Make the server's network private |
| The member's outbox is full | The member has not reached its server for a long time | Check the network and the server. The results go by themselves afterwards |
| A link between branches is late to exchange or failing | No route between the two servers, or Clarus Link refused | Read the link's route and Clarus Link's reason. Exchange by file meanwhile |
| A browser on a device warns that the connection is not private | The laboratory's certificate is not installed on that device | Install it once in "Trusted Root Certification Authorities" |