Why use VNC and not XRDP?

[NicoVanDerDussen]

Hi,

Reading the forums and Twitters, it seems as if preference is given to TightVNC server and not XRDP.

However, I found that XRDP installs complete to even start when booting (sudo apt-get install xrdp)

This is much easier than configuring TightVNCServer.

Is there reason for the preference to use TightVNCserver rather than XRDP?

Thanks
Nico

[klricks]

Hi,

Reading the forums and Twitters, it seems as if preference is given to TightVNC server and not XRDP.

However, I found that XRDP installs complete to even start when booting (sudo apt-get install xrdp)

This is much easier than configuring TightVNCServer.

Is there reason for the preference to use TightVNCserver rather than XRDP?

Thanks
Nico

One reason is that XRDP will always open a new and independent session(s). The local session is not aware of the remote connection(s).
With TightVNC you can access the main session so that what is done remotely is shown on the local screen and vs.

Also RDP is a Windows invention. If I remember right TightVNC is actually installed and used by XRDP.

[Joe Schmoe]

One reason is consistency. If you are used to using VNC, it helps to continue to use VNC. Of course, the opposite is equally true: If you are used to using RDP, it helps to continue using RDP [*].

One reason to favor VNC over RDP in the Windows world is that RDP always opens a new session (and kills the primary session in the process - both literally and figuratively - trust me, I know of what I speak). So, you should never use RDP on Windows. And, since you shouldn't use it on Windows, you shouldn't use it on Linux (or anything else), because of "the previous paragraph" (above).


[*] Rule #1 of programmers has not been repealed. Programmers like what they know.

P.S. Ease of setup is a one-time thing. It is essentially a non-issue in the long term.

[blachanc]

P.S. Ease of setup is a one-time thing. It is essentially a non-issue in the long term.

Joe, you need to try to view things from a newbies perspective:

This first step can be difficult for newbies, and remote access can be one of the first task someone would like/need to do.

XRDP is a two steps (one step on PI, One step on the client( PC MAC ANDROID IPAD)) task that does not need any configuration.

I still how a github pull in the PI documentation regarding xrdp .... Easter weekend is probably a good time to do this

https://github.com/raspberrypi/documentation/issues/26

Ben

PS: as an example, I struggled 1-2 hours to get mail working the first time, now it is trivial (5-10 minutes) when I need to reinstall.

[DougieLawson]

XRDP is a two steps (one step on PI, One step on the client( PC MAC ANDROID IPAD)) task that does not need any configuration.

VNC is TWO steps. One on the RPi (sudo apt-get install tightvnc*), One on the client (PC, Mac, Android, etc.) that doesn't need any special configuration except for the IP address of the RPi and the password set when you first start vncserver on the RPi.

The only benefit of RDP is that the Windows client comes pre-installed on Microsoft systems.

[blachanc]

Only way to close the debate would be to find a 16 years old kid and ask him to do
the required steps (VNC vs XRDP) on two different PI, and this on the 4 platforms PC MAC ANDROID IPAD.

Otherwise, will will ourselves look like kids trying to convince each other.

Ben

[Joe Schmoe]

VNC is TWO steps.

Indeed - that was my real point. That "ease of use" in programming contexts almost always boils down to "Rule #1" (Programmers like what they know). If you are comfortable with RDP (and Windows-y things in general), RDP will look so much easier. There's nothing wrong with that.

It's like asking what is easier: English or Spanish? Well, obviously, the answer is whatever language your learned first. And so it is with everything.

[Cancelor]

I speak Russian.

[Joe Schmoe]

I speak Russian.

I certainly didn't mean to imply that English and Spanish are the only languages in the world.

Although, they certainly are the two primaries around here (where I live) …

[mikronauts]

XRDP only kills the open session on Windows, and that is only due to a deliberate crippling of Windows in order to disallow multi-user use of it. If you google, you will find replacement dll's that allow several people to log into a windows box at once.

I've tested xrdp'ing into one of my Pi's simultaneously from two computers, worked fine, while the local Pi console was also running. (mind you, it did slow down the response speed a bit, but it was quite usable for most things)

One reason is consistency. If you are used to using VNC, it helps to continue to use VNC. Of course, the opposite is equally true: If you are used to using RDP, it helps to continue using RDP [*].

One reason to favor VNC over RDP in the Windows world is that RDP always opens a new session (and kills the primary session in the process - both literally and figuratively - trust me, I know of what I speak). So, you should never use RDP on Windows. And, since you shouldn't use it on Windows, you shouldn't use it on Linux (or anything else), because of "the previous paragraph" (above).


[*] Rule #1 of programmers has not been repealed. Programmers like what they know.

P.S. Ease of setup is a one-time thing. It is essentially a non-issue in the long term.

[klricks]

XRDP only kills the open session on Windows, and that is only due to a deliberate crippling of Windows in order to disallow multi-user use of it. If you google, you will find replacement dll's that allow several people to log into a windows box at once.

I've tested xrdp'ing into one of my Pi's simultaneously from two computers, worked fine, while the local Pi console was also running. (mind you, it did slow down the response speed a bit, but it was quite usable for most things)

You also have to remember to logoff the RPi properly for each remote session. Don't just close RDP or else you could get multiple sessions left running on the RPi.

[MrEngman]

Hi,

Reading the forums and Twitters, it seems as if preference is given to TightVNC server and not XRDP.

However, I found that XRDP installs complete to even start when booting (sudo apt-get install xrdp)

This is much easier than configuring TightVNCServer.

Is there reason for the preference to use TightVNCserver rather than XRDP?

Thanks
Nico

Yes there is. For whatever reason xRDP does not work for me, but TightVNCserver and SSH do.

Can anyone suggest what I could look at to fix it? I have my own domain with dhcp and DNS servers and can access my Pi's using IP or hostname when using SSH or TightVNCserver.


MrEngman