To launch and use a lab, the following requirements must be met:
- Use a supported operating system:
- Windows 7 or later
- Ubuntu 14.04 or later (or comparable distribution)
- macOS 10.12 or later
- Have a supported browser. IE, Edge, Chrome, Firefox, Safari.
- Latest version is preferred, but full support details can be found below
- Chromium based browsers such as Opera or Vivaldi can connect, but default hotkeys they set may interfere with lab inputs
- Be connected to a network that allows at least one of the following:
- Secure Web sockets on HTTPS port 443 and 43443
- Web sockets over HTTP port 80 and HTTP over Port 843 (Flash control) (Hyper-V only)
- RDP over port 21xxx or 443 (Enhanced control)
- VMware custom protocol over port 902 (VMware Remote Console Plug-in – vSphere only)
- For more information see Browser/Controller Support below
- Have administrative rights on the local machine if installing the Enhanced control (Hyper-V w/RDP only).
- Have administrative rights on the local machine if installing the VMware Remote Console Plug-In (vSphere only).
Firewall Exception Rule Information
For those that need to create a firewall exception rule to allow connectivity to the Lab on Demand servers (this isn't common), the following information can be used to create a limited destination rule to only allow the above protocols and ports from your network to the Lab on Demand cloud.
- Domain Names:
- *.labondemand.com (Hyper-V)
- *.learnondemandsystems.com (Hyper-V)
- IP Range:
- 184.108.40.206/25, 206.196.30.001 - 206.196.30.056
- 220.127.116.11/24 (Hyper-V Only)
- 18.104.22.168/24 (Hyper-V only)
The Lab on Demand system is a cloud platform that automatically provisions and connects the learner with private sandboxed resources. There is no way to predict which IP address in the cloud the learner will connect to for the provisioning of their virtual machines. Therefore, we provide a range of IP addresses and only a second level domain name.
For Hyper-V and Hyper-V w/RDP only labs, the domains and IP addresses in the table below may also be required as firewall exceptions. We strongly encourage using names, and not IP addresses, for firewall and proxy configuration if possible, as the IP addresses may change without warning (and without documentation update). This allows access even in network failover and future geographic targeting scenarios.
If specific IP addresses are required, use the following table as a guide for IP addresses:
|DNS name||IP Address 1||IP Address 2|
Launch a Test Lab
With this link Launch a LODS Virtual Lab: Legacy Lab Orientation you will launch a test lab. This will allow you to see if you are able to connect and function with-in the lab environment.
Connection Assessment Test
If you are experiencing frequent disconnects or lag when controlling your machines, you may run a connection assessment test. This page allows you to run a connection assessment test. A connection assessment test is a very deep and thorough test that measures throughput speed, capacity, and packet quality to assess the user experience of a connection to their respective data center. This includes efficiency, data loss, recovery, duplication of data, retransmissions and even corruption.
For help with analyzing the results of your test, please review the Interpreting Your Connection Assessment Results article.
When Connections Traverse a Proxy
When connecting to a lab instance via a proxy, certain configuration requirements must be met for each remote controller. For more information, please review the Proxy Requirements article.
When Using Windows Server Operating Systems
When connecting to Learn on Demand Systems Training Management Systems (TMS) portals with a computer having Windows Server operating systems on it, you may experience difficulty in connecting to the sign-in page or clicking on some buttons. Steps to remediate can be found here.
In-Lab Software Whitelisting Information for Lab Developers
Software that communicates with remote servers outside of the lab environment may need addresses whitelisted with the vendor to work. The below address ranges are used by NAT internet access labs.
- IP addresses/scopes: 22.214.171.124 126.96.36.199/24
- IP Ranges: 188.8.131.52 - 184.108.40.206, 220.127.116.11 – 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52
The below ranges are used by Public IP internet access labs.
184.108.40.206/24 220.127.116.11/24 18.104.22.168/24 22.214.171.124/23 126.96.36.199 - 188.8.131.52 184.108.40.206 - 220.127.116.11 18.104.22.168 - 22.214.171.124 199.101.111.05 - 126.96.36.199
Machines in your lab can be accessed using any one of five virtual machine controls depending on the type of lab you are running. You can freely change between controls on those virtual machines not using RDP to find the one that works best for you.
|Virtual Machine Control||Chrome||Firefox||Internet Explorer||Microsoft Edge|
|Flash||11+||Websockets||80 & 843 2||11+||Websockets||80 & 843 2||11+||Websockets||80 & 843 2||11+||Websockets|
|Silverlight||4-34 5||HTTP||80||4-52 5||HTTP (RDP), HTTPS||80 (RDP), 443||4+||HTTP||80 (RDP), 443||N/A||N/A|
|Enhanced 3||N/A||N/A||N/A||N/A||N/A||N/A||8+||VMRDP||21xxx or 443||N/A||N/A|
|VMware Remote Console (vSphere) 4||N/A||N/A||N/A||11-56||Custom||902||8+||Custom||902||N/A||N/A|
2 Port 843 is required by Flash Socket Policy to authorize the use of Web sockets
3 Requires Internet Explorer. The 21xxx value depends on which host server in the cloud the lab is running on. If connection on port 21xxx fails, the Enhanced client will rollover and attempt the connection on port 443.
4 Windows and Linux only, not supported on Firefox version 57 or later
5 Support for NPAPI plugins (silverlight) was removed with version 45 of Chrome and 52 of Firefox. The plugin is not supported on Linux or macOS