Networking - basic building

[Orangeb]

Hello Everyone,
I am new to networking - I have posted a couple of times on here. My cousin and I are building a very basic network for me, so I can learn by experience, not just watching videos etc.
He has a very complicated network. My little network is currently only in design stages - although now my tower PC works again, and has more memory in it and a very powerful graphics card (not that relevant I guess, but still)!
What I am working out, without giving my cousin a million questions a day, whislt he is at work, is if I have my basic network - PC tower with windows 11 on it, and ‘ontop’ that, a virtual machine, which will run a server OS, and then a small 5 port switch going to my Vodafone router.
I hope I have not missed anything, or got anything way off with that.
The first thing is, how does the PC with windows 11 on it AND the virtual machine with the server OS simultaneously talk to the network at the same time. It’s hard to describe what is in my head with this. It’s like they are ontop of each other. I am assuming the OS server would have to take priority, so it could act as a server? I’m guessing a domain controller would sit on that server OS too? I am not sure where, or what would deal with the DHCP and the DNS?.

Once I figure these basic things out I was thinking about putting in some storage, and wiring that into the network too, and maybe a small firewall. BUT I can’t do that without solving the more basic things, above. The DNS and the DHCP for example, what would be doing that? Where would they sit, and or exist? They are not hardware, they are a function of something - but what, in hardware terms?
Sorry for the complexity of this description - it’s a bit of a mess in my mind, being slowly untangled.
Thank-you for reading this.
Matthew

 

[Armageus]

The first thing is, how does the PC with windows 11 on it AND the virtual machine with the server OS simultaneously talk to the network at the same time. It’s hard to describe what is in my head with this. It’s like they are ontop of each other.

Yes a virtual machine would run "on top" of the Host OS, and special network drivers are installed by the virtualisation software to filter out the Guest machines data.
You could use something like VirtualBox or VMWare Workstation Player on top of Windows 11, but generally people virtualising their "homelab" will use bare-metal hypervisors such as Proxmox, VMware ESXi or Microsoft Hyper-V.

I am assuming the OS server would have to take priority, so it could act as a server?

The case of VirtualBox/VMWare Player then the Virtual machine runs like any other App, sharing the Windows 11 host's resources.

I’m guessing a domain controller would sit on that server OS too?

You generally wouldn't want a domain controller to be running on top of a Windows host, as presumably you would want the Windows host to make use of the various services that a Domain Controller could offer.

I am not sure where, or what would deal with the DHCP and the DNS?.

DHCP and DNS are normally done via a router, unless you have other specific requirements (e.g. Active Directory integrated DNS)

Once I figure these basic things out I was thinking about putting in some storage, and wiring that into the network too,

Storage will generally be via a NAS, whether that's something pre-built like a Synology or QNAP, or diy running either Unraid or TrueNas.
Both Unraid and TrueNas (and pre-built options) can also host various other services, virtual machines and Docker Containers.

and maybe a small firewall. BUT I can’t do that without solving the more basic things, above. The DNS and the DHCP for example, what would be doing that? Where would they sit, and or exist? They are not hardware, they are a function of something - but what, in hardware terms?

DNS and DHCP are network services - they are software based, but in a "normal" home environment are performed by a Router (e.g. currently your Vodafone router). As above unless you've a specific need then there isn't an immediate need to change this.

Sorry for the complexity of this description - it’s a bit of a mess in my mind, being slowly untangled.

No worries - everyone has to start somewhere

