-: In order to support users working remotely,
it's necessary that we're going to provide
them the ability to remotely access
our networks and the resources they contain.
We can do this many different ways,
but one of the ways we do this is using
RDP or the Remote Desktop Protocol.
RDP is a proprietary protocol that was developed
by Microsoft to allow administrators and users
to remotely connect to another computer
and have a graphical user interface instead
of the command line provided by tools
like Secure Shell and Terminal Services.
This allows the user to operate the computer
as if they were simply
sitting in front of a Windows Desktop.
Now, remote desktop protocol provides
native encryption as part of the design,
but it doesn't provide for authentication.
Therefore, you have to enable SSL or TLS
for service authentication and require
some kind of a digital certificate
for increased security when RDP
is being implemented within your network.
There's also another thing called
Virtual Network Computing or VNC.
This is similar to RDP, but it's platform-independent.
Where RDP works on Windows machines,
VNC works on Linux, OSX, or Windows,
making it cross platform and an easy way
to get a graphical user interface
that you can remotely connect to.
VNC becomes a great solution for us to consider anytime
you're using things that are just beyond the Windows domain.
In order to use VNC or Virtual Network Computing,
you have to have a VNC server set up
on the machine that you want to access.
You also have to have a VNC client
on the machine you're going to access it from
and the VNC protocol, known as the remote
framebuffer, to communicate between the two.
VNC or Virtural Network Computing, normally,
is going to operate over port 5900 or 59 hundred
and it should only be used internal to your own network.
For connections outside of your enterprise network,
it's much more secure to use VPN or an SSH connection first
and then, tunnel VNC over that secure connection.