kroy

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 544 total)
  • Author
    Posts
  • in reply to: Console (not desktop GUI) displayed #35893
    kroy
    Contributor

    We are investigating the problem. Meanwhile you can edit org.gnome.Shell.desktop entry

    sudo vim /usr/share/applications/org.gnome.Shell.desktop

    and change line:
    Exec=env LD_PRELOAD=/usr/NX/lib/libnxegl.so /usr/bin/gnome-shell
    to this:
    Exec=/usr/bin/gnome-shell

    and tell us if it helps.

    in reply to: Connects but shows wrong remote host name #35748
    kroy
    Contributor

    Thanks for letting us know.
    It’s not necessary to remove NoMachine. Network broadcasting informations are cached in ~/.nx/cache folder – to clear remove correct .nxs file or remove all files from that directory.

    in reply to: Connects but shows wrong remote host name #35731
    kroy
    Contributor

    Can you check what the uname -n command shows on that “Host-B” machine? On NoMachine player you should see exactly the same hostname.

    in reply to: Not finding physical session or opening virtual session #35606
    kroy
    Contributor

    DefaultDesktopCommand "/usr/bin/cinnamon-session --session cinnamon" should fix the problem with virtual desktop.

    Regarding to physical desktop – we cannot reproduce such problem on Mint 19.3 with LightDM. Is it clean installation of the NoMachine? If it’s update, upgrade or some re-installation – execute following commands:

    sudo /etc/NX/nxserver --addtoredis
    sudo /etc/NX/nxserver --restart

    and recheck. If that won’t help we suggest to remove NoMachine with all config files:

    sudo dpkg --purge nomachine
    sudo rm -rf /usr/NX /etc/NX /var/NX

    and install again newest package.

    in reply to: Server not displaying external IP address #35327
    kroy
    Contributor

    Possibly that could be some Router software problem. You can try router reset or upgrade firmware. You can also try to manually set up port forwarding. This is an example of how you can open ports on your router model: https://portforward.com/linksys/wrt54gl/

    In your case you can try:

    Application: NX
    Start: 4000 (this is the default NX port)
    End: 4000
    Protocol: Both
    IP Address: 192.168.1.102 (there should be local IP to your machine with nxserver – according to output which you paste it’s IP with 102 ending)
    Enable: yes (just check the box)

    Save settings. Then you should be able to connect there using External IP and choosen 4000 port

    in reply to: Enabling a user does not enable it #35286
    kroy
    Contributor

    In your script possibly instead of:

    service nxserver start

    Use this:

    service nxserver start > /dev/null 2>&1 &

    or

    /etc/NX/nxserver --startup

    kroy
    Contributor

    Hi.

    UserHome applies only to newly created users. For existing users, /usr/NX/etc/node.cfg key with correct path must be set:

    UserNXDirectoryPath “”

    in reply to: NoMachine & Samba login trouble #34472
    kroy
    Contributor

    Are you using home sharing with samba? If yes, can you verify isn’t it similar problem https://www.raspberrypi.org/forums/viewtopic.php?t=158919? It doesn’t sound it could be related to NoMachine. Please verify if it’s possible to connect to that machine over terminal – via ssh and if home directory of the affected user have correct ownership or if it’s shared at all.

    in reply to: Clipboard between Mac and Ubuntu rarely works #34076
    kroy
    Contributor
    in reply to: Clipboard between Mac and Ubuntu rarely works #34059
    kroy
    Contributor

    Hi.

    Please refer to the article: https://knowledgebase.nomachine.com/AR10Q01058. If you want to start nxplayer with option –activegrab by default quit nxplayer, edit file $HOME/.nx/config/player.cfg and enable active grab key:

      <option key="Enable active keyboard grabbing" value="true" />

    in reply to: How to clear cache data #33782
    kroy
    Contributor

    Clear NoMachine installation shouldn’t occupy more than 200 MB (the size depends on the type of package installed). You can check the size of the installation path (in the default is /usr/NX), including the nxserver log path (in the default it should be in /usr/NX/var/log, more about logs you can find there: https://knowledgebase.nomachine.com/DT11R00181).

    Check also specified paths for program files and connection settings, transferred files and recordings, which you can find here: https://knowledgebase.nomachine.com/DT11R00177#2.4.

    in reply to: Uninstall issue #33726
    kroy
    Contributor

    Hi

    We didn’t notice such kind of issue. Please reboot the system and install the program properly. After that, you should be able to uninstall NoMachine. (https://knowledgebase.nomachine.com/DT10R00166#2.2).

    in reply to: NodeLoginGreeting not working #33188
    kroy
    Contributor

    Hi,

    You can try the new line sequence “\n”, for example:

    NodeLoginGreeting “Hello\nWelcome to your NoMachine session\nHow are you today?”

    Also, it would be preferable for this message to be displayed *before* someone logs into a NoMachine session. Is that possible?

    Check node.cfg key: UserScriptBeforeSessionReconnect. More info about user scripts you can find there: https://knowledgebase.nomachine.com/AR02L00787

    in reply to: Systemctl nxserver.service #32870
    kroy
    Contributor

    Hi,

    We tried the same OS and had no problems neither with the detection of the desktop nor with the start of the nxserver service with systemctl. Maybe as you said installation was broken during the update and your disk was out of space? Please try to uninstall the program (sudo /usr/NX/scripts/setup/nxserver --uninstall && sudo rm -rf /usr/NX /etc/NX) and install again the newest version.

    in reply to: No connection via public IP possible #32630
    kroy
    Contributor

    Is the local connection still working? If it’s not a problem with the credentials maybe try to unselect “Use UDP communication for multimedia data” (it’s in the player – in connection file) in case UDP ports are blocked in the router.
    Logs from both the client and server side would be helpful to investigate the problem. You can send them to forum[at]nomachine[dot]com, making sure you add the title of the topic as the email subject. Instructions about debugging and collecting logs can be found here: https://www.nomachine.com/DT11R00181.

Viewing 15 posts - 1 through 15 (of 544 total)