Network Test
A device can be joined to Wi-Fi and still be unable to do anything useful, because something between it and the internet is blocking the way. Network Test tells the two apart.
Say "ABOUT DEVICE" from My Programs, then "NETWORK TEST".
What each check means
The test works outwards, from the local network to the services the device depends on. Where it stops tells you where the problem is.
| Check | What it proves |
|---|---|
| Internet | The device can reach a public DNS server, so basic internet routing works. |
| The device can reach an ordinary website, so name lookup and web traffic work. | |
| Cloud API | The device can reach the service that manages it. |
| Storage | The device can download a file, which is what app and configuration downloads depend on. |
| Cloud Access | The device can reach the management portal. |
| RealTime Server | The device can reach the video calling backend. Only needed for calls; everything else works without it. |
| Connectivity Hub | The device can reach the messaging service it is managed through, which is what lets applications be pushed to it. |
Reading the result
Everything passes. The network is not the problem. Look elsewhere.
Everything fails. The device is not really on the network at all, whatever the Wi-Fi icon says. Check it has joined, and check the network itself works from something else.
The first checks pass and the later ones fail. This is the common case and it means a firewall. The device has internet access but specific addresses or ports are blocked. Take the list of failures to whoever runs the network; the ports and addresses required are published separately.
Only RealTime fails. Video calling via the RealWear One companion app will not work. Everything else will. This is not related to the Collaborate app.
When to run it
Run it before reporting a connection problem. "The device cannot connect" and "the device passes every check except Connectivity Hub" describe very different problems. The second is far quicker to resolve.