I can connect to my VPS via VNC through Remmina

Hi all,

This is my first topic here. I’m a recent Ubuntu user (less than 6 months) so I’m not a Linux nerd…yet. :slight_smile: I installed Ubuntu on my laptop and I want to access my Windows Server VPS via VNC. I know I can do it via RDP, but because of some software running on my VPS, that is not possible. This is why I want to use Remmina to access it through VNC. However, every time I try I get a black screen and a message on top saying ‘read (104: Connection reset by peer)’.

I can access it from another personal computer on Windows so apparently the issue is on my Ubuntu. Could some please help? Here you have my technical data:

Ubuntu Version:
Ubuntu 24.04.3 LTS

Desktop Environment:
GNOME version 46

Remmina version:
1.4.41 (git 3792a0bed)

You may generate info about this problem to try to get a clue on what’s happening:

In the client (Ubuntu):

  • Start Remmina but don’t try to connect to the VPS yet.
  • Open a terminal and enter sudo journalctl -f
  • Try to connect to the VPS with Remmina to get the mentioned error.
  • Go to the terminal you opened before and cancel the previous command pressing Ctrl+C
  • Look the generated messages for errors. You may also paste the messages here for help.

In the server (Windows):

  • I don’t know about Windows but you may do something similar to the Ubuntu part to get system and/or VNC server error messages during connection.

Thank you very much for your quick reply. I’m not sure it worked. This what i did on my Ubuntu laptop.

1. I followed dots 1 and 2 and I got the following result:

ego@ego-MS-7B86:~$ sudo journalctl -f
[sudo] password for ego: 
ene 23 13:13:12 ego-MS-7B86 gnome-shell[3296]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
ene 23 13:13:23 ego-MS-7B86 systemd[2967]: Started app-gnome-org.gnome.Terminal-36225.scope - Application launched by gnome-shell.
ene 23 13:13:23 ego-MS-7B86 dbus-daemon[3003]: [session uid=1000 pid=3003] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.259' (uid=1000 pid=36228 comm="/usr/bin/gnome-terminal.real" label="unconfined")
ene 23 13:13:23 ego-MS-7B86 systemd[2967]: Starting gnome-terminal-server.service - GNOME Terminal Server...
ene 23 13:13:23 ego-MS-7B86 dbus-daemon[3003]: [session uid=1000 pid=3003] Successfully activated service 'org.gnome.Terminal'
ene 23 13:13:23 ego-MS-7B86 systemd[2967]: Started gnome-terminal-server.service - GNOME Terminal Server.
ene 23 13:13:23 ego-MS-7B86 systemd[2967]: Started vte-spawn-caee4989-ae3a-45f8-95fa-cefe8ee9f4a3.scope - VTE child process 36244 launched by gnome-terminal-server process 36232.
ene 23 13:13:32 ego-MS-7B86 systemd[1]: systemd-timedated.service: Deactivated successfully.
ene 23 13:13:44 ego-MS-7B86 sudo[36258]:   ego : TTY=pts/0 ; PWD=/home/ego ; USER=root ; COMMAND=/usr/bin/journalctl -f
ene 23 13:13:44 ego-MS-7B86 sudo[36258]: pam_unix(sudo:session): session opened for user root(uid=0) by ego(uid=1000)

2. Then I followed dots 3 to 5 but no additional text appeared.

Does it make sense?

Well, in my case, without connection errors, it gives me at least some connection info. I’ve checked if I have some Remmina preference about logging level that explains it but I didn’t find anything.

You may also try starting Remmina (command remmina) from a terminal instead of the desktop manager. It may give more messages.

Also you may get some connection info/error at server side.

Seems that there is another way to get debug info in Remmina.

Open Remmina and go to the Menu (the three lines at upper-rightside) and choose Debugging. It opens a messages window. It may show something when trying to connect…

https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-22-04

A better reply is….what are you wanting to do on the remote system that needs the full desktop session? Why are you wanting to use VNC to connect to the remote system graphically?

I’ll try that, thanks.

