역시 Linux에서는 nxfree가 짱~ ㅎㅎ (www.nomachine.com)


lsysdir:/home/scripts/nxfree#]ls
nxclient-3.5.0-7.x86_64.rpm  nxnode-3.5.0-7.x86_64.rpm  nxserver-3.5.0-9.x86_64.rpm
  
>>> 반드시 client -> node -> nxserver 순으로 설치해야 함 !!!
lsysdir:/home/scripts/nxfree#]
rpm -ivh nxclient-3.5.0-7.x86_64.rpm
Preparing...                ########################################### [100%]
   1:nxclient               ########################################### [100%]
Showing file: /usr/NX/share/documents/client/cups-info

 CUPS Printing Backend

 The NX Client set-up procedure detected that your "IPP CUPS" printing
 backend doesn't allow printing from the NX session. In order to have
 printing support in your NX system, you need to set proper permissions
 on the IPP backend. Please execute:

   chmod 755 /usr/lib/cups/backend/ipp
lsysdir:/home/scripts/nxfree#]
rpm -ivh nxnode-3.5.0-7.x86_64.rpm
Preparing...                ########################################### [100%]
   1:nxnode                 ########################################### [100%]
NX> 700 Starting: install node operation at: Wed Apr 18 06:14:14 2012.
NX> 700 Autodetected system 'redhat'.
NX> 700 Install log is '/usr/NX/var/log/install'.
NX> 700 Creating configuration in /usr/NX/etc/node.cfg.
NX> 700 Inspecting local CUPS environment.
NX> 700 Generating CUPS entries in: /usr/NX/etc/node.cfg.
NX> 700 Installation of version: 3.5.0-7 completed.
NX> 700 Bye.

lsysdir:/home/scripts/nxfree#]rpm -ivh nxserver-3.5.0-9.x86_64.rpm
Preparing...                ########################################### [100%]
   1:nxserver               ########################################### [100%]
NX> 700 Installing: server at: Wed Apr 18 06:14:23 2012.
NX> 700 Autodetected system: redhat.
NX> 700 Install log is: /usr/NX/var/log/install.
NX> 700 Creating configuration file: /usr/NX/etc/server.cfg.
NX> 723 Cannot start NX statistics:
NX> 709 NX statistics are disabled for this server.
NX> 700 Version '3.5.0-9' installation completed.
NX> 700 Showing file: /usr/NX/share/documents/server/install-notices

Server keys

The initial login between client and server happens through a DSA key
pair, i.e. a couple of specially generated cryptographic keys, called
the private key and the public key, which allow you to establish a
secure connection, by means of SSL encryption, between NX client and
NX server.

The public part of the key-pair is provided during the installation
of the server, while the private part of the key-pair is distributed
together with the NX Client. This ensures that each NX client is able
to authenticate to the server and to start the procedure for autho-
rizing the user and negotiating the session.

If you want to create a virtual private network (VPN) instead, you
need to generate a new DSA key-pair and distribute the private part
of the key-pair to those NX clients you want authenticated to the NX
server. More information on how to generate and distribute a new DSA
key-pair is available at:

http://www.nomachine.com/ar/view.php?ar_id=AR01C00126

Creating Users

NX is configured to allow access from any system user, as long as
valid credentials are given to the user for the SSH login. NX pro-
vides an alternative authorization method, allowing system admin-
istrators to determine which users are given access to the NX fun-
ctionalities. This works by implementing a separation between the
system password and the NX password, so that, for example, it is
possible to forbid remote access to the system by any other means
except via NX and use the NX tools to implement effective accounting
of the system resources used by the user, or to share NX passwords in
an external database.

To activate the NX user and password DBs, you will have to edit the
NX server configuration file by hand or use the NX Server Manager
Web tool available for download on the NoMachine Web site at:

http://www.nomachine.com/download-manager.php

Session Shadowing and Desktop Sharing

The session shadowing functionality allows you to share NX sessions
running on the node. The desktop sharing functionality instead, gives
access to the native display of the X server as if you were in front
of the monitor. By default you can access sessions in interactive mode
and upon authorization of the session owner. You can modify this beha-
viour by tuning the server configuration according to your needs, for
example by allowing access to sessions in view-only mode, or connecting
to either a suspended session or the local display via the Desktop
Manager login window.

Load Balancing

NX Advanced Server provides support for multi-node capabilities and
load balancing. In its current implementation, NX server can only
manage accounts on the host machine, so to grant access to the node
running remotely, you will need to create the user account directly
on the remote node host by issuing the NX node commands as root user.
You will also need to add the NX Server public DSA Key to the node to
allow this server to connect to the node running on the remote host.

Documentation

For further information on how to manage the configuration of your
NX system, please refer to the System Administrator's Guide available
on the NoMachine Web site at:

http://www.nomachine.com/documentation/admin-guide.php

The NoMachine Team.


NX> 700 Bye.

lsysdir:/home/scripts/nxfree#]cd /usr/NX/scripts/setup
lsysdir:/usr/NX/scripts/setup#]
./nxserver --install
NX> 701 Updating: server at: Wed Apr 18 07:28:09 2012.
NX> 701 Autodetected system: redhat.
NX> 701 Update log is: /usr/NX/var/log/update.
NX> 701 Checking NX server configuration using /usr/NX/etc/server.cfg file.
NX> 701 Running: chkconfig to remove init script.
NX> 701 Verifying that all init scripts have been removed.
NX> 723 Cannot start NX statistics:
NX> 709 NX statistics are disabled for this server.
NX> 701 Version '3.5.0-9' update completed.
NX> 701 Bye.

