Error 71: Protocol Error

Forum / NoMachine for Linux / Error 71: Protocol Error

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #18593
    benhbell
    Participant

    I have a client and a host both running on Ubuntu (one is 18.04 the other is 16.04 [HOST]) And I am unable to connect to the machine remotely.

    Both are running version 6.1.6

    The client connects and asks me to enter password, then it shows me a white screen, followed by an error screen.

    The connection with the server was lost.
    Error is 71: Protocol error.

     

    #18640
    Britgirl
    Keymaster

    It’s difficult to say why that’s happening.

    Better to enable debug, reproduce and then send us the logs. Player logs (connecting client side) would be useful as well. Please see the article here for instructions on how to get the logs:

    https://www.nomachine.com/DT10O00163

    Then send them to forum[at]nomachine[dot]com making sure you reference your topic.

    #18968
    tmehh
    Participant

    I got the ‘exact’ same.

    The connection with the server was lost.

    Error is 71: Protocol error.

    We can reproduce this at all workstations when updating/reinstalling to OpenSUSE Leap 15.0

    The rest of the workstations with < 15.0 are working fine.

    I will send the logs to forum[at]nomachine[dot]com

    A solution would be appreciated.

    Thanks in advance.

    Best Regards,

    Tim

    #18988
    Britgirl
    Keymaster

    Unfortunately, the log file you sent was empty. Additionally, we need server-side logs (see document I mentioned earlier). The document also explains the steps for getting the client-side logs.

    Send directly to forum[at]nomachine[dot]com.

     

    Thanks!

    #19099
    kroy
    Contributor

    Are you sure that ~/.Xauthority file has the correct permissions? Can you try removing ~/.Xauthority* files and re-login?

    Logs which you sent weren’t the right ones. The Player logs you must send are from the same session which we can find in /usr/NX/var/node/. If the suggested above workaround won’t help please edit /usr/NX/etc/node.cfg, uncomment and set the following:

    SessionLogClean 0

    Then reproduce problem and send again player logs and server side logs.

Viewing 5 posts - 1 through 5 (of 5 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.