So now that we've talked about some of our VP and VP and protocols, now we need to talk about our remote access protocols. Now remote access is not necessarily just over a VPN connection remote access protocols or protocols which work even on a local area network.
Their protocols, which allow us to connect from our local area network,
possibly to an Internet service provider. So our remote access protocols are another layer of protocols. Allow that allow us some point the point connective ity between us and another. Another device allows to remotely access another device remotely access another another point to point connective ity or another application on, and could
technically be utilized over our V p. M.
We could utilize our remote acts we could. We need to use a remote action server and connect to it over our VPN. Or we can utilize our remote desktop and connect in connect to a machine using remote desktop over a VPN connection. So remote access roles in a remote access
protocols are going to be another layer of our network knowledge that we're just going to cover, not necessary, not necessarily encompassing r V P M. But just another network access protocol that we need to be aware of. Our first aspect of our remote access protocols are going to be our is going to be our rass server.
Rass stands for our remote access server.
So saying rass server sort of like saying a T M machine. So ar rass is going to be a several roll roll that provides for
allows us to provide for remote authentication into remote access into a network. Rather, this is typically a Windows role that we can put on a server. And this is the server that we're going to use in order to set up how remote connections are goingto work.
We're going to set up how what type of protocols were going to use, what type of authentication method
we're going to use into our network. And it's going to be the one of the gateways that we have for someone remotely connecting into our network or someone trying to establish remote connection to our some some device inside of our network. So our remote access over can be on the perimeter of our network.
It could just be hanging out there in the d m Z
where we could connect to directly to the remote access server. But we may not want to do that. We may not want to put a remote access server out there on our public facing network because we don't we may not want to leave it vulnerable to intrusion. We may not want to leave it out. They're vulnerable to attack.
We could also for place remote access sober inside of our network
and then just have a VPN concentrator, which Ford's requests and Ford's Ford's Authentications to it. So
utilizing a VP and concentrator may allow us to put in pushing our remote actions. Serve a little bit farther, passed a couple additional security walls into our network. But just know that when you see remote access server, this is going to be a server that provides a remote, remote role that allows remote access into our network,
helps work for remote connections into our network
and allows users to begin establishing and negotiate what protocols were going to use in order to create this connection into our internal network.
So next we have our rdp protocol, and this is going to be our remote. Our Windows remote desktop protocol. Now Rdp Protocol is a peer to peer connectivity that allows for controlling a another computer. Essentially. So it's the protocol that allows you to create a remote connection into a
another computer and bring it up. And it's like you're sitting at that computer right there.
RDP Connection may, depending on our security policy, may or may not be disabled by default, but depending on how are how are I T department connection to our computer? How are remote users connect into their computer? We may need to enable our DP.
So our DP is going to need tohave in order for us to use our DP properly. The user that is connecting to the remote computer needs toe have permissions on that remote computer. You can't just initiate an already P session with someone else's computer that you don't have permission so long into.
It does require that you have permissions in orderto log in using an R D P session.
So keep that in mind when you're set. When you're trying to connect to a computer using our DP that you do need to have those permissions if you're going to try to log in and help somebody.
So in our D P session, it could be initiated from within our local area network. Weaken, Connect. We could connect a VPN connection from a remote site into our private network and then initiate in RTP session into a box there.
But just know that this is going to be our DP stains for our remote desktop protocol.
And it's a peer to peer connectivity, and it's a peer to peer control from one computer and establishing a connection to another computer. Next up we have our P p. P. O. E. Is going to be point the point over Ethernet and what it allows us to do is it allows us to encapsulate point to point protocol packets
inside of an Ethernet frame.
So it allows us to take point to point connective ity from
essentially what we as if we were connected directly to another server, another computer, another site, and then send that over an Ethernet type frame packet so we could formulate that we could create that point to point connective ity, and then we could send it over a. D. S l connection to our Internet service provider.
It can allow us to connect multiple local area network users
multiple point to point connective ity users over A. D S L network to the Internet to our Internet service provider. So with our point to point over Ethernet, what we're going to set it up. We're going to typically need a some sort of user name and password from our Internet service provider
that we put inside of our router that we are rather a modem
that we connect to our Internet service providers end.
So this point the point over Ethernet we'll see if it hasn't already been set up by our Internet service provider will take our user name and password will set up a point to point over Ethernet. It's going to encapsulate our point to point packets, send them over Ethernet to our Internet service provider and is going to allow us to connect
multiple users multiple people inside of our local area network
over Ethernet over that BSL to our Internet service provider. So all of them can access the Internet at once
and then lastly, we have I see a I see a stands for independent computing architecture, and this is a Citrix proprietary software which is, you know, lives for cross platform application management.
if you have a application that's running, say, on a
UNIX or Lennox over and then you have a windows, some sort of windows computer, or maybe even a windows to win a Windows machine to another Windows machine or to a Windows server and you're tryingto access and you're trying to manage an application that's running on that other machine. Well, I see a is Citrix is solution to this.
I see A is its proprietary sensor tricks, which means that in order to use it, you would have to be paying Citrix
and you you're able to manage these applications remotely, a little bit different than remote desktop. You aren't necessarily taking command of the entire desktop. You aren't taking command of the entire server. You're just taking command of this one particular application. You're taking command of this one particular software remotely.
So if you have say, we have a server that hosts multiple instances of an application that these users on our network need to use,
and we don't want each of them tow have to initiate a remote desktop session to the server, we just want them to utilize one instance of this application that we may invest in. I see a remains investing this independent computing architectures, which would allow each of those computers to initiate a remote session. With the application,
I wouldn't be able to initiate a
essentially connect into the server on Lee Toe, have that application pop up on their computer screen, and that application isn't technically running on their computer. They're just creating a session where they're connecting remotely to the application, running on some other device.
So that's I see a and again when Here I see a
see that see in there
and no, but it's Citrix. This particular software, or this particular protocol, is going to be Citrix proprietary on its use for cross platform applique remote application, handling an application management