Steps for Remote Access
Before your beamtime starts
3. Submit us request for remote access with your IP address
- When scheduling your beamtime, submit to Sheila Trznadel (email@example.com) your request to run remote.
- Note that remote access can be allowed from a requested pool of IP addresses only and only for the time of experiment.
- Also, if you are behind a proxy or firewall, your IP address presented to us may differ from what you see locally.
- Run Check IP Address tool to check your IP and email the requested pool of IP addresses to your host.
- Provide host with a phone number where you can be reached during remote experiment.
On the day of your remote experiment
5. Have NxPlayer or TeamViewer installed
- We offer four methods for remote connections to GMCA computers, three using different ways of installing NOMACHINE™ NxPlayer and one using TeamViewer™ (click to see the flowchart). With all four methods the supported operating systems are Linux, MacOS, and Windows.
- If you already have NxPlayer installed, then clear NX cache and proceed to Step-6.
- If you do NOT have NxPlayer, first try Method-1: check if Java is operational in your browser. In case of any problems read Java on Linux and Java in browsers FAQ.
- If Java is operational, add https://www.gmca.aps.anl.gov to the Exception Site list on Java Control Panel (see details here). Then proceed to Step-6. A 32-bit version of NxPlayer will be automatically installed at Step-7 with no admin rights required.
- If Java is NOT operational, try Method-2: download and unpack portable version of NxPlayer from GMCA website. Then start nxplayer from the bin subdirectory of unpacked distribution.
- If neither Method-1 or Method-2 worked for you, download Enterprise NxPlayer from NOMACHINE web site and install it on your computer (admin rights required).
- Finally, if you prefer to use TeamViewer™ instead of NX (Method-4; admin rights required), follow the TeamViewer™ instructions page.
6. Check your credentials on the day of experiment
- You will receive remote login credentials (username and password) from your host over the phone at ~10am CST on the day of experiment.
- Beware that the Lab firewall treats multiple login failures as a hacking attack and blocks respective remote IP after 3 failures.
- Therefore it is very important that you run Check Credentials tool before trying to login remotely.
- Contact your host to find out what might be wrong if the tool reports incorrect login credentials. See more details in FAQ.
7. Run your remote experiment
- For automatic NxPlayer installation via Java (Method 1) proceed to Table-1.
- For manually installed NxPlayer (Methods 2 and 3) proceed to Table-2.
- Connect with NX to blXws2 for data collection
- Connect with NX to blXws6 for data analysis
- Connect with NX to blXws5 for data backups
- For TeamViewer™, read TeamViewer™ FAQ and ask beamline host to start TeamViewer server for you.
- Remotely start Rayonix-300 software (BM beamline only) or remotely start Pilatus3-6M or Eiger-16m servers (ID beamlines).
- Phone the beamlines if needed: +1(630)252-1823 for 23-IDD and +1(630)252-1723 for 23-IDB. The office phones of GMCA hosts are listed on the staff page.
- You can also use Skype to communicate with the beamline or an on-site part of your team.
- In addition, Google Talk is available on blXws3 for on-site visitors who have a Google account.
- Pidgin instant messaging client supporting most chat networks is available on all computers.
9. Logout once finished
- Check FAQ on how long you can use the remote workstations.
- Workstations blXws2 (data acquisition) and blXws6 (data processing) are available for the time of experiment only.
- Workstation blXws5 (data backup) is available for an extra day. It can be also used for data processing in case you have such need.
- Please be a good neighbor and logout from all workstations once your work is over.
Clicking these links initiates installation of free NxPlayer on your computer.
The administrative access is not required, but the installation needs
Java Runtime Environment (JRE)
and a Java-enabled web browser (not all browsers may work). Also, you need to add
https://www.gmca.aps.anl.gov to the Exception
Site list on Java Control Panel. If you cannot meet the above prerequisites, then
you need to gain administrative rights on your computer in order to install a free
standalone NxPlayer, which is available at the
Enterprise downloads (look for Enterprise Player). Finally, if none of the
above is possible (no Java, no admin rights), try this
hack. With the NxPlayer installed, use preconfigured NX™ sessions
listed in Table-2 to connect to the GM/CA @ APS beamlines.
Right-click on the session link in Table-2 to download the
session file. Then, start NxPlayer on your computer, skip to "Recent
connections" screen and open the saved NX session file. On some systems, e.g.
Microsoft Windows, this command can be launched by double-clicking on the session
Our beamline computers operate under CentOS-7, a free clone of Redhat Enterprise Linux-7.
We use Mate graphical destop as a faster alternative to Gnome3, the default desktop of
this operating system. For the sake of simplicity, other Linux desktops, such as Gnome3, KDE,
Unity, Xfce, Cinnamon, and etc., are not supported.
Shadow sessions establish additional connections to already running remote sessions.
They provide collective viewing/controlling of the same desktop. These sessions are
mostly meant for the GM/CA @ APS staff when there is a need to help users remotely.
Shadow sessions are not recommended for users with slow network connections since
streaming multiple remote desktops may result in a degraded performance. Be aware
that with NxPlayer, after opening the shadow session and connecting to remote
computer, you need to do Ctrl+Alt+DoubleClick (Cmd+Alt+DoubleClick on MacOSX) on
the running session icon in order to shadow it. See this FAQ
for additional details.
Flowchart for choosing remote connection options
(click to enlarge)