In order to make sure that the Remote Labs Client works with your device, please read the System Requirements. Afterwards, please Download the right version for your OS in the Download area and open the file. Follow the installation routine. The picture below shows the installation dialogue for Windows.

Open the client by clicking the Remote Labs Client icon in the start menu.
After the client has been opened the first time you will be asked to adjust the window resolution for remote connections as well as the keyboard layout.

Please Note: The Keyboard Layout affects the remote desktop sessions only. The terminal sessions are using your local keyboard settings.
When working with VNC connections, the keyboard layout has to be adjusted on the target machine.

Additionally a connection test will be performed to assure that all neccesary servers can be accessed. If you encounter a red result please check your firewall settings and click Recheck to test again. The picture below shows the settings dialogue for Windows.
You can open the settings window later by clicking on the  button.

You will be directed to the actual login page of your Remote Labs Service. Please log into your lab by typing your username and password.

You are ready to start working on your lab now. Please follow the Guide.

Please download, install and configure the Remote Labs Client and log into your Remote Labs Service. Read Installation and Configuration for clear instructions.

After your login, you will reach the Start page. Basic information on your lab will be displayed. Please check the Notes-document for more information on your lab.

Please click on Network Diagram(s) -> Pod x. You will be directed to your network diagram. Click on a device to access it.

On the Lab Administration page a list of devices and the option to clear them is displayed.

Please use the help content provided on the Landing Page. Additionally we offer personal support for trainers through our trouble ticket system. Please select “Support Tickets” after logging into your lab.

Need further help?

The Remote Labs Client is a native application to guarantee easy lab access when working with the Fast Lane Remote Labs Services. You do not need to install any additional software as the client comes with everything you need to work on your lab.

Currently the Remote Labs Client works with Windows and OS X.

The access data sent by Fast Lane will come with a Labname such as „L-Labname-X123“. The X represents the location of the lab and is one of the following: H=Hamburg, B=Berlin, F=Frankfurt.
If the access data subject starts with REMOTELABS- the lab is located in Frankfurt.
If you have not gotten your access data, please contact the support team and ask them directly.

You can change them in the Remote Labs Client settings area. Click the  button on the right side to open the window.

The Remote Labs Client will be installed on your device and can simply be removed by deinstallation. Installation and configuration paths for Windows and Mac are:

Windows:
Installation Path: C:\Users\%USERNAME%\AppData\Local\FastLane\RemoteLabsClient\
Configuration Files Path: C:\Users\%USERNAME%\.fastlane

Mac:
Installation Path: /Applications/
Configuration Files Path: /Users/%USERNAME%/.fastlane

The Remote Labs Client works with the remote desktop solution X2Go. Read more here.

You are logged in with the trainer account which is not able to connect to devices without an established student session. Please use the student account to connect to devices. The trainer account can only ghost sessions from students.

Press <F8>, then “Send ctrl-alt-del”.

It is not possible to access the Fast Lane Remote Lab System directly using a Proxy. If a Proxy must be used due to company policies, please see the proxy section in the System Requirements.

When you are logged in as a trainer you can clear lines using Lab Administration in the menu. This only concerns Remotelabs 1.0.

Please check if there is a local firewall blocking your access.

Press <Alt> + <b> to send a break signal. Or you can press <Ctrl> + <right click> for special commands.

Using Remotelabs 1.0: To copy text from the console client, select the text with your left mouse button. To paste into the console client, simply right click with your mouse.

Press <CTRL> + <SHIFT> + <X>

This problem can be solved by changing your screen arrangement. Choose Apple menu > System Preferences, click Displays and then click Arrangement. You will see the arrangement of your screens indicated by two blue boxes. The primary screen will have a white bar at the top of the blue box. From this point, you have to options to solve the problem.

1. Select the blue box with the bigger resolution as primary screen.

2. In case you would like to keep the resolution of the primary screen bigger than the resolution of the secondary screen, you need to arrange the blue boxes in a way so they align at the bottom.

Please check the list below for an explanation of the symbols.

RDP connection
VNC connection
Serial connection
XDMCP connection
Device is powered off. Click to power it on.
Device is powered on. Click to power it off.
Reset device

The shadowing feature can be used by a trainer to log into a students POD in order to help the student. Please read the instructions on how to establish a shadow session below.

