13-05-2021

Hello, I've recently purchased a Mac Mini and I'm trying to get NxClient working to connect to my Linux server. The client works fine when connecting from a Windows host, but no such luck on the Mac. Here's what I've done:
-Uninstalled nxclient
-Removed ~/.nx
-Rebooted
-Downloaded and installed nxclient-3.4.0-8.pkg.zip directly from NoMachine
-Launched the client, configured my host, and tried to connect
It seems to connect successfully, X11 gets launched, but nothing appears and it eventually times out.
/Users/jwhite08/.nx/temp/182/sshlog shows:
NX> 203 NXSSH running with pid: 195^M
NX> 285 Enabling check on switch command^M
NX> 285 Enabling skip of SSH config files^M
NX> 285 Setting the preferred NX options^M
NX> 200 Connected to address: 172.23.100.100 on port: 22^M
NX> 202 Authenticating user: nx^M
NX> 208 Using auth method: publickey
and /var/log/windowserver.log shows:
Apr 29 13:32:30 56 kCGErrorIllegalArgument: CGXOrderWindow: Operation on a window 0x6 not owned by caller nxclient
Apr 29 13:33:35 56 kCGErrorIllegalArgument: CGXSetWindowListTags: Operation on a window 0x6 not owned by caller X11
I've searched the forums, but it would seem as though no one else has encountered a similar issue. Any help would be appreciated.
-Jesse

Mac Mini, Mac OS X (10.6.3)

Key features and fixes from the previously released NX 3.3.0, such as support for Mac OS X Snow Leopard, are also integrated into the new NX 3.4.0 release. With NoMachine's remote desktop solutions being widely adopted and deployed across a variety of industries, there has been an increasing demand for multi-monitor support. NoMachine NXclient NXLogin::reset. I've used NoMachine's NX software for some time, but on one of my machines it simply will not work. I'd recommend use the NX client and freeNX Server. Our developers are working to implement this for a successive maintenance release of NX 3.4.0. We advise you to sign up to one of our mailing.

Posted on

Active4 years, 11 months ago

It broke after Mac Os software update, I think.

This problem is not uncommon, but I have not seen a solution that would work for me.

Nx Client For Windows 10

Keyboard mapping is completely screwed up - e.g. typing 'damn it' gives me'1cxngw'. All machines have QWERTY keyboards and are set up to use US.

Thanks!

Fantomas
FantomasFantomas
1841 gold badge9 silver badges27 bronze badges
Nx Client 3.4.0 For Mac

1 Answer

Nomachine Nx Client For Windows

A solution that works with on Mac (10.6) login with an NoMashine-Client to an FreeNX-Server running on an Ubuntu (10.04).

  1. Read out your keyboard mapping from your OSX System

    Open X11 terminal and execute:

  2. Edit nxclient_mac.xmodmap to enable also also remapping of shift-,alt- and command-keys

    Add at the beginning of file:

    Add at the end of file:

  3. Copy the new file nxclient_mac.xmodmap to your home directory of your used user on server system

  4. Load the key mapping file on server system only when login with this user when using NX-Login

    Add this lines to your '.profile' file:

  5. Terminate former NX-session and login again with NX-client... now hopefully it works

mac usermac user

Nx Client 3.4.0 For Mac

Not the answer you're looking for? Browse other questions tagged macosfreenx or ask your own question.