reza

Forum Replies Created

Viewing 15 posts - 106 through 120 (of 138 total)
  • Author
    Posts
  • in reply to: Both machines behind different firewalls #2905
    Avatarreza
    Moderator

    In future it will be handled by NoMachine Anywhere.
    Right now routers supporting UPnP or NAT-PMP are configured automatically to pass connections to NoMachine and all required informations are displayed at initial screen (Welcome to NoMachine).
    Routers not supporting UPnP or NAT-PMP and Firewalls have to be configured manually to pass traffic to port 4000 (NX protocol), 22 (SSH protocol on Linux/MacOSX) or (4022) (SSH protocol on Windows)

    • This reply was modified 6 years, 8 months ago by Avatarreza.
    in reply to: Nexus 5 input #2811
    Avatarreza
    Moderator

    There is a known issue with Swiftkey Keyboard.

    Please try with default Android keyboard.

     

    in reply to: Unable to connect on Ubuntu #2777
    Avatarreza
    Moderator

    It seems that you cannot connect to your servers because of Firewall or NAT. If you are using NX protocol please ensure that the Security Group for your EC2 instance allows connections on port 4000.

    • This reply was modified 6 years, 8 months ago by Avatarreza.
    in reply to: NX using SSH tunnel? #2775
    Avatarreza
    Moderator

    You can configure your router to forward some TCP ports to your internal machines.
    Each unique external TCP port should map to port 4000 of the separate internal machine.
    In a similar way you can handle UDP ports to improve multimedia performance.

    • This reply was modified 6 years, 8 months ago by Avatarreza.
    in reply to: NX using SSH tunnel? #2761
    Avatarreza
    Moderator

    Yes, it’s possible to tunnel NX protocol over a SSH, as explained in https://www.nomachine.com/AR10K00728.

    However there are no benefits to do that, compared to use SSH directly.

    in reply to: Connection SSH Timeout #2726
    Avatarreza
    Moderator

    In NoMachine version 4 it’s possible to specify a proxy server in connection settings GUI.
    Please edit your connection settings and go to ‘Advanced’ panel, mark ‘Use a HTTP proxy for the network connection’ and click on ‘Settings’ to adjust host, port, username and password. HTTP proxy can be used in both – NX and SSH protocols.

    • This reply was modified 6 years, 8 months ago by Avatarreza.
    in reply to: Can only connect using local administrator #2720
    Avatarreza
    Moderator

    From what you have written it seems to be a problem we have fixed, but not yet released (scheduled for the next version).
    So that we can make sure, are you able to send us the complete server logs (compressed)?
    Follow the instructions here and submit to the forum, or issues[at]nomachine[dot]com:
    https://www.nomachine.com/AR07K00677

    • This reply was modified 6 years, 8 months ago by Avatarreza.
    in reply to: Mint 14: Can’t Start nxplayer #2622
    Avatarreza
    Moderator

    Can be that you installed the 32 bit package on a 64 bit Linux?

    If yes, please use the NoMachine 64 bit package or add support for 32bit to your Linux installation:

    $ sudo dpkg –add-architecture i386

    $ sudo apt-get update

    $ sudo apt-get upgrade

    $ sudo apt-get install ia32-libs

    in reply to: Replacing NoMachine keys with another certificate #2585
    Avatarreza
    Moderator

    It’s not possible in the current 4.1 but we have it planned.

    Please consult the Feature Request here: http://www.nomachine.com/FR02L02810

    • This reply was modified 6 years, 9 months ago by Avatarreza.
    in reply to: Black Box #2390
    Avatarreza
    Moderator

    Check out the following article and follow the instructions in Point 1.

    https://www.nomachine.com/AR02L00776

    in reply to: Desktop lost #2271
    Avatarreza
    Moderator
    in reply to: Desktop lost #2218
    Avatarreza
    Moderator

    With the previous version I used KDE-desktop. Now when i start a nomachine session, it waits a long time and gives me a gnome-session, with a screensaver of long time ago. There are no icons and no menu-bars. The Desktop locks.

    Set the DefaultDesktopCommand key to the same value set already set in CommandStartKDE in the node.cfg. Alternatively,  set the ConnectPolicy key to desktop=1. More about the default desktop in version 4 is here: https://www.nomachine.com/AR10K00725

    The main Desktop, Alt-F7 on the console, tries to start but without success. It repositions/restores to a normal char-mode login.

    The log files will be useful. Send us the $HOME/.xsession-errors and  /var/log/Xorg.0.log files.  Attach them here. Alternatively, send them to issues[at]nomachine.com

    in reply to: Nautilus – general protection fault #2138
    Avatarreza
    Moderator

    Not related to NoMachine. It is the same issue for which Red Hat recently released a patch. The package version, which you are using, contains a bug that caused applications using librsvg2 to crash when loading certain SVG images.

    dmesg indicates:nautilus[34443] general protection ip:30c022633c sp:7fff602653e0 error:0 in librsvg-2.so.2.26.0[30c0200000+37000]

    nautilus[34450] general protection ip:30c022633c sp:7fff1a19ab10 error:0 in librsvg-2.so.2.26.0[30c0200000+37000]

    We advise you to patch your system with the latest fix from Red Hat. The advisory they issued was: Updated librsvg2 packages that fix one security issue are now available for Red Hat Enterprise Linux 6.

    If you have a Red Hat subscription, you can get more details here:

    https://rhn.redhat.com/rhn/errata/details/Details.do?eid=25640

    • This reply was modified 6 years, 9 months ago by Avatarreza.
    in reply to: Can’t connect outside of local network #2121
    Avatarreza
    Moderator

    We didn’t publish all the information on your routing table, but from it we can see that you have a double NAT. So NoMachine has to go through two. That is, a router facing the internet for which you have a private LAN with IP address of 192.xxx.xx.x) and then another router  for access to the private network/LAN for which you have an IP address of 192.xxx.x.x).

    UPnP doesn’t easily support this type of scenario. In this particular case, our upcoming product NoMachine Anywhere would resolve this problem for you and the hassle of having to configure routers by hand or setting up awkward tunnels.

    Until then, and if you have access to both your routers, port forwarding should be set up on the second one as you already did for the other that you mentioned.

    • This reply was modified 6 years, 10 months ago by Avatarreza.
    in reply to: RC4 broken – implications for NoMachine? #2015
    Avatarreza
    Moderator

    The 4.1 will ship with AES. About your concerns, I don’t think you should worry too much. As the article correctly mentions “the current attack is just on the edge of feasibility”. Amazon and Ebay, as of today, are still using it. You must also consider that the attack is based on millions of connection iterations from the same host. A similar scenario is theoretically possible in the case of a browser connecting to a Web server, but unlikely to happen in the case of a client connecting to a NoMachine host.

    https://www.nomachine.com/FR11K02792

     

Viewing 15 posts - 106 through 120 (of 138 total)