- This topic has 1 reply, 2 voices, and was last updated 6 years, 10 months ago by
.
-
Posts
-
Hello,
I have 3 different computers, all Windows 10 home fully updated version 1709 (Fall Creators Update,) Build 16299.192, all running the latest version of the free edition of NoMachine (6.0.66). When I restart or first turn on my computer, I frequently run into an issue where after inputting my authentication information NoMachine states there are no available sessions, and if I click for more information the message states: “The server was unable to make the local display available or access to the local display is disabled.” One server is headless but the other two have monitors connected.
The really weird thing is that after 1 or 2 hours with no additional changes or input on my end, I am usually able to then connect to the remote server normally without issue. However, the fact I can’t remotely connect for an hour or longer after restarting my server is not a very good situation nonetheless. I’ve included my logs in an attached zip folder.
It is hard to say based on the received logs. Can you enable logs in server.cfg and node.cfg by uncommenting and setting SessionLogLevel 7? Then restart nomachine with command nxserver –restart and reproduce problem.
Instructions on how to enable and gather logs are available here:
https://www.nomachine.com/DT10O00163Also client side logs could be really helpful at this point.
Zip them all up and submit to forum. If the logs are big, you can also send them to forum[at]nomachine[dot]com making sure to reference your topic.
Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.