Forum Replies Created
-
AuthorPosts
-
BritgirlKeymaster
If you made this change on the client, you could try a reinstall and create a new connection. Reinstalling will use the default key.
BritgirlKeymasterEither your router doesn’t support UPnP or or NAT-PMP, or they are disabled. Have you tried manually configuring forwarding on the router? See these similar posts:
https://www.nomachine.com/forums/topic/cant-connect-outside-of-local-network#post-2247
https://www.nomachine.com/forums/topic/both-machines-behind-different-firewalls#post-2905
BritgirlKeymasterThe client program is now called nxplayer, so this is what you need to use.
BritgirlKeymasterCan you send us the logs? Follow the instructions in the article here: https://www.nomachine.com/AR10K00697 Enable logs, reproduce the problem and then zip up and send to us. You can either attach them here, or send to issues[at]nomachine[.]com.
May 16, 2014 at 09:32 in reply to: Lightweight mode: setxkbmap -model pc105: Error loading new keyboard description #3632BritgirlKeymasterI am closing this thread. The keyboard problems described should be fixed in 4.2.21. Refer to https://www.nomachine.com/forums/topic/nomachine-key-mappings-issue
BritgirlKeymasterUp arrow key problems were fixed in 4.2.19 (https://www.nomachine.com/AR05L00803) and then in a successive 4.2.21. Users should therefore make sure they have the latest packages.
BritgirlKeymasterHave you enabled ‘Remote resize’ in the menu panel in the session? See here for more details: https://www.nomachine.com/DT10K00060#5.2
May 13, 2014 at 10:53 in reply to: Single application / Floating window cut off at bottom when maximized #3565BritgirlKeymasterA TR has been inserted, you can insert your email address to track its status here:
https://www.nomachine.com/TR05L04420BritgirlKeymasterCheck this first:
Installing NoMachine 4 packages for Linux 32bit on a 64bit system
https://www.nomachine.com/AR02J00623
And if you are still having problems, send the install log to issues[at]nomachine[dot]com (put the title of the topic in your email).
May 12, 2014 at 14:29 in reply to: Supporting the blank screen feature during a remote desktop session #3528BritgirlKeymasterApproved means that it has been inserted into the roadmap as a definite feature (just so you know). It doesn’t necessarily mean that it will be included in the next available release. Recent releases have concentrated on stabilizing the software and improving the overall experience. Now we can dedicate more time to some of the missing features such as locking the screen. We understand that it’s important to many of our users (many have requested it). Rest assured it’s among those at the top of our list 🙂
BritgirlKeymasterCan you download the latest update and let us know if you are still experiencing the same problem? If so, server logs would be useful. Currently, we aren’t aware of any specific issues with Linux Mint.
BritgirlKeymasterCan you send us screenshots in which you highlight what it is you want to change/remove? If you don’t want to attach them here, you can also send them to issues[at]nomachine[dot]com.
BritgirlKeymasterHi, we’ve reproduced this and a Trouble Report has been opened: https://www.nomachine.com/TR05L04413
We also have a patch available if you are interested in testing it. If so, can you contact us via the website for further instructions? 🙂
BritgirlKeymasterThere is currently a bug in profiles which won’t let you correctly disable access to the node:
User can connect to a remote node even if access to that host is disabled by profile rules
http://www.nomachine.com/TR05L04399Once this bug is fixed the correct procedure will be to create user profile rules to forbid connections to specific Enterprise Desktops:
/usr/NX/bin/nxserver –ruleadd –class node –type <node:port> –value no –user <username>where <node:port> is the name of the node as displayed by the nxserver –nodelist
Because of TR05L04399, a solution is to use the redirect capabilities instead of profile rules. You can use the following command to redirect connections from the cloud server to the enterprise desktop based on the users:/usr/NX/bin/nxserver –useredit <username> –redirect <node:port>
where <node:port> is the name of the node as displayed by the ‘nxserver –nodelist ‘ command.
Redirection can be set also on-per client IP basis:
/usr/NX/bin/nxserver –hostadd <clientIP> –redirect <node:port>
Pre-requisite is that the user has a system account on the Cloud server host and on the Enterprise Desktop host. The username has to be the same. First of all add each Enterprise Desktop as a node of the Cloud server by running the following command from a console on the server host:
/usr/NX/bin/nxserver –nodeadd <IP of the Enterprise Desktop>
You can gather information on the node by running:
/usr/NX/bin/nxserver –nodelist
All the Enterprise Desktop you added will be seen by all users connected to the Cloud Server. Users will be able to choose which Windows desktop to join.
BritgirlKeymasterCan you please send server side logs to us?
%PROGRAMDATA%\NoMachine\var\log on Windows Vista, 7 and 8.
Please compress this folder and send to issues[at]nomachine[dot]com.
-
AuthorPosts