Not enough X resources

Forums / NoMachine for Windows / Not enough X resources

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #29617
    AvatarMcVitas
    Participant

    Hello, 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?

    #29648
    AvatarMcVitas
    Participant

    so I am really the only one with this problem??

    #29649
    AvatarMcVitas
    Participant

    Funnily enough today it started to work again! But I am nervous if it happens again what will I do. Wait until next day? :-]

    #29674
    Avatarfra81
    Moderator

    Hello,

    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.

    #29678
    AvatarMcVitas
    Participant

    so it broke again today 🙁 I sent the logs

    #29704
    Avatarfra81
    Moderator

    Hi,

    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:

    https://stackoverflow.com/questions/48198/how-can-you-find-out-which-process-is-listening-on-a-port-on-windows

    #29717
    AvatarMcVitas
    Participant

    well 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 :-\

    #29719
    AvatarMcVitas
    Participant

    Reboot of the target machine seems to be working as workaround, but it’s not practical to close and open all the apps again :-]

    #29902
    Avatarfra81
    Moderator

    It must be something on the system blocking the port binding, most likely the firewall.

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.