Step 1 –  Student establishes Master Session connecting to a device

Ask the student to establish a connection to a device. The shadow feature will not work if the student is not connected!

Step 2 – Trainer establishes Shadow Session connecting to the same device 

– Log into the lab as a trainer and click on “Lab”. Select the students POD in the dropdown menu in the right upper corner.

– Establish a connection to the same device as the student.

– You can now help the student using the shadowing feature

Hint: If you are getting a “No Desktop found” error when trying to establish a shadowing session, please check if the student has already established a connection to a device.

There are dynamically generated local ports for localhost sockets. They do not establish an outside connection and therefore do not need to be allowed on your firewall.

CTRL and + (zoom in)
CTRL and – (zoom out)
CTRL and 0 (default, 100%)
CTRL and D (default, 100%)

The Connection Test assures that all necessary servers can be accessed. Using Windows, it can be found in the “Settings” menu, using OS X, in the “Preferences” menu. The image below shows the Connection Test for Windows.

+ Removes links and access to RL2.0
+ Connection test reworked to match current infrastructure changes
+ Improved Keymappings on macOS

+ Save log feature via menu bar / help
+ 4k display support
+ DPI support
+ Direct links to RL1.0 and RL2.0 via menu bar
+ Improved Keymapping for VNC-Connections

+ Changed System Check access IPs

+ Improved System Check that checks simulated remote lab device connections
+ Improved scroll bar behavior for smaller screen size resolutions
+ Improved terminal windows settings
+ Apple Mac OS X El Capitan support

+ Issue *.dll not found fixed
+ Putty window size optimization for ssh/telnet connections
+ Shortcut improvements (Zoom in/out)
+ Minor Bugfixes
+ Search function within the Remote Labs Client accessible via menu

+ Settings and connection test directly accessible through the symbol bar
+ Concurrent connection issues fixed (error message: failed to create SSH proxy tunnel)

+ Release

If the installation process stops and doesn’t continue (e.g. picture below) please check your desktop firewall or antivirus program. Some users encountered issues with Avast Antivirus and the software doesn’t show a message and blocks the installation process hidden for the user.
In order to install the Remote Labs Client (RLC) please stop your desktop firewall or antivirus programm for the installation and reactivate it afterwards.

Sometimes the Remote Labs Client (RLC) can’t start because *.dll (e.g. Qt5Core.dll) is missing from your computer. In order to get the RLC running you can copy all *.dll files from the installation path to your System32 folder under your windows installation.

From: C:\Users%USERNAME%\AppData\Local\FastLane\RemoteLabsClient\

To: C:\Windows\System32\

Users of Windows x64 have to copy the *.dll files to the following folder as well:

To: C:\Windows\SysWOW64\

If the Remote Labs Client won’t open Putty / Terminal connections with the following log output:

x2go-INFO (1): Starting x2goclient…
x2go-INFO (1): libssh version:0.6.4
x2go-INFO (3): Started x2goclient.
x2go-INFO (1): Starting x2goclient in hidden mode…
x2go-INFO (8): Starting connection to server: rl1ffm-x2goserver02
x2go-INFO (12): Connection established.
x2go-INFO (9): Opening Session, starting command.
x2go-WARNING (5): Waiting for proxy to exit.
x2go-WARNING (6): Failed, killing the proxy.
x2go-INFO (6): Closing x2goclient…
x2go-INFO (7): Closed x2goclient.

Due to an updated “libz” file from Apple you have to delete the existing one in the Remote Labs Client Installation.

The Remote Labs Client needs to be started an you can delete the following two files (and empty them from the Recycle Bin).

/Applications/RemoteLabsClient.app/Contents/Resources/x2go/x2goclient.app/Contents/Frameworks/libz.1.dylib

$HOME/.fastlane/x2go/x2goclient.app/Contents/Frameworks/libz.1.dylib

Note:

The Quickest Way to Show/Hide Hidden Files

Since the release of macOS Sierra, when in Finder, it is now possible to use the shortcut:

CMD + SHIFT + .

Fast Lane Europe

Fast Lane America

Phone: +49 (0)40 2533 4618
eMail: info@flane.de
Website: http://flane.de

Phone: +(1) 855 778 7246
eMail: info@fastlaneus.com
Website: http://fastlaneus.com