Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.os.windows-10 > #186524

Re: Alternative for remote desktop connection

From Fokke Nauta <fnauta@solfon.nl>
Newsgroups alt.comp.os.windows-10
Subject Re: Alternative for remote desktop connection
Date 2025-08-04 11:34 +0200
Message-ID <mfbd59F2lsiU2@mid.individual.net> (permalink)
References <mf4082Fpv52U1@mid.individual.net> <mf6ma7F98dlU2@mid.individual.net> <o78tmld4q1m.dlg@v.nguard.lh> <mf9oi7Fp0bfU1@mid.individual.net> <mcz8fbdd3ilg$.dlg@v.nguard.lh>

Show all headers | View raw

On 04/08/2025 01:11, VanguardLH wrote:
> Fokke Nauta <fnauta@solfon.nl> wrote:
> 
>> On 03/08/2025 02:56, VanguardLH wrote:
>>> Fokke Nauta <fnauta@solfon.nl> wrote:
>>>
>>>> On 01/08/2025 16:11, Fokke Nauta wrote:
>>>>> Hi all,
>>>>>
>>>>> At home I have my own W10 pc and two other W10 pc's and two W11 laptops.
>>>>> To have a remote connection with the other pc's and laptops I use
>>>>> RealVNC Viewer. U used it for years, but since last year I have to pay
>>>>> for it (about 250 euro's per year). It's limited for just a few
>>>>> connections. I'm not happy with it. It's too expensive, and sometimes it
>>>>> can't make a connection.
>>>>> Can you advice me an alternative that is cheaper and works well?
>>>>> Many thanks in advance.
>>>>>
>>>>> With kind regards,
>>>>> Fokke Nauta
>>>>
>>>> Thanks for your suggestions.
>>>> I installed TightVNC. It worked well for the other pc's, but not for the
>>>> wifi laptops. It asked for a password which I didn't know. I filled in
>>>> the password for the user of the laptop but that didn't work.
>>>> I uninstalled it.
>>>> I installed UltraVNC. It didn't work. It is asking for a password. Onve
>>>> again I filled in the password for the user of the laptop but that
>>>> didn't work. I installed a password in the server, but filling this in
>>>> in the viewer didn't work as well. So I unstalled this as well.
>>>>
>>>> So - I haven't got a clue.
>>>>
>>>> Fokke
>>>
>>> The VNC clients connect to a VNC server.  You have a VNC client
>>> installed on the remote host, and a VNC server on the local host.  For
>>> example, you'd have a VNC client on host-A, and a VNC server on host-B.
>>> When you connect the client to the server, the client needs to specify
>>> the login password at the server.
>>
>> I know that. You can choose to not using passwords. As this is all in
>> our home, I choosed for that.
>>
>>> https://www.tightvnc.com/doc/win/TightVNC_for_Windows-Installation_and_Getting_Started.pdf
>>> Installation
>>>     Register TightVNC Server as a system service (recommended)
>>
>> Ofcourse I did.
>>
>>>       By default, TightVNC Server is installed as a Windows service and
>>>       starts immediately after installation. At the end of the
>>>       installation you will be asked about passwords for TightVNC
>>>       Server as a service, in order to protect it from unauthorized
>>>       access.
>>
>> I choosed for not using passwords.
>>
>>> You SHOULD use a password at the server to ensure that intruders don't
>>> get access to your host running the VNC server.
>>
>> We don't have intruders in our home.
> 
> Then maybe when prompted for a password, you leave it blank, and hit
> Enter.  The expectation when choosing not to use passwords is that you
> don't get prompted for them, but maybe not using password with TightVNC
> means you just click through the password prompt.  A user reported
> "TightVNC site claims there is no default password", like blank or
> "password", also verified at:
> 
> https://www.tightvnc.com/winst.php
> "In the default configuration, each user can have his/her own separate
> WinVNC password, bit also there is a special default password used when
> no user password is available (e.g when nobody is logged in, or if no
> user password was set). Note: there is no any predefined default
> password in TightVNC, machine-wide password is called "default" just
> because it's used when there are no user-specific passwords available."
> (They need to use a grammar and spelling checker for their docs.)
> 
> Either there is no default password, and you have to specify one, or
> maybe they're trying to say the default password is "default".
> 
> It was unclear you would use VNC only with your intranetwork hosts
> versus having access to one of your intranet hosts from outside your
> network, like from the Internet.  That's highly likely why there is
> password protect on login.  When you get a prompt to enter a password,
> can you click OK to ignore the prompt?
> 
> Just not specifying a password at the server may not mean you don't need
> one to log into the server.
> 
> https://raspberrypi.stackexchange.com/questions/31281/tightvnc-to-windows-7-password
> 
> The respondent there said a password is required.
> 
> https://www.tightvnc.com/vncpasswd.1.php
> 
> "Each password has to be longer than five characters".  I can't see how
> a blank passwword could be longer than 5 chars.

Thanks.
I now use TightVNC for the two local W10 pc's. Don't use passwords and 
it works well. With my wife's W11 laptop it won't connect. It didn't ask 
for a password. I get an error message, saying that the connection has 
failed.
With my W11 laptop, it asks for a password. I didn't set a password.
With a secons attempt I did set a password, but it still didn't work. 
The password was not accepted.
So I won't use TightVNC for the W11 wifi connected laptops.

Fokke

Back to alt.comp.os.windows-10 | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-01 16:11 +0200
  Re: Alternative for remote desktop connection "Alan K." <alan@invalid.com> - 2025-08-01 10:28 -0400
    Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-01 18:19 +0100
      Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-01 12:33 -0500
        Re: Alternative for remote desktop connection "Alan K." <alan@invalid.com> - 2025-08-01 13:49 -0400
        Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-01 21:11 +0100
      Re: Alternative for remote desktop connection NY <me@privacy.net> - 2025-08-02 16:29 +0100
        Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-02 18:26 +0100
    Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-01 20:45 +0200
      Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-02 15:58 +0200
        Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-02 16:35 +0200
  Re: Alternative for remote desktop connection Graham J <nobody@nowhere.co.uk> - 2025-08-01 16:43 +0100
    Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-01 20:47 +0200
  Re: Alternative for remote desktop connection T <T@invalid.invalid> - 2025-08-01 09:02 -0700
    Re: Alternative for remote desktop connection T <T@invalid.invalid> - 2025-08-01 09:13 -0700
  Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-01 18:41 +0200
    Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-01 20:49 +0200
  Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-01 12:06 -0500
    Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-01 20:54 +0200
      Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-01 15:26 -0500
    Re: Alternative for remote desktop connection Michael Logies <logies@t-online.de> - 2025-08-06 15:58 +0200
      Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-06 18:41 +0200
        Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-06 12:35 -0500
  Re: Alternative for remote desktop connection T <T@invalid.invalid> - 2025-08-01 17:32 -0700
    Re: Alternative for remote desktop connection Philip Herlihy <nothing@invalid.com> - 2025-08-02 12:15 +0100
      Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-02 15:57 +0200
        Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-02 15:46 +0100
          Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-02 17:30 +0200
            Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-02 18:32 +0100
              Re: Alternative for remote desktop connection "Carlos E.R." <robin_listas@es.invalid> - 2025-08-02 19:53 +0200
              Re: Alternative for remote desktop connection Paul <nospam@needed.invalid> - 2025-08-02 17:53 -0400
          Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-03 19:43 +0200
          Re: Alternative for remote desktop connection Char Jackson <none@none.invalid> - 2025-08-03 20:41 -0500
            Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-04 11:55 +0100
              Re: Alternative for remote desktop connection Char Jackson <none@none.invalid> - 2025-08-04 23:22 -0500
                Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-05 20:24 +0100
            Re: Alternative for remote desktop connection "Carlos E.R." <robin_listas@es.invalid> - 2025-08-04 12:57 +0200
        Re: Alternative for remote desktop connection T <T@invalid.invalid> - 2025-08-03 23:10 -0700
          Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-04 15:37 +0200
    Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-02 15:54 +0200
  Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-02 16:40 +0200
    Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-02 19:56 -0500
      Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-03 20:36 +0200
        Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-03 18:11 -0500
          Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-04 11:34 +0200
            Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-04 14:06 -0500
              Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-06 08:59 +0200
    Re: Alternative for remote desktop connection Philip Herlihy <nothing@invalid.com> - 2025-08-03 21:07 +0100
      Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-04 11:24 +0200
        Re: Alternative for remote desktop connection Philip Herlihy <nothing@invalid.com> - 2025-08-04 10:50 +0100
          Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-06 09:01 +0200
            Re: Alternative for remote desktop connection Philip Herlihy <nothing@invalid.com> - 2025-08-07 11:39 +0100
              Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-07 15:19 +0200
        Re: Alternative for remote desktop connection Zaidy036 <Zaidy036@air.isp.spam> - 2025-08-04 16:25 -0400
          Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-06 09:03 +0200
  Re: Alternative for remote desktop connection Brian Gregory <void-invalid-dead-dontuse@email.invalid> - 2025-08-06 20:55 +0100
    Re: Alternative for remote desktop connection Brian Gregory <void-invalid-dead-dontuse@email.invalid> - 2025-08-06 21:00 +0100
      Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-07 15:22 +0200
    Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-07 15:20 +0200
      Re: Alternative for remote desktop connection Philip Herlihy <nothing@invalid.com> - 2025-08-08 11:44 +0100
        Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-09 12:59 +0200
          Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-09 13:17 -0500
            Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-10 18:01 +0200
              Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-10 18:12 +0100
                Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-10 19:33 +0200
                Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-10 19:08 +0100
                Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-11 09:46 +0200
                Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-11 14:07 +0100
                Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-11 08:19 -0500
                OT: Microsoft product (and service) naming (was: Re: Alternative for remote desktop connection) "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-11 14:36 +0100
                Re: OT: Microsoft product (and service) naming "Carlos E.R." <robin_listas@es.invalid> - 2025-10-20 11:06 +0200
                Re: OT: Microsoft product (and service) naming "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-10-20 10:48 +0100
                Re: OT: Microsoft product (and service) naming "Carlos E.R." <robin_listas@es.invalid> - 2025-10-20 13:36 +0200
                Re: OT: Microsoft product (and service) naming Frank Slootweg <this@ddress.is.invalid> - 2025-10-20 12:36 +0000
            Re: Alternative for remote desktop connection "Carlos E.R." <robin_listas@es.invalid> - 2025-08-10 19:57 +0200
      Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-10 20:42 +0200
        Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-11 09:44 +0200
        Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-11 14:09 +0100
          Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-11 08:53 -0500
            Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-11 15:53 +0100
              Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-11 13:03 -0500
                Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-11 19:31 +0100
                Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-11 21:11 +0200
                Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-12 02:00 +0100
                Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-13 21:21 +0200
                Re: Alternative for remote desktop connection The Horny Goat <lcraver@home.ca> - 2025-10-19 23:36 -0700
                OT: ageing (was: Re: Alternative for remote desktop connection) "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-10-20 08:45 +0100
                Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-11 20:20 -0500
                Re: Alternative for remote desktop connection Java Jive <java@evij.com.invalid> - 2025-08-12 12:35 +0100
                Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-12 14:16 -0500
                Re: Alternative for remote desktop connection Java Jive <java@evij.com.invalid> - 2025-08-12 21:11 +0100
                Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-12 17:24 -0500
                Re: Alternative for remote desktop connection Java Jive <java@evij.com.invalid> - 2025-08-13 05:10 +0100
                Re: Alternative for remote desktop connection Paul <nospam@needed.invalid> - 2025-08-12 15:29 -0400
                Re: Alternative for remote desktop connection Michael Logies <logies@t-online.de> - 2025-08-11 22:40 +0200
                Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-11 21:06 +0200
                Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-11 20:35 -0500
                Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-12 09:01 +0100
                Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-12 13:23 -0500
                Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-13 03:45 +0100
                Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-13 21:28 +0200
                Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-13 17:09 -0500
                Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-14 13:27 +0200
            Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-11 21:03 +0200
              Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-11 20:39 -0500
          Re: Alternative for remote desktop connection rsutton <rsutton43@comcast.net> - 2025-08-12 07:49 -0400
            Re: Alternative for remote desktop connection wasbit <wasbit@REMOVEhotmail.com> - 2025-08-13 09:26 +0100
              Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-13 11:39 +0200
                Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-13 12:13 +0100
                Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-13 18:33 +0200
                Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-13 12:52 -0500
                Re: Alternative for remote desktop connection rsutton <rsutton43@comcast.net> - 2025-08-14 08:22 -0400
                Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-14 16:00 +0200

csiph-web