Forum Replies Created
-
Posts
-
Create a .nxs file with your settings, protect the .nxs file so that it cannot modified by the user (using chown/chmod or putting it on a read-only file system), create a link on the client’s desktop. That’s it.
As I tried to explain, the microphone is handled in a special way. This is intended to protect the user.
We had a quick meeting and we decided to modify the key as:
<option key=”Audio is muted” value=”default” />
In this way the default behavior is preserved but if you change it in the .nxs to true or false it will retain the requested setting. This change should be available in the update published tomorrow.
The fact the user has to explicitly enable the microphone at session startup is a security feature, to avoid that the microphone can be inadvertently left active and so a user sitting at the remote side can hear what you say (with an appropriate program). Presumably you know whether there can be somebody at the remote side, but NoMachine can’t know.
Di you consider this? Would a dialog showed at session startup improve things? Of course you would be able to select “Don’t show this dialog again” if the dialog annoys you.
http://www.nomachine.com/forums/forums/topic/pointer-position-error-with-multiple-monitors#post-269
…Or letting the user select to which screen NoMachine must connect.
This will stop all the NoMachine programs, included the !M icon. NoMachine will be restarted when you reboot the machine.
We are adding a dialog to let the user decide in just one click if he wants to start the server at the next boot. This change will be included in the next release, scheduled for tomorrow.
Note that the server configuration is being completely redesigned, to make it more comprehensible and easier to use. The fact users can’t disable the server in one click and have to disable the different “services” one by one (assuming users know what each “service” is) is a useful feature in a “enterprise” setting but clearly an annoyance for the rest of us.
Hi Aaron,
there are a number of issues with the QT version we use in the player. The version is quite old and the reason we haven’t upgraded is that this version is well tested and carefully trimmed down to reduce the size, since we only use it for the GUI. Unfortunately this version has incomplete support for the retina displays, besides showing a number of problems when trying to resize the GUI on the fly (this explains why, differently from the web-player in the Portal server, the desktop player doesn’t adjust to fit the window size). The Android and iOS players use the latest QT and, given the code base is the same, we expect to complete the transition as soon as these players are released. This should help to solve all these problems.
About the resolution of the NX session itself, you must consider that while are the lower layers to handle encoding/decoding, the final stage of showing the pixels on screen (on Mac) is still handled by the QT library, so even if the remote screen has an higher resolution, the window on screen will be displayed at 1440×900.
Hi Jules,
yes, see this post:
https://forums.nomachine.com/topic/nomachine-gateway-for-windows-8
Reading the gateway IP from the inside the network is not supported by some routers, despite UPnP being working fine. Additionally some routers take forever to respond, so the reply may come after the client has gone past that dialog. Unfortunately it seems that there is a “communication” problem, here. We’ll check how we can improve the dialog so that it doesn’t give the misleading impression that the connection isn’t going to work.
Security risk? Remote access now involves unlocking my desktop
NoMachine now works as traditional remote access software, which is what Mac, Windows and Linux users expect, as long as these users are looking for a remote access software. NoMachine should provide the option of blanking the screen and locking the keyboard and mouse while an unattended computer is engaged in a connection. We are working on this. It turned out to be a bit trickier than one would have expected. If the computer is on a table where there are others that walk and see what is displayed, you should probably look for a terminal server that the free NoMachine 4 is not.
I can no longer choose which desktop I login into remotely I just use the one the user is connected to.
The Workstation and all the Terminal Server versions work as terminal servers, by creating sessions running in the background. These are terminal servers, intended for the enterprise market. The free 3 worked as a terminal server limited to 2 users. This functionality is no longer available in the free version.
Is there a way to login to a different desktop/user and im a way where my physical pc is not needed to be unlocked (like NX 3.x) ?
Yes, install the Workstation edition or run a virtual X server as explained here:
http://www.nomachine.com/AR10K00710
We have added a new configuration key to the server in the next update, so that users can specify to which display NoMachine must connect. You can run a virtual X server on :1 and tell NoMachine to connect to it, rather than the physical display on :0. This :1 will run in the background, so others can’t see what is displayed. This is the way VNC also works, so, free for free, you get a widely better software for the same price.
Definitely yes. Much better support for DirectX and games is coming soon. We are testing with different DirectX and OS versions (9/10/11, XP, Vista, 7 and 8). I think we are one or two months from completion.
I know this program wasn’t exactly made for games/gaming in general
Let me say that NoMachine is not specifically about gaming (a gaming-only solution would have been much simpler and would have required much less time and effort), but we want people to do whatever they do with their computers on remote computers. Gaming is one of the most important thing people do with computers, so it is absolutely paramount. Gaming and watching media. I’m not much a gamer, but I have an old iMac with a TV tuner at home working as TV set. I use NoMachine to watch the TV in other rooms. As a user and a developer, I’ve spent months to ensure I could watch the TV as smoothly as I could do front of the real thing. It’s not perfect and there are tons of improvements we want to do, but to be a sort of 1.0 it’s not bad. This is the kind of use we want people to do with NoMachine.
Bug. The developers responsible for this will check it. Please tell me more about:
– NoMachine product and version on local and remote machine (free version, Workstation, etc).
– Whether the problem arises connecting to a physical or a virtual display.
– Remote and local Linux version (Ubuntu xyz, Mint x.y, etc.).
– Desktop version (GNOME. KDE, whatever).There is a plan ongoing to add better multi monitor support. For example by opening a different player window for each monitor, or, as you suggest, by letting users switch from one monitor to the other in a single window, by using a keystroke, similarly to Spaces in OS X.
Maybe I misinterpreted your question. What is the part of the menu bar that NoMachine wants to occupy? Is it the !M icon in the notification area? This is a security measure used by the server, indeed to notify you about connections and also to let you check at any time who’s watching your screen while you are working. It is also used to access screen recording, something you probably want at hand when you need it.
If you only use the client you can disable the server part using the admin GUI.
To check if it is disappearing try:
sudo /Applications/NoMachine.app/Contents/Frameworks/bin/nxserver –shutdown
If this is what you are talking about, we didn’t consider, honestly, that the icon in the notification area could be so obtrusive. Good to know. Probably there should be an option to hide it. Of course at the cost of some functionality loss, but after all the user is king.
Please see this reply:
http://www.nomachine.com/forums/forums/topic/nomachine-gateway-for-windows-8#post-237
You should probably review the configuration of your router. It can be that it doesn’t support UPnP, or UPnP is disabled. We’ll improve the error reporting.
Please more info :-).
– NoMachine product and version on local and remote.
– Remote Linux version (Ubuntu xyz, Mint x.y, etc.).
– Desktop version (GNOME. KDE, whatever).Connect, then go to your valuable real-estate in your menu bar at top-right and click. In the menu panel select Input and clear “Use page-peel for menu access”. To get to the menu panel press CTRL+ALT+0.
To uninstall do what any casual user would do. On my machine I move the program to the trashcan, but I heard some people have to go to “Control panel” -> “Installed programs” and press “Uninstall”.
The repeat is nearly immediate – so way faster than the autorepeat. but it’s not instant
The autorepeat we are interested in is the autorepeat timeout causing the first repetition. The further repetitions of the same key continue because the “key release” event is not received by the remote, presumably because of a network problem. So what really counts is that the round-trip time is less than the (first) autorepeat timeout.
This problem can be caused by a particular delay between packets being introduced by the network. A SSH terminal is not affected by this, since the characters sent by the terminal application are produced on the client side and only echoed by the server. Same for a voice or a video call, where the buffer underflows or the network jitter can be easily compensated. For voice and video 1 second delay (caused by buffering) is the norm. You just don’t notice that because audio and video are synchronized. When you are talking with somebody there are not many “round-trips”, but YouTube is full of videos showing the funny effect when people try to “synchronize”. Unfortunately in a system like NoMachine you can’t produce characters on the client, since how each key press is translated depends on whatever keymap or program is running on the server. NoMachine has some tricky algorithms to “compensate” the key presses, but evidently they don’t work in your case. Probably this depends on big spikes in latency, happening from time to time.
If you want, we can provide a test version with some logs enabled. This should shed more light on the issue and surely help to improve the code.