You are probably best working out what you want to achieve and what your budget is (as homelab stuff can easily get expensive fast, if you aren't careful).




A basic "homelab" will generally have some of the following features:

1. Router (Initially Hardware e.g. your Vodafone, but later could be software based e.g. OPNSense)
2. Network Switch - connected to the router, this connects all of your wired devices. PoE is useful for powering Wireless access points, CCTV, and other devices.
3. Wireless Access points - depending on the size of your house 1 or more access points, all wired back to the switch. Something like Unifi ideally to give you stats and extra control over signal coverage
(Note a Wifi Router can also be classed as an Access Point)
4. NAS (Network Attached Storage) - A device separate to your PC where you can store your music, videos, photos, documents etc. Makes life easier if needing to access from more than 1 device, and can be set up for both remote access, and off site backups.
5. Client Devices - wired and wireless PCs, Laptops, Phones, Smart TVs, Games Consoles etc.


More "clever" stuff - moving on from the above:

6. A hypervisor for virtual machines or a container host (as mentioned can be on a NAS device, or could be a separate PC - e.g. frequently mini PCs are used) - this is to run things that are "always on", so that when you turn your main PC off they stay running.
These things can include:
- Plex/Emby/Jellyfin media server
- "Other" media cataloguing and automated downloading services
- Pihole or Adguard home DNS based advert blocking
- CCTV software e.g. Blueiris or similar
- Home Assistant software
- Print Server or 3D Printing software
- Local Game Servers e.g. Minecraft etc

7. VLANs - allow you to segment up your network into Virtual Lans, controlling what devices can access either the rest of your LAN, or the wider internet. Hugely flexible, but can be difficult to get your head around at first.

8. Remote Access. Various methods available including VPN, or dedicated remote access software

9. Domain Controller / Windows Domain - generally only needed if you want experience of it for a job/workplace environment, or you absolutely need to have your home users log onto several PCs and have everything follow them (e.g. settings, documents, everything)

10. Software based router e.g. PFSense/OPNsense or others - fully software based firewall/router, infinite flexibility

 

[Orangeb]

That’s really kind of you to write such a detailed reply - thank-you.
Do domain controllers have to sit on a server? Like a windows server?
Is it just a program that runs, like Active Directory?

 

[Orangeb]

This is what appears on some searches about DCs.
“A domain controller (DC) is a server that responds to security authentication requests within a computer network domain. It is a network server that is responsible for allowing host access to domain resources”
If its gotta be on a server - how can it just sit on a normal windows 11 setup?

 

[Armageus]

Domain controllers are normally part of the "Server" edition of Windows, but most NAS hardware or software normally include a compatible domain controller role based on Linux Samba.

I do wonder why you are focused on a domain controller though? For 99.9% of users there is no benefit at home.

 

[dlockers]

It sounds like you want a lab environment rather than upgrade your home network. You can install several VMs on your PC with various roles and they can all connect to the network (a domain controller, file server, print server etc... whatever).

You may be thinking a "server" is something special. It isn't (in the general sense). It is just a computer running an OS except it lacks any nonsense like full media player or an email client etc...

Server operating systems remove this junk to be more reliable/less to go wrong/less to create a security issue.

I'd strongly recommend not messing with DHCP or DNS on your home network as it really isn't that interesting and it can screw up your day-to-day PC enjoyment for no gain.

 

[Orangeb]

I’;m doing it all really so I can get into IT support, with an aim to work in networking and then security (later down the line). There is so much stuff, and its hard to know where to focus. It’s like i need to be able to see a picture and or diagram of these things in my mind. So with the DC, its kind of working out “so if it sits on the Server, how can it also be beneficial for the standard windows 11 for example.

 

[Armageus]

I'm still not sure which bit you are struggling with?

Maybe a diagram will help

A Domain Controller is just a PC that runs Windows Server. Can be a Physical PC (e.g. the pink one in the diagram) or a Virtual PC (one of several Virtual Machines running on the Green hypervisor PC).

The Physical Windows 11 PC would use either of the Server 2019 instances for Active Directory and other Services. E.g. To log onto the Windows 11 PC using a domain User, the Win 11 PC would contact one of the Server 2019 PCs to verify the username and password.
Once logged on, domain controllers are then used to verify security access rights to File Shares, and are used to provide Local DNS services e.g. mapping computer names to IP addresses within your local network. E.g. typing Ping PC3, will look up the IP Address of PC3 from one of the domain controllers.


I think the point you are confusing based on your earlier posts, is that you want to run a domain controller on top of your Windows 11 PC?
You should never do this, as you can run into a catch 22 situation where if you set your Windows 11 PC to use the resources of the domain controller e.g. to log in, but you can't log in unless it's running.

 

[dlockers]

I’;m doing it all really so I can get into IT support, with an aim to work in networking and then security (later down the line). There is so much stuff, and its hard to know where to focus. It’s like i need to be able to see a picture and or diagram of these things in my mind. So with the DC, its kind of working out “so if it sits on the Server, how can it also be beneficial for the standard windows 11 for example.

Just do it as a lab environment then; don't complicate your home internet.

 

[Orangeb]

I'm still not sure which bit you are struggling with?

Maybe a diagram will help

A Domain Controller is just a PC that runs Windows Server. Can be a Physical PC (e.g. the pink one in the diagram) or a Virtual PC (one of several Virtual Machines running on the Green hypervisor PC).

The Physical Windows 11 PC would use either of the Server 2019 instances for Active Directory and other Services. E.g. To log onto the Windows 11 PC using a domain User, the Win 11 PC would contact one of the Server 2019 PCs to verify the username and password.
Once logged on, domain controllers are then used to verify security access rights to File Shares, and are used to provide Local DNS services e.g. mapping computer names to IP addresses within your local network. E.g. typing Ping PC3, will look up the IP Address of PC3 from one of the domain controllers.


I think the point you are confusing based on your earlier posts, is that you want to run a domain controller on top of your Windows 11 PC?
You should never do this, as you can run into a catch 22 situation where if you set your Windows 11 PC to use the resources of the domain controller e.g. to log in, but you can't log in unless it's running.

I’m confused how is best to approach networking, and how much depth you might need for an IT support role (just to start). Like do I need to know every intricate detail a switch might do - flooding with a MAC address of all Fs, when it might or might not do this, or does knowing what switches do and how to physically wire them up, and a more basic knowledge ok? I don’t mind learning every small detail, but don’t wanna waste time doing something people don’t really bother with.
The other bits are also a depth of knowledge required for routers, and then like you have written about, the diagrams of how everything sits and maps out on a network (like your diagram) - and what talks to what, and when it does so. For example, I didn’t realise the wi-fi aspect sits ina seperate place from the router (but having said that, I have not gotten into how and where wi-fi does its stuff, yet). I figured it would exist somewhere in the router. But that is obviously a very important bit of knowledge!!
Thank-you so much for the detailed reply. It is very helpful.

 

[Armageus]

I’m confused how is best to approach networking, and how much depth you might need for an IT support role (just to start). Like do I need to know every intricate detail a switch might do - flooding with a MAC address of all Fs, when it might or might not do this, or does knowing what switches do and how to physically wire them up, and a more basic knowledge ok? I don’t mind learning every small detail, but don’t wanna waste time doing something people don’t really bother with.

I wouldn't waste time on how a switch works for basic I.T. Support (e.g. basic helpdesk). How to physically wire them up, IP addressing, VLANs etc is probably all you need to know.

The other bits are also a depth of knowledge required for routers, and then like you have written about, the diagrams of how everything sits and maps out on a network (like your diagram) - and what talks to what, and when it does so.

Again with Routers, very little to learn for a general I.T. Support - again a lot of crossover with the above, but probably tied in with Routing between subnets and/or VLANs, but probably more basic things like port forwarding, firewall rules etc.

For example, I didn’t realise the wi-fi aspect sits ina seperate place from the router (but having said that, I have not gotten into how and where wi-fi does its stuff, yet). I figured it would exist somewhere in the router.

In a typical home network your Router already works as an access point (so a "Wifi Router"), but as you get to bigger environments (whether that be a big house or garden, or a business setttings), then it can be more beneficial to have the wifi in different places to where your Router is situated (and also to allow you to upgrade them separately e.g. to get a better Internet router without having to reconfigure your wifi)

 

[Begbie]

I recommend you sit a basic course, to get the understanding of domain controllers etc. it will help massively. There's absolutely tonnes of free ones available. MS even run their own, which I don't think are too expensive and are probably worth doing if you want to get into that field anyway.

 

[Zefan]

You should study the CompTIA A+ curriculum, it really is made for people in your position. If you can hack his accent, Professor Messer on YouTube has free training for the entire thing:

Professor Messer CompTIA A+ 1101 Playlist (Hardware, Networking, Virtualization)
Professor Messer CompTIA A+ 1102 Playlist (Software, operating systems, security)

I would advise doing the exams as well. This has three effects:

1) Gives you something tangible to show to prospective employers.
2) Creates a sense of urgency/a more clearly defined purpose behind your studying.
3) Gives you experience in self-paced learning. This is something that will pay dividends moving forward in the industry.

 

