Before you access the labs you must install Citrix Receiver on your local machine. Go to the Citrix Receiver download via web browser to download/install the appropriate desktop software. Once installed please reboot your system.
Citrix Web Interface
- Once logged into the Live Labs interface you will be set into Pod Control which is under Home>Labs>Go to Lab. You can launch the Citrix Live Labs interface by clicking PC-Console under Pod Links found on the left side of the page.
- You should see desktop icons corresponding to your class and pod assigned by your instructor. Launch the icon you have been assigned by clicking it in the interface.
- If the desktop launches then leave open the Citrix desktop page during your lab time.
Citrix Web Interface Troubleshooting
- If you click on the desktop icon and nothing happens you may need to add https://desktop-gw.remotelabs.com to your trusted sites in Internet Explorer/Edge.
- When you click the icon it responds “Cannot start desktop <name of desktop>” please right click the icon and select “Restart” Wait 1 minute for the desktop to restart and launch. You may need to click the icon again or refresh the web page depending on your browser.
- If your browser downloads a file or doesn’t seem to do anything when connecting to the desktop your browser may need to have the Add-ons or Plug-in enabled for Citrix ICA Client in the settings/options for the browser.
- If you continue to have issues launching the desktop please try a different browser if you have the availability.
- Please inform your instructor if problems continue.
- If you are having issues with the current Citrix Receiver for Windows provided directly from Citrix.com please download the legacy version below. Before installing please uninstall Citrix Receiver from the “Programs and Features” section of the “Control Panel” and reboot your system.
The Enter command allows you to connect to your pod and take a lab on real equipment. If you reach this page 15 minutes or less before the lab starts, you will see a clock on the upper left that counts down to the lab start time. During the last 7-9 minutes of this countdown, the equipment is being set up for the lab that has been reserved. Once the countdown is over, the equipment is ready for that lab. A countdown of your remaining time to actually perform the lab then starts.
The clock time is listed using the web server's local time and is regularly updated via NTP so as to be very accurate.
When you click a network device on the topology diagram, you will go straight to a a telnet session connecting you to the device.
Once the telnet session starts, an access server may present you with a password prompt. Enter the same password that you used to log into the lab system. You should see an acknowledgement saying "Password OK" or "Console Active. Press enter to see prompt." When you see either message, you are now allowed to use the device console, but you must hit the <Enter> key again to get the device to prompt you.
Depending on the lab exercise, you are likely to get another password prompt at this point. If you do, it will not be your lab system password, because you are no longer being prompted by the access server, but rather, by the actual network device. The lab instructions should tell you what the passwords will be for network devices.
Important Note: in a very small number of cases, the lab exercise purposely leaves the device powered down and you will therefore get no response on the console until you turn its power on. Sometimes, the device configuration is blank and you are prompted about entering the system configuration dialog. Please read the lab instructions carefully to see what state the device is expected to be in, before using the device.
Notes on Special Keystrokes Break sequences are occasionally required, e.g., for password recovery on a router. To do this, click the "Send break" button on the device tab.
Acknowledgements Live labs use the Java Telnet applet, Copyright © 1996 - 2005 Matthias L. Jugel, Marcus Meissner. Java Telnet sessions are redirected to their final target system using software based on the mrelayd program Copyright © 1996, 1997 Marcus Meissner.
On the Lab Session page, you will see several device links below the clock. You can click the pod link and see several actions:
- Reset To... - offers to reset your equipment to the start state (preconfiguration) of any lab supported by the and for which you have usage privileges. You may also specify that a compatible saved configuration be restored during the reset operation. If you use the "Change Doc" button rather than the "Reset" button, it will change the lab document without performing any reset.
Important Note: If you reset the equipment, you will be prevented from using the system for a period of several minutes, since the reset requires total control of the equipment during that time.
- Topology - connect to your pod topology diagram to do the lab
- Setup Results - allows you to see the results of all the setup activity for this reservation (scheduled setup at the beginning, plus all resets.)
- Save config (some courses) - saves the configuration of all relevant devices. You can use the configurations link (near the bottom left) to look at these configurations and copy them to your workstation, and Reset to... link to restore them.
- Save config copies the existing configuration to non-volatile RAM (NVRAM) and captures a copy of that. So when you use Save config, you are also updating all devices' NVRAM with their running configurations.
- You cannot restore a configuration to a different type of pod, nor a pod with a different pod number, than the one on which you saved it.
Before attempting any access to the devices in the labs, you should consider the firewall setting. The "firewall wizard" on the main labs page and the login page helps you to determine whether you have any firewall or proxy restrictions that affect the use of graphical-based lab devices. The firewall wizard should recommend to you one of four choices:
- Tarantella - telnet is actually run from within the lab system, and is therefore unaware of any port restrictions on your corporate network. The session is supported on port 443 through the SSL-encrypted Tarantella system. This should work for almost all corporate firewalls.
Important Note: If you take two or more reservations using Tarantella back-to-back, it is important to log out of the Tarantella window and close its browser window, in between the two reservations.
- RDP - a single connection is made to the lab system via a Terminal Services or Remote Desktop Client on port 3389. On the lab system, all applications are offered from an application launcher. The details of running them vary significantly based on both browser and operating system. A few suggestions:
- IE6 / Windows XP: on the new window that shows the RDP file details (starting with "screen mode id", etc.), go to the IE File menu and choose the Edit with Remote Desktop Connection command.
- IE7 / Windows XP: on the new window that shows the text of the RDP file details (starting with "screen mode id", etc.), right-click the text, click "Select All", right-click the selected text, and click "Copy". This will put the RDP file contents to your clipboard. Create a new file on your desktop called "gklabs.rdp" or "gklab443.rdp" (depending on the mode chosen), edit this file with notepad and paste the text from the popup window to that file. Double click the file to start the Remote Desktop client.
- Firefox / Windows XP: Choose "Open with: RDP.file".
- Pre-XP Windows: cancel download, but run terminal services client, setting host and user manually. The host and username were specified in a dialog that popped up when choosing the firewall mode.
- Firefox / Unix: choose "Save file" and run the resulting file via the command "tsclient -x filename".
- If nothing else works: cancel download, but run terminal services client, setting host and user manually. The host and username were specified in a dialog that popped up when choosing the firewall mode.
- RDP 443 - a single connection is made to the lab system via a Terminal Services or Remote Desktop Client on port 443. See the RDP firewall mode above for other details.