Troubleshooting a Lab Connection

Modified on Thu, 18 Jan at 3:45 PM

If you're having trouble connecting to a lab template or class lab, try these tips.



Most people have no trouble connecting to an OrasiLabs lab.  Once a Lab Template or Class Lab has been defined, you can Start it to initialize the required resources.  After the lab is completely started and running, you will see a live thumbnail of the resource in the current window.  You can then Enlarge this thumbnail to connect and manipulate the lab.

 

For more information about creating or starting lab templates, refer to Customizing Lab Images.  For more information about defining class labs, refer to Creating an Instructor-led Class or Creating an On-demand Class.

 

For example, when you Start a lab template, you will see an image like the one below.  You can then Play the thumbnail to connect to the running lab.

 


Troubleshooting Your Connection

If for any reason you don't see the image thumbnail shown above, then there might be a problem with your network connection to the OrasiLabs service.  Listed below are a few things to check that might resolve the issue.  If you continue to have trouble connecting even after trying these things, contact OrasiLabs Support for more help diagnosing the problem (select Help in the top right of any OrasiLabs window).

 

1. Try Connecting From A Different Computer

Though it might seem obvious, the first thing to try is to connect to OrasiLabs from a different computer.  This will help to identify whether the connection problem is localized to a specific machine or a common, network-wide symptom.  Sometimes local caching or customized settings are the culprit and testing from another machine will help to identify this.

 

2. Check Your Browser Version

OrasiLabs supports most modern browser versions.  Click here for a list of the known compatible browsers.  If you are using a compatible browser, make sure it is updated to the latest revision level offered by the vendor.  Most browsers have the ability to automatically update themselves, but if that setting is not enabled, you may have to manually update it.

 

NOTE:

  • Microsoft Internet Explorer is not supported because it lacks some of the modern connectivity features used by OrasiLabs.  Microsoft has announced "End Of Life" for Microsoft Internet Explorer and recommends that Microsoft customers use the latest version of Microsoft Edge instead.  Microsoft Edge is supported for use with OrasiLabs.

3. Check Browser Extensions

Some browser extensions will block the internet connection necessary to access a remote resource.  These might include extensions like Ad Blocker or Antivirus plug-ins.  Try disabling any browser extensions and reconnecting to the lab.  You normally have to close and reopen the browser after disabling the extensions.

 

NOTE:

  • Using an "Incognito" or "Private" browsing mode may also disable browser extensions.  Check your browser features to determine whether this is an alternative way to test without browser extensions.

4. Check VPN Connections

Although it doesn't always happen, some VPN software will block the internet connection necessary to access a remote resource.  Try disabling the VPN and reconnecting to the lab.  You normally have to reboot your client machine in order to fully disable the VPN once it has been turned off.

 

5. Check Antivirus Software

If your client machine is running antivirus or anti-malware software, it is possible that it's blocking the websocket network protocol.  Ensure your antivirus settings do not block websockets.

 

Also, antivirus firewall rules could be blocking connections to the OrasiLabs server.  If possible, add "<tenant>.orasilabs.net" (where <tenant> is the name of your OrasiLabs tenant) as a safe domain name in your antivirus settings.

 

6. Add Network Routing/Firewall Rules

Finally, if none of the machine-specific conditions seem to be causing the problem, it's possible that network routing rules are blocking traffic to the OrasiLabs server.

 

First, check whether the websocket protocol is enabled on your network.  If not, you will need to request that websockets be enabled for your connections.  You will likely need to contact your network administrator for this information.

 

Second, you may need to request a network routing/firewall rule to allow connections to the OrasiLabs servers.  If so, the following URLs will need to be whitelisted:

  • *.orasilabs.net

-- OR --

  • <tenant>.orasilabs.net (where <tenant> is the name of your OrasiLabs tenant)

  • ws.orasilabs.net

  • streaming.orasilabs.net

  • guacamole.orasilabs.net

  • api.orasilabs.net

Third, if you use external port resources in any of your lab templates, you will additionally need to whitelist the following URL:

  • *.orasilabsdns.net

Contact OrasiLabs Support

Finally, If you continue to have trouble connecting even after trying these things, contact OrasiLabs Support for more help diagnosing the problem.  Select Help in the top right of any OrasiLabs window to initiate a support request.

 

Where to go next...

 


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article