lsysdir:/usr/NX/scripts/setup#]cd ../../bin/
lsysdir:/usr/NX/bin#]
./nxserver --keygen
NX> 704 Starting: server-keygen operation at: Wed Apr 18 07:28:35 2012.
NX> 704 Generating new ssh-keys. Please wait.
NX> 704 Keys generated correctly. Backing up files.
NX> 704 Back up of keys made. Updating files.
NX> 704 Keys updated. NX clients should now use key:
NX> 704 /usr/NX/share/keys/default.id_dsa.key
NX> 704 to get connected to this NX server.
lsysdir:/usr/NX/bin#]
cat /usr/NX/share/keys/default.id_dsa.key
-----BEGIN DSA PRIVATE KEY-----
MIIBugIBAAKBgQDDIaDmPIoH2z8uruP0eqfTbydJXMs7sRBb/0PMirES7JC8tkjt
kBBzPkptdQcafF8JR9GMvY1fxDRxX7Ofr9Z3WV82dvxfyv9GqJR7Q+92nhShIRJe
                               ................
gwxQtALE5/qzfUjmx1iRUhu/OlmRMQdfwz8wXlmvoWtDZ3MyKrRQR6HII7daxsy7
bHysGXXHbgO+KJ3D6B8ktQHiv5XCCLtIO/MBDKHW06/es6Ebgm8oEgIUGne8mNxU
N2bpKUVM3axzCbMdDso=
-----END DSA PRIVATE KEY-----
lsysdir:/usr/NX/bin#]
lsysdir:/usr/NX/bin#]adduser nxfree
lsysdir:/usr/NX/bin#]
passwd ****
Changing password for user nxfree.
New UNIX password:
Retype new UNIX password:
passwd: all authentication tokens updated successfully.
lsysdir:/usr/NX/bin#]
su - nxfree
[nxfree@lsysdir ~]$
exit
logout
lsysdir:/usr/NX/bin#]
./nxserver --useradd nxfree
NX> 900 Setting password for user: nxfree.
NX> 102 Password:
NX> 102 Confirm password:
NX> 110 Password for user: nxfree added to the NX password DB.
NX> 900 Adding public key for user: nxfree to the authorized keys file.
NX> 900 Verifying public key authentication for NX user: nxfree.
NX> 900 Public key authentication succeeded.
NX> 301 User: nxfree enabled in the NX user DB.
NX> 999 Bye.
lsysdir:/usr/NX/bin#]
/etc/rc.d/init.d/nxserver restart
Trying to restart NX server:
NX> 123 Service stopped.
NX> 153 Stopping NX server monitor.
NX> 153 NX server monitor already stopped.
NX> 122 Service started.
NX> 999 Bye.
Trying to restart NX statistics:
NX> 723 Cannot start NX statistics:
NX> 709 NX statistics are disabled for this server.
NX> 999 Bye.
lsysdir:/usr/NX/bin#]
service nxserver restart
Trying to restart NX server:
NX> 123 Service stopped.
NX> 153 Stopping NX server monitor.
NX> 153 NX server monitor already stopped.
NX> 122 Service started.
NX> 999 Bye.
Trying to restart NX statistics:
NX> 723 Cannot start NX statistics:
NX> 709 NX statistics are disabled for this server.
NX> 999 Bye.
lsysdir:/usr/NX/bin#]

-------------------------------
2. freenx 세팅
freenx는 기본적으로 22번 포트(SSH 포트)를 사용한다.
# vi /usr/NX/etc/server.cfg 로 설정을 수정한다.
#SSHDPort = "22" 를  주석을 푼뒤 저장한다.

그다음 #vi /etc/sysconfig/iptables 로 22번 포트를 열어준다.
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT 
방화벽재기동
# /etc/rc.d/init.d/iptables restart
# netstat -ntlp 로 22번 포트가 열려있나 확인한다.

안열려 있을 경우 ssh와 nxserver을 restart 시킨다
정상적으로 확인이 될경우
ntsysv로 시작프로그램으로 등록해 매번 실행시키는 수고로움을 덜자
-------------------------------



---------------------------------------------------------------------
   Ubuntu 12.04에서 3D 문제로 nxfree가 않뜰 경우...
NoMachine NX Desktop on Ubuntu 12.04 Precise Pangolin ? No menus?
Posted on May 28, 2012 by drye
---------------------------------------------------------------------
NoMachine NX is a perfect solution to connect to your remote Ubuntu desktop.
But ever since Canonical introduced Unity, NoMachine doesn’t seem so perfect anymore:
client successfully connects to the NX server, but the menus never show up, and there’s no Unity side bar.

Here’s what works in 12.04 Precise Pangolin:

On the remote machine open up this file: /usr/NX/etc/node.cfg and edit it as a superuser:

sudo vim /usr/NX/etc/node.cfg
Towards the end of the file, look for CommandStartGnome and change it to

CommandStartGnome = "/usr/bin/gnome-session --session=ubuntu-2d"
Save the file, and Unity should now work in 2D mode the next time you connect and the menus
and the sidebar will show up.

This entry was posted in Howtos, Technology. Bookmark the permalink.


블로그 이미지

Melting

,