![]() I then reinstalled NM on the windows machine, and I got the same exact error as beforeĪgain, I was previously able to get a connection, however it was a connection that I will not be using much. I made sure that port 4000 was forwarded. I followed the instructions for removing NM from the Linux machine. Connecting Windows 7 (2) to Windows 10 gives error 138. Connecting Windows 7 (1) to Windows 10 works. After that, please reproduce the problem and send the logs from server side. Connecting Windows 10 machine to itself from the public IP displayed in NoMachine works. NX> 611 The NX server can’t perform the requested operation.ģ356 2240 07:40:16 884.379 Connection: Started connection at 0x05e900d0.ģ356 2240 07:40:16 894.379 ClientSession: Started session at 0x0085f500.ģ356 2240 07:40:46 925.191 Connection: Connection at 0x05e900d0 failed.ģ356 2240 07:40:46 925.191 ClientSession: Runnable at 0x05e900d0 caused the session at 0x0085f500 to fail.ģ356 2240 07:40:46 925.191 ClientSession: Failing reason is ‘Could not connect to the server. Thanks for the logs, but after changing value SessionLogLevel you need to restart nxserver (you can do it from NoMachine Player: click on NoMachine icon on system tray -> Show the connection status -> Connection -> Restart). ‘NX> 611 No subscription information found. The error log includes:ģ356 6312 07:26:59 479.624 ClientServerMethods: Failed to retrieve server version from: Thinking this might be a licensing issue, I uninstalled NM on both the linux and windows machines, and completed a new install. I can say that this connection is not local, it’s through the router. I set up the server (raspberry pi) and the client ( Debian) and I do not found any problems to connect in my house. Both platforms have the same version of NoMachine (5.1.7 ). The firewall is turned off on WINDOWS and port 4000 is released in the Rules of Entry and Exit, TCP and UDP. I’m using NoMachine in a Raspberry Pi 2 and a laptop with Debian Jessie. Then installed NM Free on the Windows 7 machine in my office, and tried to make a connection. When I try to connect through WINDOWS Ubuntu, the following message appears: Error 138 connection timed out. Took the Linux machine home, physically plugged into router. Everything worked, but this is not the connection I need. Two days ago, downloaded NoMachine free on Linux box (laptop, actually), then tested to connection with a computer in my lab with the laptop on a wireless connection. As Windows 10 Home has no integrated Windows Remote Desktop Service (RDS. As it is super-fast and easy to handle within a home network it can be used to substitute a KVM-switch. Once it’s properly setup it is running smoothly. The Windows 10 machine acts as the server. One is a Windows 10, one is Windows 7(1), last one is Windows 7(2) all in different locations. Trying to connect from Windows 7 to Linux Ubuntu 15.10. NoMachine is a nice comfortable remote access tool, free for non-commercial use. NoMachine is up to date as of the update of.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |