Forum Replies Created
-
AuthorPosts
-
October 10, 2019 at 09:07 in reply to: White screen when tried to access a Linux Ubuntu machine from Windows 10 #23938BritgirlParticipant
Here is the Trouble Report’s link: https://www.nomachine.com/TR10Q09420
It also includes the known workaround. Please use the ‘notify me’ checkbox to receive notification of when a patch has been officially released.
BritgirlParticipantPlease check your email inbox – we sent you further instructions on how to do further debugging.
BritgirlParticipantHello, a Trouble Report has been opened: https://www.nomachine.com/TR10Q09425
You can sign up to receive notification of when a fix has been officially released using the ‘notify me’ service.
BritgirlParticipantDoes this help?
Disabling the automatic start-up of NoMachine at boot time
BritgirlParticipantAll users are invited to update the latest version.
October 4, 2019 at 14:34 in reply to: Multible desktop sessions, new terminal server, ‘The session negotiation failed’ #23872BritgirlParticipantDuring installation NoMachine detects the default desktop environment set on the system and configures the node accordingly. If you don’t want to run the default one, you change it. It could be that this is what causing the problems?
Firstly check that in the node.cfg that you have:
DefaultDesktopCommand "/usr/bin/startxfce4"
written there. More info is in our KB here: https://www.nomachine.com/AR04K00667BritgirlParticipantThe patch has been queued up (and already fixed) for the next available maintenance, but I can’t say exactly when that will be. We can send you over a link to download a patched package. Can you tell me if you are using RPMs 64 or 32 bit?
October 4, 2019 at 07:42 in reply to: Windows 10 configuration fix for dropped NoMachine connections? #23864BritgirlParticipantHi, this is weird. We’ve been unable to reproduce the behaviour that you have described above, with and without Samba, but to no avail. You mention “an obscure fix” you found on the internet. Can you pass us the link?
October 3, 2019 at 10:14 in reply to: Connection failed from NoMachine Windows client to Linux on AWS #23860BritgirlParticipantHi, to understand better what is happening, we need to see the server-side logs from the AWS CentOS machine.
Please follow the instructions here: https://www.nomachine.com/AR10K00697 and then send them to forum[at]nomachine[dot]com.
October 2, 2019 at 10:03 in reply to: Multible desktop sessions, new terminal server, ‘The session negotiation failed’ #23848BritgirlParticipantTerminal Server works out of the box for a myriad of distros and set-ups, so why are you getting that message is unclear. You don’t mention the desktop environment. You mention you have an older version (note that forums handles the latest version only), what’s not clear is whether you have installed version 6 on top of that. If I were you, given that you have a subscription, I would open a ticket in your customer area, also to avoid sensitive data being published here.
BritgirlParticipantYou need to be using at least 6.3. The possibility to know the version of each client connecting was introduced with this Feature Request.
September 27, 2019 at 09:17 in reply to: NoMachine fails with Radeon HD-667X-ZH graphics card #23806BritgirlParticipantHello, can you try sending again? We checked to make sure that everything is working and it is. We’ve also checked our mail server as well for attempted receipts from your IP address and domain. You can also try submitting here if they are small – I wasn’t sure how big they would be, hence I suggested to send them directly.
BritgirlParticipantThe evaluation software provides 30 days, after which you will need to make a fresh reinstall. Alternatively, you can contact the sales team and request an extension.
The free version connects to the physical display only.
BritgirlParticipantThis is planned. Please see:
Forwarding SSH agent authentication to the remote nodes
https://www.nomachine.com/FR09Q03878 -
AuthorPosts