> On 22. Jun 2020, at 15:55, Michael Tuexen wrote:
>
>> On 21. Jun 2020, at 23:12, Rodney W. Grimes
>> 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 23:12, Rodney W. Grimes
> > 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
BTW, I was not using it purposefully. I think I used it because it was
suggested by TigerVNC viewer itself. The original connect dialogue, I think,
had that address in it. So I used it, and it worked. This is how I remember it.
Other than that I NEVER used this wildcard address unless suggested
> On 21. Jun 2020, at 23:12, Rodney W. Grimes
> 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
> On 21. Jun 2020, at 23:12, Rodney W. Grimes
> 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
> > 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
> > > >
> 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
> 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
Hi,upgraded to 362292 via buildworld.Now I cannot connect to my bhyve guest as
I used to: neither via VNC nor via RDP.VNC gets error: unable to connect the
socket. Address family not supported by protocol family (47).
Neither can I ping my bhyve IP (it uses a separate NIC and should have no
15 matches
Mail list logo
