Your subscription doesn’t match the NoMachine server product installed

Forums / NoMachine for Windows / Your subscription doesn’t match the NoMachine server product installed

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #5699
    Avataromsi
    Participant

    HI.

    have installed the free new Linux Client/Server for Ubuntu:

    dpkg -i nomachine_4.3.30_1_amd64.deb

    Everything works :O) Then i have Installed the free Client for Windows on a Windows 7 laptop and an Windows 8 Home Computer to Connect to the Linux Server, work :o)

    Now installed the same Client on my Work Windows 7 Computer an get following Error by Connection:

    Info: Starting NoMachine version 4.3.30.
    Info: Loading settings from ‘C:\Users\oms\.nx\config\player.cfg’.
    908 4656 17:08:19 150.679 Main: Exception handling library not loaded.
    908 4656 17:08:19 150.679 Main: Creating the client session.
    908 4656 17:08:19 150.679 ClientSession: Initializing session at 0x0080ced0.
    908 4656 17:08:19 650.729 ClientSession: Initialized session at 0x0080ced0.
    908 4656 17:08:19 650.729 Main: Entering the GUI event loop.
    908 3596 17:08:21 074.872 ServerMethods: Failed to retrieve server version from:
    ‘NX> 614 Your subscription doesn’t match the NoMachine server product installed.

    NX> 614 Please visit the NoMachine web site at: http://www.nomachine.com/

    NX> 614 to acquire a valid subscription.

    NX> 614 The NX server can’t perform the requested operation.

    NX> 999 Bye.
    908 4656 17:08:21 075.872 ClientSettings: Settings file name unknown.
    908 4656 17:09:34 548.218 ClientSession: Starting session at 0x0080ced0.
    908 4656 17:09:34 548.218 ClientSession: Going to start session ‘C:\Users\oms\NXC495~1\config\Huk2.nxs’.
    908 4656 17:09:34 566.220 Connection: Initializing connection at 0x0548a5a8.
    908 4656 17:09:34 567.220 Connection: Initialized connection at 0x0548a5a8.
    908 4656 17:09:34 567.220 Connection: Starting connection at 0x0548a5a8.
    908 4656 17:09:34 567.220 ClientDaemonConnector: Starting a new connection to host ‘5.9.39.150’ on port ‘4000’.
    908 4656 17:09:34 568.220 Connection: Started connection at 0x0548a5a8.
    908 4656 17:09:34 575.221 ClientSession: Started session at 0x0080ced0.
    908 4656 17:10:04 569.220 Connection: Connection at 0x0548a5a8 failed.
    908 4656 17:10:04 569.220 ClientSession: Runnable at 0x0548a5a8 caused the session at 0x0080ced0 to fail.
    908 4656 17:10:04 569.220 ClientSession: Failing reason is ‘Could not connect to the server.

    Error is 138: Connection timed out’.
    908 4656 17:10:04 579.221 ClientSession: Stopping session at 0x0080ced0.
    908 4656 17:10:04 591.222 Connection: Stopping connection at 0x0548a5a8.
    908 4656 17:10:04 592.222 ClientDaemonConnector: Stopping the current connection.
    908 4656 17:10:04 592.222 Connection: Stopped connection at 0x0548a5a8.
    908 4656 17:10:04 608.224 ClientSession: Stopped session at 0x0080ced0.

    Why this, at Home everything works fine, its the same installation ??

     

    Hope some can help!!

     

    Thanks

    #5706
    AvatarHaven
    Contributor

    hello omsi,
    Attached logs show issue with NoMachine license but not on machine that you are trying to connect to, but on local host.

    You can verify this issue by executing:
    nxserver.exe –subscription
    nxserver.exe –version

    If you need some help with finding the reason of that issue send us logs from local machine. Please follow the instructions here:
    https://www.nomachine.com/AR07K00677
    Send them to issues[at]nomachine[dot]com

    About the issue with connecting to remote machine:
    NoMachine nxplayer failed to connect to ’5.9.39.150′ and returns error: Connection timed out. It could be due to issue with accessing port 4000 on that machine. In this case you should check router configuration if port 4000 is forwarded to the proper machine.

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

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.