![]() Installing NoMachine Enterprise Clientĭownload the appropriate version of the NoMachine Enterprise Client from NoMachine. This page contains links to several different products. The only one you need to install is "NoMachine Enterprise Client". Versions are available for Windows, Mac and Linux. You may need privileges on your local machine in order to install the software so you may need to ask for help from your local IT helpdesk. Note that "Nomachine Enterprise Client" is a different application to the "Nomachine Enterprise Desktop" available from the more publicised download link on the NoMachine website or other applications in the NoMachine suite: the desktop edition contains additional components to enable remote access to your own (e.g. desktop) machine from a remote location: perhaps convenient but not what we are trying to enable for you here. The NoMachine Enterprise Client is purely a client to connect to a remote server: in our case the server is at the JASMIN end, providing an additional (graphical desktop) interface to JASMIN. Remember to check for updates for the enterprise client to ensure you always have the latest stable version. You can configure the application to check for updates (and optionally apply them automatically) by going to Settings / Updates in the menu. Setting up your connectionĪs you can see from the following videos, the instruction steps below are very similar for Windows / Mac / Linux, once the enterprise client is installed. On Mac and Windows, click the NoMachine Icon.Instructions for v7.x clients: (v6.x clients look slightly different hence slightly different steps, but the same concept overall) Note that the interface may look slightly different depending on which version number of the client you have installed (we can't promise to keep the videos up to date with every new version, unfortunately!) NOMACHINE EXIT FULL SCREEN WINDOWS ![]() On Linux, the default location for the executable once installed is /usr/NX/bin/nxplayer, so you may want to add this to your path. ![]() Your desktop environment may enable you to add an icon to your desktop. XAUTHORITY points to the Xauthority file, which could be %USERPROFILE%\.Xauthority.Type a name for this connection profile, and the full hostname, e.g. In addition to NX_SYSTEM, it is necessary to set the NX_ROOT and XAUTHORITY environment variables before running nxservice. nxservice -start display -nokeyhook -resolution fullscreen To find out about your font path setting, you could try running NXWin through nxservice.exe which will result in informative log output on the console, e. Path arguments to nxwin.exe should be in POSIX format ("/cygdrive/c/."). ![]() instead of "-fullscreen" to get a window. You can supply "-screen 0 1280x1024" etc. A line that works for me is: nxwin -fullscreen -fp -hide -clipboard -noloadxkb -nokeyhook -auth -nowinkill -name NX :1 It can be a bit picky about its invocation. NXWin is included with the client installation. But nxauth should work just fine if you set the NX_SYSTEM environment variable to your NX client's installation directory. If that's not what you want, because you want to use Cygwin's xauth, remove the appropriate part from Auth.cpp. Note: nxcomp includes code that makes it use nxauth instead of xauth when building for Windows. LIBS="$LIBS -L./nxcomp -lXcomp -lstdc -Wl,-e,_mainCRTStartup -ljpeg -lpng12 -lz"Īfterwards put cygXcomp.dll and nxproxy.exe in any directory of your choice, it should run from there. CXXFLAGS="-I/usr/include/libpng12 $CXXFLAGS" Unpack the NX tarballs in one common directory, so that it contains the subdirectories nxcomp/ and nxproxy/ afterwards. You might need the following Cygwin packages: However, you can compile it with Cygwin tools from nxcomp-3.4. and nxproxy-3.4. Nxproxy doesn't seem to be supplied for the Windows client.
0 Comments
Leave a Reply. |