Forum Replies Created
-
Posts
-
Here is the link to the Trouble Report. https://www.nomachine.com/TR02N06431
Check the ‘notify me’ box in order to receive notifications about when a fix has been released.There are two ways to do that: 1) if you are the owner of the computer which is showing up in the local desktop connections list, then you can disable the ‘Advertize on the network’ feature in the Connection Preferences of that PC. See here: https://www.nomachine.com/DT11M00106#3.1. for more details. That way, no one on the same network will see this computer.
2) If you simply don’t want to see this or any other computer (also those owned by other users) on the same network as you, follow the instructions here for the NoMachine Player on the machine/device you are connecting from, https://www.nomachine.com/DT11M00106#2.5.
You mentioned it was working last week. So something has changed in your set up. Are you sure that you have the local IP reserved for your machine? Maybe you have dynamic IP and it has changed? If you open NoMachine on the server side (the machine you want to connect to) does it still have the same IP that you were using before in the Welcome window?
We’re not able to reproduce this problem on Windows using the latest version. Just so we can make sure that we have your exact set up, can you tell us what type of session you are running when this happens and what are you connecting to? I.e are you connecting to a host with the latest NoMachine software installed and what product is installed on the remote computer?
You have two routers, and since you don’t control them, this makes things more difficult. You would need to contact the administrator to open the necessary ports to get access to the office network from home. The easiest option for you is to wait for NoMachine Network which will eliminate this problem altogether. You won’t need to know the IP address of your computer or worry about which router you have.
Can you send in what you tried to attach to the forum topic? Please submit everything to forum[at]nomachine[dot]com.
Can you give more details about the host environment, what Linux distribution? What product have you installed – NoMachine, NoMachine Workstation, Terminal Server?
Is the user connecting to a physical desktop or is it a virtual desktop session (Linux)? If it’s a virtual desktop session what’s the desktop environment?
Please check out these similar threads and follow the advice.
https://www.nomachine.com/forums/topic/error-138-cant-connect-to-office-computer-from-home
For sure you shouldn’t be killing nxserver, nxnode and nxd processes. Additionally, nxclient -monitor should remain as well.
Hi, we’ve tested again on Red Hat 5 and also Red Hat 6 just to make sure, but we are not able to reproduce this problem using the lastest version 5 NoMachine client whilst connecting to NoMachine 5 installed on the Red Hat instance running on Amazon.
Can you confirm what versions and products you are using from our website, on both client and server?
Were there any errors shown during the installation of NoMachine packages?
And did you install anything on the RH desktop before installing NoMachine? I.e is this a RH with factory settings, or have you installed other programs?
Seems the image was too heavy. We’ve sent you an email. Just reply to that and attach the image. Thanks.
NoMachine Network (formerly Anywhere) is in its final stages. Then it will enter the testing phase. I can’t give a precise date of release at the moment.
Security is utmost priority for all our products. If you don’t feel comfortable opening a port on your router, NoMachine Network is what you need.
There was no evidence of a session having been started in the logs you sent us, so we can only assume that you sent us the logs from the client side (the machine you are connecting from) rather than than server side (from the machine that you want to connect to).
Enabling debug on the server side is essential for us to see why you are not able to connect to that machine. Once enabled, start a session and then zip up the logs that will have been created.
To enable these logs, go to the folder of the NoMachine installation on the machine you want to connect to, and in the /etc/server.cfg, uncomment (remove the #) where it says SESSION LOGS and set it to 7. This is the same place where you can append the key “PhysicalDesktopAuthorization 0″ in which Nars suggested you do in an earlier reply. Placing it at the end is fine.
-
I have not updated the AVC pack since I updated the NoMachine version, would this be important?
The version of the pack should not be causing compatibility problems.
Send the logs to forum[at]…..
-