Forum Replies Created
-
AuthorPosts
-
BritgirlKeymaster
A quick update from our last post on this topic. You can see from the image that I attached that performance has greatly improved, so much so that we can say that quality is on a par, if not better, with the other mentioned products.
Attachments:
November 10, 2014 at 12:25 in reply to: Supporting the blank screen feature during a remote desktop session #5341BritgirlKeymasterThe FR was originally inserted for an earlier version and it was then postponed to NoMachine 4 roadmap as is often normal practice as priorities can change. Development has been far from inactive regarding this particular feature. All we ask is for you to be patient a little while longer.
BritgirlKeymasterHi, please submit the logs again using the following contact, issues[at]nomachine[dot]com, and specifying the forum title in the subject.
Thanks.
Britgirl
BritgirlKeymasterOn the machine you are connecting from, open NoMachine and go to Preferences-Updates. The version will be written there. Yesterday we released 4.3.30, so it would be a good idea to update both client and server and see if the problem still persists.
BritgirlKeymasterThe next update will fix some copy and paste issues that we have reproduced in virtual desktop sessions. Thanks for taking the time to report.
BritgirlKeymasterWe’re taking a look at this particular model and will update the post once we have further information.
BritgirlKeymasterIs the client also 4.3.24? Did you revert the server or the client back to the previous version?
October 29, 2014 at 09:15 in reply to: Configure NX to connect to desktop manager in display :1? #5230BritgirlKeymasterIt’s possible by switching the virtual terminal from keyboard connected to the machine or remotely with help of chvt command line tool. Alternatively you can use a Xvfb for a secondary display.
Another solution is to use the Workstation edition from our virtual Linux desktop range of products.
BritgirlKeymasterA patch for this issue was released in version 4.3.24. See here:
BritgirlKeymasterFrom the logs your submitted:
The following error:‘2014-10-16 10:55:21 485.536 12919 NXSERVER ERROR! X resources are not enough to start another session.’
can occur when the server is not able to find a free display in the range defined by the server configuration.
Default values are:
#DisplayBase 1001
#DisplayLimit 200
You can try to increase value set for the DisplayLimit key to see if it helps.
The problem can be due to leftovers from previous sessions. The cleaning procedure to free system resources when a session
failed was not working properly in version 4.2.27. This problem is not present in the 4.3 versions.We suggest to upgrade your installation to the latest 4.3.24 version.
BritgirlKeymasterCan you tell us the exact version of Mac OS X?
BritgirlKeymasterI suggest you take a look at our installation guides. You can find these in the support section of the website: https://www.nomachine.com/all-documents.
Alternatively, you can find them also linked in our Knowledge Base https://www.nomachine.com/search/node/installation%20guide.
I also suggest you download and try the any of packages offering the virtual Linux desktop functionality. They are available in the following section of the website in evaluation. A good starting point is Terminal Server or Workstation:
BritgirlKeymasterHave you tried this?
BritgirlKeymasterRight now routers supporting UPnP or NAT-PMP are configured automatically to pass connections to NoMachine and all required information is 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).
Additionally, your NAT service is running on Virtual Box which means that it cannot be configured automatically with help of UPnP or NAT-PMP. To do it manually please refer to: https://www.virtualbox.org/manual/ch06.html#natforward
BritgirlKeymasterJust a reminder that 3.5.0 issues are now dealt with via the traditional support channels. From the logs we saw that it was an issue with 3.5.0 client to version 4 server.
A Trouble Report was opened and has since been fixed.
https://www.nomachine.com/TR11K04011
-
AuthorPosts