mirror of
https://github.com/1Remote/1Remote.git
synced 2026-04-25 13:36:03 +03:00
[GH-ISSUE #147] NX as connection option #122
Labels
No labels
area-configuration
area-ct-app
area-ct-rdp
area-ct-remoteapp
area-ct-ssh
area-ct-vnc
area-launcher
area-list
area-tags
area-teamwork
bug
chore
dependencies
general-build/ci
general-performance
general-refactor
general-security
general-supportive
general-ux
meta-documentation
meta-enhancement
meta-enhancement
meta-feature
meta-help-wanted
meta-unknown-error
priority-hi
priority-low
pull-request
question
resolution-duplicate
resolution-invalid
resolution-wontfix
stale
task-put-off
task-still-considering
task-working-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/1Remote#122
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Josephkready on GitHub (Aug 15, 2021).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/147
Originally assigned to: @VShawn on GitHub.
Describe the solution you'd like
Having NX (NoMachine) as a connection option. If I have nomachine service installed on a machine, I would like to use PRemoteM to connect to that machine using the NX protocol.
NX protocol seems to be much faster than xrdp for linux machines. It could be challenging to integrate, so I am interested on what you think.
@majkinetor commented on GitHub (Aug 15, 2021):
Never heard about it.
Here is some quick info for others.
Why would I use this over standard RDP and friends
@VShawn commented on GitHub (Aug 16, 2021):
Hi I've considered FreeNX protocol when I create the demand planning at 2020.04.
https://github.com/VShawn/PRemoteM/projects/3#card-38295433
But afert some investigations, here are some challenges we meet:
1. open by command line
NoMachine client can start connection only by passing a config file to it.
2. password storage
In the file
arm.nxsI didn't see a field storaged the password, but cmd.\nxplayer.exe D:\arm.nxsdid not request me to enter a password. So we don't know how to genterate a NoMachine config file containing a password by PRemoteM.3. Integer
cmd
.\nxplayer.exe D:\arm.nxswill start a process A, then A will exit and start new process B (not a sub-process of process A) to show the remote desk window.Then PRemoteM can not capture the PID of process B, which means we cannot integer NoMachine client window into the tab window of PRemoteM.
I‘m still looking for solutions for these challenges, no progress yet.
@VShawn commented on GitHub (Oct 26, 2021):
A new protocol: APP is add to the PRM:
github.com/VShawn/PRemoteM@ea3ca701d7so that you can assign the nxplayer.exe path and nomachin config file *.nxs, then start the connection with PRM
For now you have to create *.nxs by yourself in NoMachine
Annnnd since I dont find the solution to hosting then NX View in the PRM, so PRM will just open a new process of nxplayer, the NX-UI will not be integrated in my tab view
And here is the approach to create a *.nxs file, but I'm not intend to investigate if it is the correct approach.
See also:
Command line options for the NoMachine client
Preconfigure Username and Password
The password scrambling algorithm in NX Client
@VShawn commented on GitHub (Nov 6, 2021):
merged into main branch #161
@VShawn commented on GitHub (Dec 8, 2021):
@Josephkready hi, here is our new beta release, you can try it with NX