If something isn't working
Pick what you see, and work through the steps. Tick each one off as you go. Most problems are one of these.
Pick what you see
Start with the network in the window: the words under its name say what's happening.
Waiting for the network's administrator to approve this computer
Once they approve it, your computer connects by itself, usually within a minute.
Joining doesn't move past "Asking to join"
"The request has ended"
"Disconnected on this computer"
You're still a member: off only means off here. While it's off, its names are looked up as usual on this computer, as if MultiTunnel weren't there. Names from a network
"Connecting: none of the other devices reachable yet"
"On, but held"
While it's held, its names get no answer on this computer: they never go anywhere else. What each network says
Grey rings with an orange dot, or "MultiTunnel's service is not running"
A name doesn't open, but the network is connected
"Another network on this computer uses the same addresses"
That's handled for you: there's nothing to do. Names work as usual. Only a number address someone gives you, such as one for a printer, may be different on your computer. The network's page shows yours under Details.
Works on my computer but not in WSL, Docker or a VM
WSL2 (in its usual NAT mode), virtual machines on Hyper-V's Default Switch, and Docker containers don't reach your networks through this computer. On Linux, the same goes for Docker, libvirt and LXD guests. Otherwise anything running in them, even started by someone else who signs in to this computer, would reach your networks as your computer.
On Windows, a program inside such a guest gets no answer, and waits until it gives up; on Linux it is refused at once. On Windows, a port you share from a virtual machine through Windows' address translation (a static port mapping) doesn't answer your networks' devices either: run the service on this computer, or, in a full virtual machine, run MultiTunnel there.
Your antivirus says something about MultiTunnel
For administrators
Add exceptions for MultiTunnel's two programs, by full path, in every part of the product that can act on them: real-time scanning, behaviour monitoring, web protection, and the product's own firewall (allow multitunnel.exe, in and out).
C:\Program Files\MultiTunnel\multitunnel.exeC:\Program Files\MultiTunnel\mt-tray.exe
Where the product allows it, also except the folders C:\Program Files\MultiTunnel, C:\Program Files\MultiTunnel-setup and C:\ProgramData\MultiTunnel, and no more: never a whole drive, and never all of C:\ProgramData. The paths don't change between versions.
If files were quarantined already:
- Add the exceptions above first. Restored files can be quarantined again within minutes otherwise.
- Then restore them. If restoring in place fails, restore them to a folder of your own, and copy them back into MultiTunnel's folders from an elevated PowerShell.
- Never uninstall MultiTunnel, and never delete
C:\ProgramData\MultiTunnel: its keys can't be made again.
If anything is still missing, or the network won't connect, email us at enquiries@multitunnel.co.uk and we'll take you through the rest.
Something else
Still stuck? Send details to support.
Send details to support
- In the window, open This computer.
- Under For support, choose Copy details. Show the details lets you read them first.
- Paste them into an email, with a line about what went wrong and when, and what MultiTunnel said.
- Send it to your administrator. If they can't help, they'll pass it to us. You can also email us yourself at enquiries@multitunnel.co.uk.
What the details say
Which version of MultiTunnel you have, and on which system. On an administrator's account, they also give counts: how many networks the computer is in (never which), how many tunnels are working, and how many key exchanges failed.
What they never say
Keys, PINs or recovery keys; invites or reply codes; anything you send, receive or look up; names of networks, people or devices; addresses; or any ID that could pick out you, your computer or your network.
Never send passwords, PINs, recovery keys, admin keys, invites or reply codes to anyone helping you. Nobody at MultiTunnel will ever ask for them.
Command line
On Windows, in your own Terminal, as yourself (not as administrator), once you have set $mt and $st. On Linux, in a terminal. Before you start
As yourself, it gives the version, the system and the engine. The full counts need Terminal (Admin) on Windows.
& $mt diag $stsudo multitunnel diag /var/lib/multitunnelStill stuck?
Ask your network's administrator first: they can see your network and fix most things. For anything they can't, email us. A person will reply.