Steps for Remote Access
3. Submit us request for remote access with your IP address
- When scheduling your beamtime, submit to Sheila Trznadel (firstname.lastname@example.org) your request to run remote for approval.
- Note that remote access can be allowed from a requested pool of IP addresses only and only for the time of experiment.
- 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.
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 wrong credentials. See more details in FAQ.
7. Run your remote experiment
- For automatic NxClient-3.5 installation via Java (Linux and Windows only, see Step-5) proceed to Table-1a.
- For automatic NxPlayer-4 installation via Java (yet in testing phase, see Step-5) proceed to Table-1b.
- For manually installed NX clients including OpenNX 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
- Run NX™ session wizard for either NxClient-3.5 or NxPlayer-4 to fine-tune connection options, e.g. enable Adxv.
- For TeamViewer™, read TeamViewer™ FAQ and ask beamline host to start TeamViewer server for you.
- Remotely start MAR CCD software.
- 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.
- Also, Google Talk is available on blXws3 for on-site visitors who have a Google account.
- Pidgin instant messanging client supporting most networks is availble 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.
- Please be a good neighbor and logout from all workstations once your work is over.
Clicking these links initiates installation of free NxClient-3.5 on your computer.
The administrative access is not required, but the installation needs
Java Runtime Environment (JRE)
and a Java-enabled web browser. If you do not have these prerequisites, you can
still download and install a free standalone NxClient from
downloads. Then, use preconfigured NX™ sessions listed in Table-2
down this page to connect to the GM/CA @ APS beamlines. Right-click on the session
link in Table-2 to download the session file and then execute the
command "nxclient --session name.nxs". On some systems, e.g. Microsoft
Windows, this command can be launched by double-clicking on the session file.
NxClient-3.5 does not work on the latest Lion versions of Mac OS. See
respective FAQ for possible workarounds if you have Lion.
Gnome and KDE are two popular and functionally equivalent types of Linux
desktops that we use on our beamline computers. At present Gnome has been
used more frequently and hence it is a better tested and recommended option.
Use KDE only when you have problem connecting to Gnome desktop. Some known
cases are when users need to login locally and remotely on the same computer
at the same time.
Shadow sessions provide additional connections to an already running Gnome or
KDE sessions for collective viewing. They 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 since streaming multiple remote desktops may result is
a degraded performance.
Flowchart for choosing remote connection options under Linux and Windows
(click to enlarge)
Flowchart for choosing MacOS Lion remote connection options
(click to enlarge)