So when we're talking about our local area network apologies. One of the main distinctions that we have between Earth apologies and between our connectivity is going to be peer to peer versus client server. Now, when we're talking about our peer to peer technologies, we're talking about anthropology where our clients talk
to and through other clients. So this is going to be a situation such as a work group or a home group in Windows where all we do is we set up our computers. They all have their independent network connections, and then they just allow shared resource is and shared files
to other computers on their network.
The benefits of having a peer to peer network include easy set up and install as well as not too much backbone Resource is or necessary. All we need are our computers, and that's about it. And then they negotiate, and they share their own files and and all the information they want to share.
The downsides of a peer to peer situation include limited scalability, limited management, little limited performance. If we have a peer to peer network, we can't do things such as global group policy. We can't manage what type of files air shared. We can't manage
that. Everyone. We can easily manage everyone having all their updates done
and another downside. Our performance. If we are using someone else's computer in order to pull their shared files than if they're doing something else or they're they're doing a lot of work on those files, then it's going to be harder for us to access to their files. Access their resource is because their computers busy doing other things.
So in our little peer to peer network,
all we would have is say, all we would need is a device that connects our different computers. So we're just gonna go extremely minimal here, and we're going to say this is an only one router slash switch with an I P address of 1 92.1 68.1 dot one,
and this all in one router switch connects over too.
and computer to over here has a printer
So Computer One has the I P address of 1 92.1 68.1 dot two
0.3 dot four and got five. So they all this is gonna be our We're gonna have a subnet mask of 2 55 to 55 to 55.0.
And so our host I d portion is just gonna be our final octet. We talked about all this during our I p segment, but all of these computers, their hosts idea is gonna be dot to 0.0.3 dot four and five are router slash Switch is gonna be 1 92.16 th that one. That one.
And if we want to share this printer out to everyone, we don't connect that printer to a server. We don't connect that printer toe. Really. Anything else other than this computer? And then this computer says, Yeah, I want to share this printer out to everybody.
So when computers to four and five start looking for a printer and they do the ad new printer wizard and they say, Look for a network printer than this printer is going to show up
being shared off of this computer and then all these other computers have to do is map that printer and then when Computer five has a printing job. It just sends it over
And if Computers two and four have shared files that they want everyone else to access,
they just share those files out
and everyone else can access it
now. The downside and another downside in our peer to peer connection is less security
in our peer to peer connection. If we're set up in a work group and we have shared files, there's really no way for us to manage what other computers have access to those shared files. If someone can connect to our network and is able to pull up our our work group name, they can see what share of resource is air out player, and they could just connect.
They don't really need any other authentication. They don't need a special user account
or a special password. They just know our work group name.
Our home group Name is a function of like our Windows seven has home groups available that if we have our network set the home, then we can put a password on essentially a work group with a password assigned to it, and it gives us a little bit more security.
But this isn't really useful for our. This isn't
good enough for office type environment we need. We need something more than just this peer to peer technology.
So a lot of times what we'll see is we'll see. Client server Now Client server allows us to have several clients that use a server or, in the case of a domain, at least one domain controller in order to manage shared resource, is manage files and are managed,
manage print jobs and everything like that.
So we have this client server domain set up, and this is ah more difficult initial set up. We will need ah server operating system to function as our server, but it is more scalable if we need to add more computers later in the future, we can do so a lot easier.
It's better management if we want to manage security better or we went to manage a group policy.
We want to manage permissions and resource is that it's a lot easier to do this on a client server network, and it also provides us for better performance. Our computers are actual workstation computers can stick to doing computer work doing day to day work, and then our server does server functions.
We don't need to have a computer that's also
half performing is a print server and two computers that are half performing his file servers. We have a server that performs server things and computers that do are and then work stations that do work station things.
in our client server topology,
we're going to have.
We'll go back and we'll say that we just converted this network into a client service apology.
So we're still a 1 92.1 68.1 dot one network
and we have a computer here
computer here. And let's say our computer three over there we decided, Okay, No one's using this computer. All we really are doing is having it hooked up to a printer. So why don't we just clean this out and install as a server
now? A lot of times, especially people that are new to I t are new to working with networks. When you hear server you think of Oh, this thing has to be this. This has to be a really heavy duty computer. This needs to be a maybe a blade Or maybe I have a stain. A tower server,
really hefty needs to have a ton of Ramaa. Lot of
a lot of processing power, a lot of storage. Well, that's really kind of a misconception. Our server, maybe one of the least powerful workstations we have on our network, but the function as long as the functions that is performing aren't really resource intensive.
If we have a server that all it's doing is acting as a print server and the domain controller and acts, acting is a place where we can store information for active directory.
Then, as long as that server is very reliable, it doesn't really need to be a super high performance graphical amazing server computer. It can just be our one of our additional work stations that we installed a server operating system on there so it doesn't hurt to get a server operating system installed on a computer
that you may have lying around, too.
Play with it and get the hang of it. But don't be intimidated by by the fact that something is called a server. It may just be a just standard workstation with the server operating system installed,
but that being said, we have our network here, and then we have our 1 92.1 68.1 dot to our server's gonna be 0.3. We have got 45
And then, of course, our server
in addition to being plugged into our printer were going to say that we also set up our server with several. We set up our server with several additional hard drives. Maybe we set up some sort of raid.
We had a raid set up redundant array of independent discs set up in our server so that we would be able to use it as a file server a little bit better.
So we have our client server. We have a client server network here. Now, our client server will need, at least again one server and
a lot of times in our windows domain, what you'll hear this server referred to as and what will need And at least one network is our in one domain. We call our domain controller also called r d C. Now what our domain controller is going to do? Is it sort of going? It's going to be in
some of the management and administrative functions of our network.
from our domain controller, we can set up active directory. What is active director? You may ask. Well, active directory is Think of it just as a roll call of users. Computers, passwords.
Essentially, it's just a roll call of everything on our network.
Everything that's allowed on our network and this connected to our network
Active directory on our domain controller can allow us to do things like create users from active directory. We can add computers to our domain and with active directory, it gives us a lot more functionalities to manage these other computers.
We can do things like Set group policy in sending group policy will allow us to set settings on these computers
just by modifying up some policies on our domain controller.
So with our client server, with our client server set up as opposed to our peer to peer, we aren't all just talking to each other and having this lax security. If, say, an unknown computer just plugged into our network
and we have, we have it set up so that they can't just join our domain. We have to have a domain. We have to have a domain administrator joined them into our domain. Then they won't be able to access things like our printer and our shared files. And if we do have shared files, we can say OK on Lee,
User Sally can access
our only user, Sally and User John
can access the sales files and then on Lee User
Onley. Rick and John can access the access the marketing files, and only Rick and Sally can access the I T files Weaken set permissions that our user specific permissions are work group on our home group. We can't do that. We can set user specific permissions for user's on our computer.
But if we share a file out, we can't set user
specific permissions for user's on other computers because our computer isn't aware of all those other computers that are out there. But in our domain, we can do that because we set up our users on our domain. We join these other computers to our domain, and then they log in as a user that's recognized on our domain
another function that a domain would allow us to dio. If we haven't implemented correctly, then we can if we want to. We can have roaming profiles where this may be a stand, a stand up workstation that John may need to log into. So then John logs into this workstation workstation,
and it creates a user profile for him. And he can't access Sally's files.
I may not be able to access Sally's programs, but he'll be ableto have. He'll be able to pull what looks like his desktop because his desktop icons and his configuration was saved on our domain controller so you can see how a client server set up again. It gives us a lot is a lot more scalable because
we could go ahead. And if this computer was a legitimate computer, we could add that to our domain very easily.
It's better management because we could easily manage all of these computers and manage what's shared out and manage what is not shared out.
But in the case of Appeared appeared to compare that to the case of a peer to peer technology where if we just have our small home network and we have it locked down. So no one outside say our family is able to connect in. Then we met and we don't really have the need for a server.
Then we may just go with this peer to peer technology because it is easier set up an installation.
And if it's just for a small group, are maybe one or two people even than that, maybe all we need. So evaluate your network accordingly, to decide if you need to go with a peer to peer or a client server network. But knowing the these two different types of network, knowing they're pros and cons
will help us to better identify what type of network we're working in
as well as better utilize one of these two different one of these two different setups in our own network.