[Mujja]

@Orangeb you really need to follow a structured course. You're trying to do too much in one go.

As mentioned in the other thread, if you're starting out in IT you won't need to know how to install Windows Server and configure roles. When you get to the stage you'll be working with these services, it'll be in a support role before you're designing and implementing. Unless you're working for a small organisation, there will be well documented procedures and runbooks, and work you're asked to perform will be change controlled with all steps and commands defined.

A home lab will teach you a lot, but most places won't will let you loose in their environment because you've installed at home.

Even with a fully functioning lab and a few basic certs, no one is giving you a 3rd line role without a few years of experience. What you learn in a hands on support role can't be taught in a class.

 

[Orangeb]

You should study the CompTIA A+ curriculum, it really is made for people in your position. If you can hack his accent, Professor Messer on YouTube has free training for the entire thing:

Professor Messer CompTIA A+ 1101 Playlist (Hardware, Networking, Virtualization)
Professor Messer CompTIA A+ 1102 Playlist (Software, operating systems, security)

I would advise doing the exams as well. This has three effects:

1) Gives you something tangible to show to prospective employers.
2) Creates a sense of urgency/a more clearly defined purpose behind your studying.
3) Gives you experience in self-paced learning. This is something that will pay dividends moving forward in the industry.

I went to the YouTube links you sent me (thank you for those). There is a main video saying something like how to pass your exams etc etc. Then there is the first video. I assume just stick with the order they are presented in YouTube? I would assume they have laid them out that way, rather than randomly, but having said that, YouTube has a strange habit of mixing things up illogically, when you watch a number of videos from the same person.

 

[Zefan]

Yeah, these are playlists, so they will present in the order that the author intended.

The number at the end of each video title refers to the exam objective it's fulfilling.