Forum Replies Created
-
Posts
-
I’m quite sure the 4 did not do anything with your KDE setup. In fact I’m not aware of any special interaction between NoMachine and the particular desktop environment. On Linux, NoMachine interacts with the desktop at the X protocol level. Hardly this can screw ~/.kde/share/config/plasma* or any other file, unless KDE screws it by itself.
Double click on the connection (that you maybe created with a 3 client and that was then imported to the 4 by using the same protocol settings). When the client is showing the connection details click on Edit and change the Protocol to NX.
There is clearly a communication problem on our side, albeit these situations are generally difficult to handle “automatically”. Future versions will offer the choice of switching to the NX protocol if SSH connections fail with this error.
It can be that your router doesn’t support UPnP. Or that our UPnP doesn’t support your router :-). Anyway this shouldn’t affect your ability to connect, even from the outside. Many routers that don’t support the query for the external IP still accept the commands required to enable port forwarding. If not, you will have to configure the port forwarding by using the router admin interface. This is normally a Web application running at http://192.168.1.1.
This “gateway” GUI is a retrofit, intended to alleviate the annoyance of having to find and enter the IP by hand. We struggled to get NoMachine Anywhere ready for the release but it was not possible. We are going to roll out the mDNS integration, for now (also known as Bonjour in the Apple world), so that any machine will be automatically able to find the other machines on the LAN. And of course this will work on any OS. Not yet the “final” solution, but a small step in the right direction.
Definitely not. We tried the 10.9 distributed to developers and it worked fine (except for a USB issue that pushed back the release by one week). It was a clean install, though. We are trying to see if we can get the same problem on a upgraded machine. Fortunately it should not be difficult to reproduce, since this is the second post reporting this.
You must change the keyboard on the server. Check in the system settings, control panel or whatever it is called in your favorite desktop environment.
I understand it’s not as easy as before, but why don’t you just tunnel the NX connection?
ssh -L 4555:localhost:4000 youruser@yourhost
Now connect to nx://localhost:4555
Remember to disable UDP in the connection settings or you will have to wait for the UDP negotiation timeout.
I’m afraid the reason is that you are trying to connect by ssh to a free NoMachine install. The free version doesn’t support SSH. Be sure you select the NX protocol in the client settings.
There are good reasons why SSH is not in the free version. People expect software to install and work out of the box, while SSH requires that you install and configure SSH beforehand. This is not what the average user expects (in this respect previous NoMachine versions were the exception, rather than the rule). Second SSH can be tricky to configure. If you search the Internet you easily realize that 90% of problems people had with versions before the 4 were with configuring SSH, rather than the software itself. Probably NoMachine thinks support is better employed at handling the paying customers, rather than the users of the free version. Third the NX protocol can use both TCP and UDP for multimedia traffic and this can make a huge performance difference. Clearly NoMachine wants people to get the best from the software. If you are in a setting where you can’t open the port on the router, or are smart enough to know how to configure SSH, you can still tunnel the NX connection over SSH, as you would do for any other protocol.
How long it takes between the first letter (the legitimate one) and the first spurious character? Is it compatible with the autorepeat time set on the Linux server (say 1/10th of a second), or it is much shorter (almost immediate)? Can you please try to increase the autorepeat time on the server desktop and see if it makes any difference?