Forum / NoMachine for Windows / Not enough X resources
- This topic has 8 replies, 2 voices, and was last updated 5 years, 1 month ago by
fra81.
-
AuthorPosts
-
September 25, 2020 at 08:55 #29617
McVitasParticipantHello, so today I updated my Windows 10 laptop and since then I cannot connect to it via NoMachine!
The session negotiation failed. Error: Not enough X resources.
What is this and can it be fixed? Is it a problem with KB4576947 which got installed?
September 28, 2020 at 08:58 #29648
McVitasParticipantso I am really the only one with this problem??
September 28, 2020 at 09:08 #29649
McVitasParticipantFunnily enough today it started to work again! But I am nervous if it happens again what will I do. Wait until next day? :-]
September 28, 2020 at 09:53 #29674
fra81ModeratorHello,
should the problem happen again, please gather server side logs as explained in https://www.nomachine.com/AR10K00697. You can send them to forum[at]nomachine[dot]com.
September 28, 2020 at 16:05 #29678
McVitasParticipantso it broke again today š I sent the logs
September 29, 2020 at 14:40 #29704
fra81ModeratorHi,
the display service on the server can’t start up because it cannot find any free TCP port in the given range. This range can be modified to avoid conflicts with other applications as explained at point 6 of the following article:
https://www.nomachine.com/AR11L00823
However the fact that all those ports are unavailable is abnormal and it should be checked if there is an application that is misbehaving. You can see yourself what are the busy ports in the nxserver.log file:
2020-09-28 11:40:57 903.811 29296 NXNODEĀ Ā TCP port '7002' is used by another application. 2020-09-28 11:40:57 905.853 29296 NXNODEĀ Ā TCP port '7003' is used by another application. [...] 2020-09-28 11:40:58 376.810 29296 NXNODEĀ Ā TCP port '12200' is used by another application.To check what application is keeping those ports busy you may try one of these methods:
September 30, 2020 at 14:39 #29717
McVitasParticipantwell this is really weird. Yesterday it worked. Today it worked. Then I got an NoMachine update alert, so I did the update and AFTER it I can’t connect and have the same error!
I checked nestat -a and utility TCPView but NONE of the ports mentioned in nxserver.log as used by another application are there as listening or established! Seems like an error in your application or something weird in my system blocking the NXTryBindLocal function :-\
September 30, 2020 at 14:39 #29719
McVitasParticipantReboot of the target machine seems to be working as workaround, but it’s not practical to close and open all the apps again :-]
October 12, 2020 at 14:37 #29902
fra81ModeratorIt must be something on the system blocking the port binding, most likely the firewall.
-
AuthorPosts
This topic was marked as solved, you can't post.
