RealVNC server not connecting locally after update from 20.10 to 21.04
Gilles Gravier
ggravier at fsfe.org
Mon Apr 26 16:32:08 UTC 2021
Hi!
On 26/04/2021 17:01, Colin Law wrote:
> On Mon, 26 Apr 2021 at 15:58, Gilles Gravier <ggravier at fsfe.org> wrote:
>> Thanks, Karl!
>>
>> On 26/04/2021 15:57, Karl Auer wrote:
>>> On Mon, 2021-04-26 at 15:09 +0200, Gilles Gravier wrote:
>>>> I can connect from cloud to my machine but when I connect to the
>>>> configured port from LAN, I get a connection refused. Even if I
>>>> telnet localhost 5900 ...
>>> "Connection refused" means nothing is listening on that port (or, less
>>> likely, that something is actively rejecting inbound packets to that
>>> port).
>>>
>>> You can check like this:
>>>
>>> netstat -an | grep 5900
>>>
>>> Cloud connections are often initiated from the client. Clients set up
>>> an outbound connection, and don't listen for connections in the
>>> "normal" way. I say this from a position of ignorance about how VNC
>>> does things.
>>
>> That returns nothing. Unlike if I use "22". :)
> Have you verified that the VNC server is actually running?
>
Yes. It is. RealVNC accepts both local and cloud connections. On my
machine, I can connect through cloud, but not locally from the same LAN.
It almost looks like there's some strange firewall rule that is dropping
the packets (but that even from the same host so maybe an application
level firewall?)....
Gilles
More information about the ubuntu-users
mailing list