sk.bsd

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: Ubuntu 23.10 error 54: Connection reset by peer #46121
    sk.bsd
    Participant

    Hi Forum, I have installed [removed] on my Ubuntu machine and a client on my Mac. I have no experience with NoMachine so far, but [removed] works way, way better than [removed]. There is no problem with switching the monitor to a different computer. Therefore, I can do just what I wanted, i.e. connect and disconnect a monitor without any trouble with remote connexion. It would probably not be a good idea to watch movies on your remote desktop (although possible), but everything else is pleasantly smooth. The LAN traffic is from 500 kb/s to maybe 1.5 Mb/s depending on what’s going on on the screen. The only problem now is that I cannot get sound from apps like FireFox. The system sounds work fine.

    One caveat: you cannot be logged on as the same user locally and through [removed] (I think this is the same with [removed] ). If you try a remote session while logged on locally on your remote machine, you will get an empty screen. This is a bummer because there is no explanation or warning anywhere.

    Hopefully, NoMachine will get this sorted out, too. I consider this an absolutely basic and indispensable functionality.

    in reply to: Ubuntu 23.10 error 54: Connection reset by peer #46106
    sk.bsd
    Participant

    Thank you for your responses. I ran into this issue within 2 minutes of trying to set up a remote desktop. Certainly, I must be far from alone in this.

    I found that [removed] has no problem with Wayland without a monitor. Everything works, but it is quite slow and uses a lot of resources on the remote machine. I am not willing to disable Wayland just for this, so I will try other options like [removed], instead. I will report on the results here.

    in reply to: Ubuntu 23.10 error 54: Connection reset by peer #45856
    sk.bsd
    Participant

    In case it may help, here are some more details of the configuration:

    – Terminal: NoMachine for Mac free v 8.9.1_1, Mac OS 10.13.6

    – Remote (local network): NoMachine for Linux (deb) 8.9.1_1, Ubuntu 23.10, Gnome 45
    – Whether the problem arises connecting to a physical or a virtual display. Not sure about this: I have set Linux up with a display connected, but when trying to establish NoMachine connexion, the display is not attached (I switch it over to terminal).

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