Forum Replies Created
-
AuthorPosts
-
kroyContributor
It looks like there was a NoMachine directory on that Windows before you installed NoMachine package again. Please try uninstalling the program and if the directory ‘NoMachine’ still exists, remove it (it’s in %ProgramFiles% folder) and install again.
About problems with the connection. Are you sure that you entered Public IP (not local IP) of lab machine in connection settings in nxplayer? In the following article there are instructions how to connect to NoMachine when the server is behind a NAT router or a firewall https://www.nomachine.com/AR11L00827. That should help.
kroyContributorAre you sure that you have reserved local IP for your machine? Maybe you have dynamic IP and it has changed?
Can you attach here a screenshot of the ‘Welcome screen’ that is shown when you open the player on the machine you want to connect to (server side)? To avoid showing sensitive information, blot out the numbers and leave showing the first two e.g. nx://80.170.X.X:26XX.
Then check what is your public IP (you can check it by entering passphrase “my ip” in webbrowser). Is it the same?
kroyContributorFrom what you pasted it looks like a licence issue. Can you describe the exact steps to produce problem? Did you change license file? How did you uninstall NoMachine?
Please try to remove again NoMachine on Ubuntu by using command:
sudo dpkg -r nomachine
and remove all NX folders:
sudo rm -rf /usr/NX /etc/NXand install once again.
You said also that you couldn’t connect from home to server on your lab. Please make sure that you’re using the correct IP address and port.
kroyContributorEnabling UPnP makes it easier. If you don’t want to use that, you will have to configure the port forwarding by using the router admin interface. This is normally a Web application running at http://192.168.1.1. Follow these instructions for your parents’ router:
1. Reserve local IP of your parents’ computer on their router according to your router’s instructions.
2. Open a unique port for that local IP in Port Forwarding section on the router.
3. Check public IP of the router.
4. Now in your Player connection settings – enter the public IP of your parents router and unique port. Now you should connect to your parents machine.kroyContributorFrom the Kaspersky website: when establishing a connection using remote control applications, you will not be able to access the graphic user interface (GUI) of Kaspersky Endpoint Security. The GUI does not react to mouse pointer events.
We’re investigating how to successfully add NoMachine to Kaspersky’s trusted zone.
For the time being it is possible to disable self-secure option in Kaspersky GUI.
Settings -> Additional -> Self-secure -> Disable self-secure -> OKkroyContributorYou don’t need to keep changing your router’s configuration once you’ve set up port forwarding. You should set it up again only if your local IP on machine with nxserver changes. That’s why is better to reserve IP on router for that machine (static).
kroyContributorPlease try port forwarding. Configure your router manually to pass traffic to port 4000 (NX protocol) or (4022) (SSH protocol on Windows).
kroyContributorHi Lee.
Are you sure that you are using correct IP and Port number? If you have installed NoMachine free version on the server – you should enter information from last position with IP and Port list on “welcome window”. It’s your external IP. Also make sure that your router (from server side) supports UPnP or NAT-PMP and that the option is enabled. There is an article with instructions on how to connect to NoMachine when the server is behind a NAT router or a firewall https://www.nomachine.com/AR11L00827.
If your router does not support UPnP or NAT-PMP, it has to be configured manually to pass traffic to port 4000 (NX protocol) or (4022) (SSH protocol on Windows).
kroyContributorWe are not aware of any issues similar to what you have described. A reset of the NoMachine settings might help. This will allow us to see if the problem persists:
1. On Win XP navigate to \etc directory in NoMachine folder (in default is in “Program Files”).
You will see some sample cfg template files: node.cfg.sample and server.cfg.sample. You will also see node.cfg and server.cfg files. You should delete the node.cfg and server.cfg files or if you prefer to keep them, simply rename them node.cfg.old and server.cfg.old. Then rename the sample cfg files to node.cfg and server.cfg. Then restart nxserver – run cmd as a Administrator – navigate to bin directory in NoMachine folder and execute command: nxserver –restart
2. On Win 7 navigate to C:\Users\<your username> and delete or rename (if you want to save old preferences)the .nx directory. After that Create new connection to the XP machine.
And if that doesn’t help, we’ll need to look at the debug logs. Reproduce the problem – send logs from server and client side to forum[at]nomachine[dot]com? Instructions about collecting logs you can find: https://www.nomachine.com/DT04M00076.
kroyContributorHi.
On Fedora you need to add also GNOME_SHELL_SESSION_MODE=classic parameter to run gnome-classic session.
So node.cfg key should looks like this:
DefaultDesktopCommand “env GNOME_SHELL_SESSION_MODE=classic gnome-session –session gnome-classic”
kroyContributorAre you sure you entered the correct IP address and port? In your post there is no information about which license you have. If you have the free version (eg nomachine_5.0.58_1.amd64.deb), you don’t need to set-up configuration files to enable support UPnP. If you have installed one of other products, you should enable it (EnableUPnP key in /usr/NX/etc/server.cfg file on server side).
You can check the IP by using command:
sudo /usr/NX/bin/nxserver –upnpstatus
In line starting with “NX port 4000 mapped to:” there is IP and port which you should use to connect with your Lubuntu from external network.
If you are sure that the data you entered is correct, can you send logs from server and client side to forum[at]nomachine[dot]com? Instructions about collecting logs you can find: https://www.nomachine.com/DT04M00076.
kroyContributorHi,
Dynamic Tunnel in Putty use Socks protocol. NoMachine currently doesn’t support such protocol but there are plans to implement it.
Instead we suggest using HTTP proxy server or static tunneling methods available in Putty as Local/Remote tunnel.
December 21, 2015 at 15:57 in reply to: Start NoMachine Player from command line in fullscreen on multiple monitors #9413kroyContributorI would like it to a open in fullscreen on both monitors without me having to CTRL-ALT-0 out every time and click the corresponding icon after logging in to my remote PC.
– NoMachine player remember last display settings, so when you exit nxplayer with runned fullscreen on all desktop – next relaunch will be start with the same option.
Is this possible with a command line option?
– You can run connection file from command line to connect directly to the session. Execute:
[path_to_player]/nxplayer --session [path_to_session_files]/file.nxs
Example on linux:
/usr/NX/bin/nxplayer --sesson ~/Documents/NoMachine/example.nxs
Additionally, is it possible to specify a previously stored connection the Player should auto-connect to? Right now, I have to double-click on the connection every time despite it being known to the Player (it has my username stored when the login field comes up).
– You can create new connection and in last panel “Save as” select “Create link on desktop”. Double-clicking on that icon will run specific connection.
Auto-connect to the the physical session is available in default on NoMachine free version and NoMachine Enterprise Desktop. So you don’t need do extra configuration when you have installed such version.
If you are using another product from the Enterprise range with profiles enabled – you need to disable enable-multinode rule and all types from class “session” except physical-desktop. Instructions how to do it you can find there: https://www.nomachine.com/DT09K00058#3.
kroyContributorLocking the physical screen when somebody connects is a possible. This option doesn’t allow the local user to interact with the machine while somebody is connected.
Please read the tutorial here:
https://www.nomachine.com/blanking-the-host-screen-during-remote-controlkroyContributorAre you using a non-native firewall?
Please enable debug and reproduce the problem. Send logs from server and client side to forum[at]nomachine[dot]com. Instructions about collecting logs you can find here: https://www.nomachine.com/DT04M00076.
-
AuthorPosts