Update merlin7 nomachine docs
This commit is contained in:
parent
eff7143bfe
commit
fd16825e39
@ -1,130 +1,105 @@
|
|||||||
---
|
---
|
||||||
title: Remote Desktop Access
|
title: Remote Desktop Access
|
||||||
#tags:
|
keywords: NX, nomachine, remote desktop access, login node, login001, login002, merlin7-nx-01, merlin7-nx-02, merlin7-nx, rem-acc, VPN, browser access
|
||||||
keywords: NX, nomachine, remote desktop access, login node, login001, login002, merlin7-nx-01, merlin7-nx-02, merlin7-nx, rem-acc, vpn
|
last_updated: 07 August 2024
|
||||||
last_updated: 07 September 2022
|
|
||||||
#summary: ""
|
|
||||||
sidebar: merlin7_sidebar
|
sidebar: merlin7_sidebar
|
||||||
permalink: /merlin7/nomachine.html
|
permalink: /merlin7/nomachine.html
|
||||||
---
|
---
|
||||||
|
|
||||||
Users can login in Merlin through a Linux Remote Desktop Session. NoMachine
|
Users can log in to Merlin through a Linux Remote Desktop Session. NoMachine is a desktop virtualization tool similar to VNC, Remote Desktop, etc. It uses the NX protocol to enable a graphical login to remote servers.
|
||||||
is a desktop virtualization tool. It is similar to VNC, Remote Desktop, etc.
|
|
||||||
It uses the NX protocol to enable a graphical login to remote servers.
|
## New Feature: Browser-Based Access
|
||||||
|
|
||||||
|
We have now enabled browser-based access to Merlin7. This allows users to connect to the NoMachine service directly through a web browser, removing the need to install a client application. This is accessible via the following URL:
|
||||||
|
|
||||||
|
- **Browser Endpoint**: [https://merlin7-nx.psi.ch:4443](https://merlin7-nx.psi.ch:4443)
|
||||||
|
|
||||||
|
### How to Connect via Browser
|
||||||
|
|
||||||
|
1. Open your web browser and navigate to [https://merlin7-nx.psi.ch:4443](https://merlin7-nx.psi.ch:4443).
|
||||||
|
2. Enter your credentials when prompted. **Do not add `PSICH\`** as a prefix for the username.
|
||||||
|
3. Follow the on-screen instructions to launch a new session or reconnect to an existing one.
|
||||||
|
|
||||||
## Installation
|
## Installation
|
||||||
|
|
||||||
NoMachine is available for PSI Windows computers in the Software Kiosk under the
|
For traditional access, NoMachine is available for PSI Windows computers in the Software Kiosk under the name **NX Client**. Please use the latest version (at least 8.1.3). For macOS and Linux, the NoMachine client can be downloaded from [https://www.nomachine.com/](https://www.nomachine.com/).
|
||||||
name **NX Client**. Please use the latest version (at least 8.1.3). For MacOS and
|
|
||||||
Linux, the NoMachine client can be downloaded from https://www.nomachine.com/.
|
|
||||||
|
|
||||||
## Accessing Merlin7 NoMachine from PSI
|
## Accessing Merlin7 NoMachine from PSI
|
||||||
|
|
||||||
The Merlin7 NoMachine service is hosted in the following machine:
|
The Merlin7 NoMachine service is hosted on the following machine:
|
||||||
|
|
||||||
* **`merlin7-nx.psi.ch`**
|
- **`merlin7-nx.psi.ch`**
|
||||||
|
|
||||||
This is the **front-end** (hence, *the door*) to the NoMachine **back-end nodes**,
|
This is the **front-end** (hence, *the door*) to the NoMachine **back-end nodes**, which contain the NoMachine desktop service. The **back-end nodes** are the following:
|
||||||
which contain the NoMachine desktop service. The **back-end nodes** are the following:
|
|
||||||
|
|
||||||
* `login001.merlin7.psi.ch`
|
- `login001.merlin7.psi.ch`
|
||||||
* `login002.merlin7.psi.ch`
|
- `login002.merlin7.psi.ch`
|
||||||
|
|
||||||
Any access to the login node desktops must be done through **`merlin7-nx.psi.ch`** .
|
Any access to the login node desktops must be done through **`merlin7-nx.psi.ch`**.
|
||||||
|
|
||||||
{% comment %}
|
The **front-end** service running on **`merlin7-nx.psi.ch`** will load-balance the sessions and log in to any available nodes in the **back-end**.
|
||||||
(or from **`rem-acc.psi.ch -> merlin7-nx.psi.ch`** when connecting from outside PSI).
|
|
||||||
{% endcomment %}
|
|
||||||
|
|
||||||
The **front-end** service running on **`merlin7-nx.psi.ch`** will load balance the sessions
|
**Only one session per back-end** is possible.
|
||||||
and login to any of the available nodes in the **back-end**.
|
|
||||||
|
|
||||||
**Only 1 session per back-end** is possible.
|
Below are all the steps necessary for configuring access to the NoMachine service running on a login node.
|
||||||
|
|
||||||
Below are explained all the steps necessary for configuring the access to the
|
### Creating a Merlin7 NoMachine Connection
|
||||||
NoMachine service running on a login node.
|
|
||||||
|
|
||||||
### Creating a Merlin7 NoMachine connection
|
#### Adding a New Connection to the Front-End
|
||||||
|
|
||||||
#### Adding a new connection to the front-end
|
Click the **Add** button to create a new connection to the **`merlin7-nx.psi.ch` front-end**, and fill up the following fields:
|
||||||
|
|
||||||
Click the **Add** button to create a new connection to the **`merlin7-nx.psi.ch` front-end**, and fill up
|
- **Name**: Specify a custom name for the connection. Examples: `merlin7-nx`, `merlin7-nx.psi.ch`, `Merlin Desktop`
|
||||||
the following fields:
|
- **Host**: Specify the hostname of the **front-end** service: **`merlin7-nx.psi.ch`**
|
||||||
* **Name**: Specify a custom name for the connection. Examples: `merlin7-nx`, `merlin7-nx.psi.ch`, `Merlin Desktop`
|
- **Protocol**: Specify the protocol that will be used for the connection. *Recommended* protocol: **`NX`**
|
||||||
* **Host**: Specify the hostname of the **front-end** service: **`merlin7-nx.psi.ch`**
|
- **Port**: Specify the listening port of the **front-end**. It must be **`4000`** for the **`NX`** protocol.
|
||||||
* **Protocol**: specify the protocol that will be used for the connection. *Recommended* protocol: **`NX`**
|
|
||||||
* **Port**: Specify the listening port of the **front-end**. It must be **`4000`**.
|
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
#### Configuring NoMachine Authentication Method
|
#### Configuring NoMachine Authentication Method
|
||||||
|
|
||||||
Depending on the client version, it may ask for different authentication options.
|
Depending on the client version, it may ask for different authentication options. If required, choose your authentication method and **Continue** (**Password** or *Kerberos* are recommended).
|
||||||
If it's required, choose your authentication method and **Continue** (**Password** or *Kerberos* are the recommended ones).
|
|
||||||
|
|
||||||
You will be requested for the crendentials (username / password). **Do not add `PSICH\`** as a prefix for the username.
|
You will be requested for the credentials (username/password). **Do not add `PSICH\`** as a prefix for the username.
|
||||||
|
|
||||||
### Opening NoMachine desktop sessions
|
### Opening NoMachine Desktop Sessions
|
||||||
|
|
||||||
By default, when connecting to the **`merlin7-nx.psi.ch` front-end** it will automatically open a new
|
By default, when connecting to the **`merlin7-nx.psi.ch` front-end**, a new session automatically opens if none exists.
|
||||||
session if none exists.
|
|
||||||
|
|
||||||
If there are existing sessions, instead of opening a new desktop session, users can reconnect to an
|
If there are existing sessions, users can reconnect to an existing one instead of opening a new desktop session by clicking the appropriate icon (see image below).
|
||||||
existing one by clicking to the proper icon (see image below).
|
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
Users can also create a second desktop session by selecting the **`New Desktop`** button (*red* rectangle in the
|
Users can also create a second desktop session by selecting the **`New Desktop`** button (*red* rectangle in the image below). This will create a second session on the second login node as long as it is up and running.
|
||||||
below image). This will create a second session on the second login node, as long as this node is up and running.
|
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
### NoMachine LightDM Session Example
|
### NoMachine LightDM Session Example
|
||||||
|
|
||||||
An example of the NoMachine session, which is based on [LightDM](https://github.com/canonical/lightdm)
|
An example of the NoMachine session, which is based on [LightDM](https://github.com/canonical/lightdm) X Windows:
|
||||||
X Windows:
|
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
## Accessing Merlin7 NoMachine from outside PSI
|
## Accessing Merlin7 NoMachine from Outside PSI
|
||||||
|
|
||||||
### No VPN access
|
### No Direct Access Without VPN
|
||||||
|
|
||||||
No VPN access from outside is not possible for the pre-production phase, since it requires advanced network knowledge to do so, and the external **rem-acc.psi.ch**
|
During the pre-production phase, direct access to the NoMachine service from outside the organization is not supported. To access the service, you must first connect to PSI's VPN. The external **rem-acc.psi.ch** service does not yet allow direct access to the new cluster without a VPN connection.
|
||||||
service does not allow access to the new cluster yet.
|
|
||||||
|
|
||||||
{% comment %}
|
### VPN Access
|
||||||
Access to the Merlin7 NoMachine service is possible without VPN through **'rem-acc.psi.ch'**.
|
|
||||||
Please follow the steps described in [PSI Remote Interactive Access](https://www.psi.ch/en/photon-science-data-services/remote-interactive-access) for
|
|
||||||
remote access to the Merlin7 NoMachine services. Once logged in **'rem-acc.psi.ch'**, you must then login to the **`merlin7-nx.psi.ch` front-end** .
|
|
||||||
services.
|
|
||||||
{% endcomment %}
|
|
||||||
|
|
||||||
### VPN access
|
|
||||||
|
|
||||||
Remote access is also possible through VPN, however, you **must not use 'rem-acc.psi.ch'**, and you have to connect directly
|
|
||||||
to the Merlin7 NoMachine **`merlin7-nx.psi.ch` front-end** as if you were inside PSI. For VPN access, you should request
|
|
||||||
it to the IT department by opening a PSI Service Now ticket:
|
|
||||||
[VPN Access (PSI employees)](https://psi.service-now.com/psisp?id=psi_new_sc_cat_item&sys_id=beccc01b6f44a200d02a82eeae3ee440).
|
|
||||||
|
|
||||||
|
Remote access is possible through VPN; however, you **must not use 'rem-acc.psi.ch'**, and you have to connect directly to the Merlin7 NoMachine **`merlin7-nx.psi.ch` front-end** as if you were inside PSI. For VPN access, you should request it from the IT department by opening a PSI Service Now ticket: [VPN Access (PSI employees)](https://psi.service-now.com/psisp?id=psi_new_sc_cat_item&sys_id=beccc01b6f44a200d02a82eeae3ee440).
|
||||||
|
|
||||||
## Advanced Display Settings
|
## Advanced Display Settings
|
||||||
|
|
||||||
**Nomachine Display Settings** can be accessed and changed either when creating a new session or by clicking the very top right corner of a running session.
|
**NoMachine Display Settings** can be accessed and changed when creating a new session or by clicking the top right corner of a running session.
|
||||||
|
|
||||||
### Prevent Rescaling
|
### Prevent Rescaling
|
||||||
|
|
||||||
These settings prevent "bluriness" at the cost of some performance! (You might want to choose depending on performance)
|
These settings prevent "blurriness" at the cost of some performance! (You might want to choose depending on performance)
|
||||||
|
|
||||||
* Display > Resize remote display (forces 1:1 pixel sizes)
|
|
||||||
* Display > Change settings > Quality: Choose Medium-Best Quality
|
|
||||||
* Display > Change settings > Modify advanced settings
|
|
||||||
* Check: Disable network-adaptive display quality (diables lossy compression)
|
|
||||||
* Check: Disable client side image post-processing
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- Display > Resize remote display (forces 1:1 pixel sizes)
|
||||||
|
- Display > Change settings > Quality: Choose Medium-Best Quality
|
||||||
|
- Display > Change settings > Modify advanced settings
|
||||||
|
- Check: Disable network-adaptive display quality (turns off lossy compression)
|
||||||
|
- Check: Disable client-side image post-processing
|
||||||
|
Loading…
x
Reference in New Issue
Block a user