As I hinted on my opening post, I’m using an app there that runs on Windows only. It is a visual software showing images being rendered. This is why I need the remote full desktop session. I need to confirm everything is working as planned from a visual point of view.

I don’t see the link provided includes how to connect to a Windows server, but an Ubuntu one. This is my problem. Had I had the possibility of using an Ubuntu based VPS nothing of this would happen. :frowning:

Ahhh my mistake. I thought you were going Windows to Linux. Apologies.

If you nmap the Windows system can you see the port open?

Is The Windows system on the same network as the Ubuntu one?

Can you ping between them?

On your question 1, I connected to the server and nmapped it. There are what I got:

PORT     STATE SERVICE
135/tcp  open  msrpc
139/tcp  open  netbios-ssn
445/tcp  open  microsoft-ds
3389/tcp open  ms-wbt-server
5985/tcp open  wsman
5986/tcp open  wsmans
7070/tcp open  realserver

On you question 2, no my Ubuntu laptop is at home and my VPS is somewhere in the US.

On your question 3, yes I can ping from my laptop to the server normally.

Seems VNC is not running on the Windows side. VNC use 5900 or 5800. Did you setup a VNC server to connect to?

Well, this is a clear example showing I have no idea what VNC is. When I said in my first post that I could connect to my server from another Windows based computer, I was wrong. What I did was connecting it via SSH, and not via VNC, sorry. :frowning: I’m not an IT guy, what can I say.

I can’t connect via VNC no matter what. I will contact my server’s support team to ask what can I do to connect to it. Thank you very much for your help.

You’ll need to install VNC server on the Windows side. This will unlikely be encrypted and, if you expose it to the Internet, it’ll be a place where all kinds of bad actors will try to brute force your password.

1 Like

According to the support team, my VPS does include a VNC server so the issue is apparently an IP communication malfunction. They are reviewing it. And no, I’m not planning to expose it to the internet. I know what can happen if someone sees an unencrypted door.

Well, after many complaints going in and out, I finally got my server IP changed and everything works fine now. Once more, the problem was in the provider’s side but charged on the client’s side. :unamused_face: As always, never cease to request what you are paying for!

Thank you very much again for your help, guys!

1 Like

Now that I can connect normally, a new problem arose. My local pointer does not coincide on the screen with the VPS pointer. Sometimes they are very close, but most of the time they are far apart. Fortunately, both obey mi clicks at the same time, but working this way is simply ridiculous. Could someone please tell me how can I make both be pointing at the exact same place on my screen all the time?

Have you tried other clients? Are they the same? If so, then its probably the config on the Windows side

1 Like

Yes, I tried Remmina and UltraVNC. Same problem on both. :frowning: Thank you for your help again.

AI has some possible fixes

Common VNC Pointer Solutions

  • Fixing Misaligned/Offset Cursor:

    • Match Resolutions: Set the VNC client and remote host to the same display resolution.

    • Disable Scaling: Set display scaling to 100% on both machines.

    • Monitor Alignment: In multi-monitor setups, ensure screens are aligned at the top or bottom in display settings.

  • Fixing Stuck or Inaccurate Cursor:

    • Toggle Relative Motion: Press F8 (or Fn+F8 on Mac) and uncheck “Relative Pointer Motion”.

    • Enable Absolute Mode: If supported, switch to absolute pointer tracking in viewer options.

  • Fixing Invisible or “Dot” Cursor:

    • Enable Local Cursor: In VNC Viewer settings, choose to “Track remote cursor locally”.

    • Show Pointer: Enable the AlwaysShowCursor parameter in the RealVNC Server expert options.

    • Virtual Display: If the machine is headless (no monitor attached), install a virtual display driver or plug in a dummy HDMI ghost plug.

  • Fixing Double/Ghost Cursors:

    • Disable “Enhanced Pointer Precision”: Go to Windows Control Panel > Mouse > Pointer Options, and uncheck “Enhance pointer precision”.

    • Disable Mouse Trails: Ensure mouse trails are turned off in Windows settings.