> On 21. Jun 2020, at 20:02, Ian Lepore wrote:
>
> On Sun, 2020-06-21 at 19:54 +0200, Michael Tuexen wrote:
>>> On 21. Jun 2020, at 19:40, Ian Lepore wrote:
>>>
>>> On Sun, 2020-06-21 at 14:54 +0200, Michael Tuexen wrote:
> On 21. Jun 2020, at 14:28, Kostya Berger >
> wrote:
>
On Sun, 2020-06-21 at 19:54 +0200, Michael Tuexen wrote:
> > On 21. Jun 2020, at 19:40, Ian Lepore wrote:
> >
> > On Sun, 2020-06-21 at 14:54 +0200, Michael Tuexen wrote:
> > > > On 21. Jun 2020, at 14:28, Kostya Berger > > > >
> > > > wrote:
> > > >
> > > > Ok, it turns out, it gives the
> On 21. Jun 2020, at 19:40, Ian Lepore wrote:
>
> On Sun, 2020-06-21 at 14:54 +0200, Michael Tuexen wrote:
>>> On 21. Jun 2020, at 14:28, Kostya Berger
>>> wrote:
>>>
>>> Ok, it turns out, it gives the previously mentioned error only if I
>>> use VNC server string 0.0.0.0:5900 (as I always
Oh, I see, thank you.
Отправлено из Yahoo Почты для Android
вс, 21 июн. 2020 в 15:54 Michael Tuexen написал(-а): >
On 21. Jun 2020, at 14:28, Kostya Berger wrote:
>
> Ok, it turns out, it gives the previously mentioned error only if I use VNC
> server string 0.0.0.0:5900 (as I always
On Sun, 2020-06-21 at 14:54 +0200, Michael Tuexen wrote:
> > On 21. Jun 2020, at 14:28, Kostya Berger
> > wrote:
> >
> > Ok, it turns out, it gives the previously mentioned error only if I
> > use VNC server string 0.0.0.0:5900 (as I always did). in my VNC
> > client.But when replaced
Ok, it turns out, it gives the previously mentioned error only if I use VNC
server string 0.0.0.0:5900 (as I always did). in my VNC client.But when
replaced with127.0.0.1:5900it connects all right.
Отправлено из Yahoo Почты для Android
вс, 21 июн. 2020 в 9:40 Kostya Berger написал(-а):
> On 21. Jun 2020, at 14:28, Kostya Berger wrote:
>
> Ok, it turns out, it gives the previously mentioned error only if I use VNC
> server string 0.0.0.0:5900 (as I always did). in my VNC client.But when
> replaced with127.0.0.1:5900it connects all right.
I don't hink 0.0.0.0 is a valid
